-
Notifications
You must be signed in to change notification settings - Fork 8
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
secondary collapse fails on down/sub-sampled fastq #105
Comments
seqtk probably mangled the fastq and/or metadata somehow. Can you post a small sample of your seqtk-processed fastq? |
attached is sample fastq with 5000 reads,.thanks |
The first is probably your real problem. |
1 has usually worked for me,.and since the only difference during failing was seqtk. I think it is 2nd. Is that comment filed is mandatory for bmftools? I can try adding it back,.because I can see that is the only difference from my original fastq which worked. Thanks |
and that "Description" field is optional for fastq format,.so not sure why bmf must want it,. |
What release are you using? Something related to this issue was fixed recently. #98 (comment) |
I have this, I guess I should re-pull? |
If you update to master, it should handle problem 2. And you shouldn't be working with varying read lengths as that assumption is made throughout the code base, but if you think it's working, then you can do what you want. |
Should this fix it? Do I need to do anything different to implement the change? Thanks commit f9483ea |
Yes, that commit does have the fix. (See Line 33 in f9483ea
|
Hi Daniel,
I am unable to run collapse on subset of downsampled fastq, it fails without any useful message. I used seqtk to downsample. All other tools can use those fastq without any errors,.
Thanks
Sukhinder
The text was updated successfully, but these errors were encountered: