-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
When converting 'taxid' into full taxonomy from prot.accession2taxid , the program terminated after an error is reported #55
Comments
Add the flag Besides,
Also see the example 1 at usage page.
Maybe in some taxonomic names. Here they are:
|
Thanks, Dr. Shen, you wrote such good software, and sorry I didn't follow your tutorial carefully. Here is the new error message: goroutine 124244 [running]: |
Yes, it's a bug, but only occurred for input of deleted taxids with the flag You may have used I've fixed it, please use the binaries below. |
It worked! Thanks a lot. |
Dear developers! Could you clarify please is correct? I also had an error, but after adding
|
Hi, I'd recommend using commands below:
|
Thank you! Well done. Now it is much better that it was before! |
Why does the program find only 12 taxa out of 14? What needs to be updated? 137758 Potyviridae 5 |
It's easy to explain: the lineages of some taxid changed. See https://github.com/shenwei356/taxid-changelog/ . You can check the changes of the TaxIds above. taxid.log.tsv.gz
So the result could change when using a different version of the NCBI taxdump file. |
shenwei356 Thanks a lot! |
Prerequisites
taxonkit v0.9.0
go version go1.17.7 linux/amd64
Describe your issue
wget -c https://ftp.ncbi.nlm.nih.gov/pub/taxonomy/accession2taxid/prot.accession2taxid.gz
sed '1d' prot.accession2taxid | csvtk cut -t -f 2,3 | taxonkit lineage -i 3
| taxonkit reformat -i 3 -f "{k};{p};{c};{o};{f};{g};{s};{t}" -F -P -S -j 24
| csvtk cut -t -f 1,2,4
| csvtk add-header -t -n accession,taxid,taxonomy > nr.tax
[ERRO] parse error on line 37402419, column 96: bare " in non-quoted-field
while there is no quotation marks detected.
The text was updated successfully, but these errors were encountered: