Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
screen.seqs errors with optimize option #288
Comments
|
Sorry for the confusion. The name file label in the error message is misleading. It refers to the count file or name file in this case. Thank you for bringing to my attention the issue with the optimize parameter. I will look into that and work on a fix. |
khyox
commented
Jan 8, 2017
|
Thank you very much Sarah! |
|
The fix will be part of 1.39.0 releasing next week. :) |
mothur-westcott
closed this
Jan 9, 2017
mothur-westcott
added a commit
that referenced
this issue
Jan 10, 2017
|
|
mothur-westcott |
719e77e
|
khyox
commented
Jan 25, 2017
|
Thank you very much for the release of 1.39.0 with this solved! :) |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
khyox commentedNov 30, 2016
Mothur v.1.38.1 running on a GNU/Linux box. When using
screen.seqsin a batch file, the combination of the options count, alignreport and minscore works properly filtering the sequences:However, when I try to use the optimize option (with count and alignreport), the code fails with errors about the namefile, which is not an input:
On the other hand, the labels seem to exist in the current namefile (got with
get.current()just beforescreen.seqs):Finally, I unsuccessfully try to circumvent the problem generating an updated namefile and using it in
screen.seqs:Unlucky again.
Thanks!