qiime2 / q2-dada2

QIIME 2 plugin wrapping DADA2
BSD 3-Clause "New" or "Revised" License
19 stars 36 forks source link

ENH: initial plugin structure and actions #1

Closed gregcaporaso closed 8 years ago

gregcaporaso commented 8 years ago

@benjjneb, this creates the q2-dada plugin and adds support for your two DADA2 R scripts. The README.md has been updated to illustrate how to use this (including installation of development versions of QIIME 2 that are necessary to get this to work).

This is ready for review/merge. I've tested the instructions in the README on my end, but it would be great if you could test as well (see my note below about the bioconda install on Linux though, if you're working on Linux).

A couple of questions:

$ qiime dada2 --help
Usage: qiime dada2 [OPTIONS] COMMAND [ARGS]...

  Plugin website: http://benjjneb.github.io/dada2/

  Getting user support: To get help with DADA2, post to the DADA2 issue
  tracker: https://github.com/benjjneb/dada2/issues

  Citing this plugin: DADA2: High-resolution sample inference from Illumina
  amplicon data. Benjamin J Callahan, Paul J McMurdie, Michael J Rosen,
  Andrew W Han, Amy Jo A Johnson, Susan P Holmes Nature Methods 13, 581–583
  (2016) doi:10.1038/nmeth.3869.

Outstanding issues:

benjjneb commented 8 years ago

Looks good at first glance, but will test before merging, and think about filtering. Since just forward reads for now a pre-defined set of filter/trim parameters will work pretty well, but what is the longer-term mechanism for allowing the user to pass in parameters?

Changing names in the table is no problem.

We just headed to Hawaii for a week vacation so I might be a bit slow til I get back.

gregcaporaso commented 8 years ago

Thanks @benjjneb!

Since just forward reads for now a pre-defined set of filter/trim parameters will work pretty well

Do you have a recommendation for what those defaults could be?

but what is the longer-term mechanism for allowing the user to pass in parameters?

There are no limitations with users passing parameters right now. For example, in the plot-qualities visualizer that I wrapped around your R script, the user passes n, which is the number of fastq.gz files to generate plots for (n of the fastq.gz files are selected at random). You might be confusing this with use in Qiita, where the developers want to define a set of default parameters that can be use across runs?

I'll likely continue working on this in the next week while you're on vacation - I might try to add the filtering/trimming to the R script myself as I'm anxious to try it out on test data. I'll do all of this work on my master branch and have it update this pull request as I go.