Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use DADA2 1.4 to fix quality-score precedence bug in parameters #56

Closed
ebolyen opened this issue May 1, 2017 · 2 comments
Closed

Use DADA2 1.4 to fix quality-score precedence bug in parameters #56

ebolyen opened this issue May 1, 2017 · 2 comments
Labels
type:bug Something is wrong.

Comments

@ebolyen
Copy link
Member

ebolyen commented May 1, 2017

It looks like this is up on bioconda, although it lists both 1.4 and 1.4.0 and I haven't had a chance to figure out the difference.

From a forum post:

There is a small bug in the 1.2 version of the DADA2 package the plugin is using (minQ is enforced before trimming, rather than after) that is preventing p-trim-left-f from working as expected. So you would need to trim off that bad staring base position with another bit of software to get it to work with the current QIIME2 plugin. When the plugin upgrades to the 1.4 version of DADA2 the p-trim-left-f approach should work.

The conda-recipe pins the version to 1.2 so this will need to wait until 2017.5 unless we want to patch.

@benjjneb would it be more appropriate to list our dependency as >= 1.2 (or rather >= 1.4 now) so that just upgrading dada2 fixes these kinds of issues?

@ebolyen ebolyen added the type:bug Something is wrong. label May 1, 2017
@benjjneb
Copy link
Collaborator

benjjneb commented May 2, 2017

My concern about removing the fixed version dependence is that I haven't guaranteed that the current q2-dada2 R scripts are robust to all default parameter changes, and there were 2 defaults changed in our 1.4 release.

I think this bug is sufficiently minor to leave until another release of the plugin, at which point it might be worth reviewing the R code and explicitly defining every parameter to allow for >= 1.4 dependencies in the future.

@ebolyen
Copy link
Member Author

ebolyen commented May 23, 2017

fixed by #61

@ebolyen ebolyen closed this as completed May 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something is wrong.
Projects
None yet
Development

No branches or pull requests

2 participants