-
Notifications
You must be signed in to change notification settings - Fork 113
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
Optional skipping of short-read input to Filtlong for large datasets #691
Comments
Hi @ddomman ! Thanks for this! This is great you have a solution already :) Within the module we could make it optional by inserting the short_reads1/2 into the ocmmand if supplied, something along the lines of:
If you want to contribute to the module and pipeline, you can make these changes via a PR to nf-core/moduels, and we can update in the pipeline (With credit to you!) - the contributions will be gratefully recieved :) Note that @muabnezor is currently in the process of overhauling the long-read/nanopore preprocessing tools anyway, we just merged into the That said, I think updating filtlong would still be very helpful to the community as a whole. Let me know what you think! |
I think this might be handled in the PR mentioned above, but IU need to check |
Description of the bug
Hi all - long time listener first time caller:
I have a rather large set of Illumina data along with some nanopore reads on which I was trying to run the hybrid assembly option. After 10+ hours,
filtlong
was still processing the nanopore reads. I did some digging and the current command utilizes the short-read data as part of the reference option. I think that is fine for small-ish datasets but seems impractical for larger ones.Once I edited the
filtlong.nf
code to no longer use the short-reads, the filtlong process took less than 5 minutes and the pipeline has proceeded as expected. Maybe there could be a flag to turn on/off that feature?filtlong.nf
:Edited working solution:
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: