Closed Sann5 closed 10 months ago
Attention: 1 lines
in your changes are missing coverage. Please review.
Comparison is base (
22fd9a3
) 96.42% compared to head (feb5e4c
) 96.56%.
Files | Patch % | Lines |
---|---|---|
q2_types_genomics/reference_db/_format.py | 98.52% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@misialq
That all LGTM 🏅 I think, though, that this change will require updating the
classify-kaiju
code in q2-moshpit since you move the format used by that action - could you please double check and maybe open a small PR there to fix that, if needed? Thanks!
I believe there is no update required. The object that is used in classify-kaiju
is KaijuDBDirectoryFormat
which contains the file formats (NCBITaxonomyNodesFormat
and NCBITaxonomyNamesFormat
) that were moved with this PR. Now NCBITaxonomyNodesFormat
and NCBITaxonomyNamesFormat
are imported into the module where KaijuDBDirectoryFormat
is defined, instead of being defined in that same module. Only KaijuDBDirectoryFormat
is imported by q2-moshpit
, not NCBITaxonomyNodesFormat
and NCBITaxonomyNamesFormat
, so I don't see anything that breaks.
What's new
nodes.dmp
names.dmp
prot.accession2taxid.gz
build-custom-diamond-db
action, thereby allowing the user to obtain a database with taxonomy features.Run it locally
Assuming you have a working environment, run the following.
First, clone the repo and checkout the PR branch:
Now let's get you the data to try out the Semantic Type.
Now make an artifact with the new semantic type
Alternatively, you can run the tests for this Semantic Type (nothing will be downloaded).