Closed maxfarrell closed 3 years ago
So, we dealt with labroides on another post - that's a CLOVERT/NCBITaxonomy.jl issue.
saguinus nigricollis is the synonym for lentocebus that pulled up different taxonomy in CLOVER - and it doesn't have an NCBI match, so I wonder if it was manually curated by Rory? or is it a product of findSyns?
rupornis is also a synonym issue. the other match, from clover, is buteo magnirostris. but it doesn't have a host genus because, well, idk - probably outdated CLOVER code again. I think we're seeing a pattern.
marmosets is its own issue - let me create it.
The rest of these are Rory (so Rory - don't worry about marmosets, but the other two + the one documented on another post), so I'm going to call it a CLOVERT bug and leave it to him. I think basically these are two special cases where findSyns and/or manual curation had a weird outcome
Oh this is strange - it shouldn't be findSyns as I removed that from the pipeline entirely. Might be an issue of some older manual curation - I'll look into this now
@cjcarlson Fixed these and pushed a CLOVER update to the repo, so if you re-run the CLOVER integration these should go away in VIRION.
The problem was a few inconsistencies between manual higher tax and automated higher tax from hdict() - mainly caused by variable spellings in Host_Original in source datasets. All sorted now for these three but there could perhaps be more - I will keep an eye out
Nice work!
When attempting to make taxonomic trees I noticed that some species have conflicting higher taxonomies. This can be seen in the following example where Host is not NA:
This came up with four cases: