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

Best action on first connect to a run. #32

Closed
mattloose opened this issue Mar 13, 2020 · 1 comment
Closed

Best action on first connect to a run. #32

mattloose opened this issue Mar 13, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@mattloose
Copy link
Contributor

If we have a run that has been in progress and then start read until, we see a large number of reads unblocked. In many cases these reads maybe longer than the max chunks parameter. Thus we are unblocking very long molecules which we might prefer not too. A better course of action might be to estimate the length of the read on that first grab of data and have some rules for rejection or sequencing. This is especially true if we have very long reads in our libraries.

@mattloose mattloose added the enhancement New feature or request label Mar 13, 2020
@mattloose
Copy link
Contributor Author

This is addressed and closed in the current release.

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

No branches or pull requests

1 participant