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

Streamlining setup of blast databases #411

Open
Don-Isdale opened this issue Oct 9, 2024 · 0 comments
Open

Streamlining setup of blast databases #411

Don-Isdale opened this issue Oct 9, 2024 · 0 comments
Assignees
Labels
phase:discussion prospective-feature Discussion of a feature which might be added - is not yet confirmed as a requirement

Comments

@Don-Isdale
Copy link
Collaborator

Description

This issue is a proposal / discussion to simplify and streamline setup of blast databases.

It would be sufficient for the user to drop the fasta file into the Pretzel GUI, and input the text datasetId; Pretzel will do the rest of the blast database setup :

  • create the datasetId/{.dbName & .dir } (if not present)
  • build and index the blast database

Currently the 'DNA Sequence Search' panel dataset pull-down contains the list of datasets which have the BlastDb tag.
Pretzel server should also check that the datasetId blast directory exists and is readable, and not include datasets in the blast search list if they not ready for blast search, i.e. check that the blast database exists and is readable and indexed.

Pretzel GUI can display a notification tag in Dataset Explorer for datasets which have a tag BlastDb but are not ready for blast search; message display in dataset panel (can have a button for refresh status also).

@Don-Isdale Don-Isdale added phase:discussion prospective-feature Discussion of a feature which might be added - is not yet confirmed as a requirement labels Oct 9, 2024
@Don-Isdale Don-Isdale self-assigned this Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
phase:discussion prospective-feature Discussion of a feature which might be added - is not yet confirmed as a requirement
Projects
None yet
Development

No branches or pull requests

1 participant