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

Illumina data - coverage cap #17

Open
fbemm opened this issue Jun 13, 2019 · 0 comments
Open

Illumina data - coverage cap #17

fbemm opened this issue Jun 13, 2019 · 0 comments

Comments

@fbemm
Copy link

fbemm commented Jun 13, 2019

Hi Ryan,

I am using filtlong extensively as pipeline component and really like it. For a fully fledged assembly pipeline I use it with the Illumina read option. Due to different library sizes the memory footprint and runtime is often different. Would it makes sense to add a option that takes a total base count and stops reading Illumina data to speed things up and also keep the memory footprint for a given species uniform? Could also be done by specifying genome size and a target coverage. Gut feeling, its enough to have 40-50x coverage for a diploid. Otherwise one has to run through the file beforehand.

Cheers,
Felix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant