Skip to content

Conversation

@pverscha
Copy link
Member

@pverscha pverscha commented Mar 19, 2025

This PR updates the build_database.sh script with support for the new domain and realm NCBI ranks. NCBI also changed the rank of the Viruses node to no_rank. Internally, we are mapping this back to domain to make sure that our LCA computations further downstream keep working.

In order to make sure that the desktop app still works, I have also updated the static database construction action. This one now generates two static databases: 1) a copy of the current database (which still contains the superkingdom rank and is compatible with the desktop app) and 2) an up-to-date database which is labeled as v2.

@pverscha pverscha added bug Something isn't working enhancement New feature or request labels Mar 19, 2025
@pverscha pverscha requested a review from tibvdm March 19, 2025 08:49
-e 's/serotype/no rank/' -e 's/clade/no rank/' \
-e 's/isolate/no rank/' -e 's/infraclass/no rank/' \
-e 's/parvorder/no rank/' "$TEMP_DIR/$UNIPEPT_TEMP_CONSTANT/nodes.dmp"
-e 's/parvorder/no rank/' -e 's/no_rank/domain/' "$TEMP_DIR/$UNIPEPT_TEMP_CONSTANT/nodes.dmp"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For clarity: Are the substitutions sequential? As in, will the last substitution not set all previous replacements to 'domain'?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't matter, since NCBI uses no_rank (with an underscore) and we've always used no rank (with a space). I will, anyways, update the order to improve the readability here :)

@pverscha pverscha merged commit 2fa4ef5 into master Mar 20, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants