-M --maximum-length info in documentation
See original GitHub issueHi there, thanks for the great tool 😃
The docs read for -M
:
–maximum-length LENGTH or -M LENGTH Discard processed reads that are longer than LENGTH. Reads that are too long even before adapter removal are also discarded.
I think maybe this was just an accidental copy/alteration of the -m
min-length (where that seems intuitive), but that doesn’t seem to be the case for the max setting as reads too long before but under -M
after trimming are retained (as i think would be desired). At least as late as version 2.3, toy example below.
Thanks again!
First sequence is 16 bps before trimming, 11 after ; Second sequence is 15 before trimming, 10 after:
No max set, both through just fine of course:
Max = 10 set, even though they are both too long before trimming, one is 10 after trimming, and that one makes it through:
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top GitHub Comments
And thanks for the report!
That’s now also fixed, thanks!