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.

Sign up for GitHub

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

Jump to bottom

Long Runtime to convert sseqid to sseq_name: Potential database solution #16

Open
howardxu520 opened this issue Aug 10, 2023 · 0 comments
Open

Long Runtime to convert sseqid to sseq_name: Potential database solution #16

howardxu520 opened this issue Aug 10, 2023 · 0 comments
Assignees
@byee4
Labels
enhancement New feature or request

Comments

@howardxu520
Copy link
Collaborator

If there are databases that can be used for sseqid -> sseq_name conversion. To improve runtime. Currently is taking 6 hours per dataset for 100K sequences for just converting the sseqids to sseq_name. Not including the blast and diamond runtime when we run new datasets.

Alternatively, we may build our own databases by collecting sseqid's sseq_name everytime we run different datasets.
@howardxu520 howardxu520 added the enhancement New feature or request label Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@byee4 byee4

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@byee4 @howardxu520