I'd like to post on the issues/questions/answers I run into as I work through it. It'll also give me an opportunity to get back to Bioinformatics (e.g. multiple sequence alignments).
The first thing is that they recommend you use a virtual machine (Virtual Box) and install the QIIME Virtual Box on it, which is a huge download that packages Ubuntu Linux with all of the QIIME dependencies, correctly configured. Sounds like a great idea.
I started by trying this. I had to download overnight on my machine at work (> 2 GB), then buy a new thumb drive to bring the file home, since I don't have the recommended amount of memory for the VM (1 GB) on that machine. But I ran into trouble---basically much aggravation dealing with the different keys on Linux, but also the Virtual Box and extra work trying to figure out copy/paste, moving files over, etc. The killer was when the VM prompted for an administrator's password, and of course I don't have it. There shouldn't be one needed..
[ After a search of the Forum the mystery word is revealed to be: qiime. I shoulda guessed it. ]
So I decided instead to deal with the dependencies for QIIME. I got almost all of them (like 24 or so), but for the "default pipeline" you really don't need so many. Particularly if you already have PyCogent and matplotlib installed, as I do, I would recommend just going down the list. It's not difficult, and it's better to be in an environment where you're comfortable working.
There was really no trouble configuring them (at least the essentials).
#1: Python 2.6I have it, since I'm on OS X. I ran into a little trouble because (from playing with MacPorts) I still had
/opt/local/binon my path as changed in
.bash_profile. The QIIME install checks this variable and modifies its scripts (the she-bang thing), so I had to fix that later on.
#2: Numpy 1.3.0I have this too.
Not sure what the default OS X version is, but
easy_installwill fix you up quickly.
#3: PyCogentOf course, this has its own dependencies. But we've been through that before (here, here, here).
#4: MUSCLEThis is not one of the primary dependencies, but it's an old friend. I upgraded to the latest and greatest version, but it caused an error in the QIIME tests. Luckily I still had
muscle3.6_srcaround. As usual, I put it in
and I put
#5: MAFFTIt's an installer. Piece of cake. Check it:
#6 uclustSee the QIIME install notes for this. This is the work of Robert Edgar (also the creator of MUSCLE), who is a talented programmer, but also a businessman. Hence, no source code, and no 64-bit for some things. But there's a download link on the QIIME site. The only problem is that Safari put a .txt extension on the download and I thought there was a problem, went off on a wild goose chase, and got a version that is not new enough. Enough said. Put it in
~/Softwareand link as usual
unpack and move to Software
MAFFTpasses all tests except:
That's pretty silly.
#8 Greengenes files
greengenes core set data file (fasta)
greengenes alignment lanemask file (txt)
Where to put them? I put them in qiime_tutorial, see below, but will eventually want them in Qiime somewhere.
#9 FastTreefasttree 2.1.0 (src)
move to Software and link
#10 JavaI don't need to add the Java runtime. I got it from Apple a while ago (here):
#11 RDP Classifierrdp_classifier-2.0.1 (src)
Check for mismatch between the name of the classifier file. What I actually got was named 2.0 not 2.0.1.
#12 QIIMEThat's it for the default pipeline..
I followed their advice and put the install scripts in a special place (but I wouldn't do that again).
The problem with the special directory is you will need a
.qiime_configfile (see the docs)
Make sure to put it in
Also not needed yet but I'll list them here anyway:
We've done that one before. The
BLASTMATvariable must point to the NCBI data directory. In
#15 RRun R and do:
I upgraded to R 2.12.1 from 2.10.0, but it has some issue. Trying to get the ape package from CRAN hangs the app. I backed off to 2.11.1 (see here).
Still to come:10 more bits of software.
But they're not needed for the first part of the tutorial, so we should just do that first. Oh..I also have
Sphinxinstalled (from the PyCogent instructions), so the documentation got built. But I've just been working from the web version anyway. On to the fun stuff.