Any tips on starting processing on Qiime1 and transitioning to Qiime2 after splitting libraries?

Hi @ErikaGanda, Glad to hear that you’re excited about QIIME 2!

You have a few options right now:

  • You can generate a biom table and phylogenetic tree with QIIME 1 (e.g., using pick_open_reference_otus.py) and then import those files into QIIME 2 artifacts for the “downstream” analyses, including alpha and beta diversity, and taxonomic profiling and differential abundance testing. Importing is described here.
  • You can wait for the next release of QIIME 2, which should have multi-threaded support for DADA2 (though I can’t promise a specific date for this at the moment, I expect that it will happen in 2016).
  • Or, you can apply DADA2 on a per-MiSeq-run basis right now, and then merge the resulting files. This process is illustrated in our FMT tutorial. This process could take a long time to run – possibly a week or more, but we haven’t tried this on a dataset of this size yet, so I’m not certain about that. There is an approach that you can use to parallelize it. If you have access to a machine with at least six cores/processors, you could start a qiime dada2 denoise job for each of the MiSeq runs, and let all of those run at the same time. I’m not certain how much memory you would need per job, but I estimate at least 4GB. This would be possible to do on Amazon Web Services (we’ll be releasing an amazon image for this by the end of next week), or if you have an institutional supercomputer resource.

Thanks for attending the workshop, and for your interest in QIIME 2!