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

Add additional limitations for long query sequence #348

Open
billzt opened this issue Dec 26, 2017 · 3 comments
Open

Add additional limitations for long query sequence #348

billzt opened this issue Dec 26, 2017 · 3 comments

Comments

@billzt
Copy link

billzt commented Dec 26, 2017

Some end users that are not familar with bioinformatics might use long query sequence (>1Mb DNA sequences). Usually this is meaningless and instead would take long running time. It is better if we can set additional limitations for long query sequence when setting up this server.

@billzt
Copy link
Author

billzt commented Mar 30, 2018

Well, is it possible?

@yeban
Copy link
Collaborator

yeban commented Mar 30, 2018

Hey @billzt. I can think of two ways to do this. Query sequences are written to a temporary file on the server before running BLAST. One could check file size and throw ArgumenError before running BLAST. The other option is to intercept paste event in the browser and immediately inform the user if pasted data is too much. The second approach is more reactive and thus preferable, imo.

@billzt
Copy link
Author

billzt commented Apr 1, 2018

Yes. Hopes this could be implemented

@yannickwurm yannickwurm added this to TODO in 2.0 Oct 27, 2021
@yannickwurm yannickwurm moved this from TODO to In progress in 2.0 Oct 27, 2021
@yannickwurm yannickwurm removed this from In progress in 2.0 Oct 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants