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.

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

Question about sylph-tax with custom database #42

Open
lingrongjin opened this issue Jan 22, 2025 · 1 comment
Open

Question about sylph-tax with custom database #42

lingrongjin opened this issue Jan 22, 2025 · 1 comment

Comments

@lingrongjin
Copy link

I followed https://github.com/bluenote-1577/sylph/wiki/Incorporating-taxonomic-information-into-sylph-with-sylph%E2%80%90tax to profile against GTDB220 and my own MAGs. However, I got this error when running sylph-tax:
Reading metadata: ['GTDB_r220', '../n620_taxonomy.tsv'] ...
Traceback (most recent call last):
File "Software/miniconda3/envs/sylph-0.6.1/bin/sylph-tax", line 120, in
main()
~~~~^^
File "Software/miniconda3/envs/sylph-0.6.1/bin/sylph-tax", line 117, in main
args.func(args, config)
~~~~~~~~~^^^^^^^^^^^^^^
File "Software/miniconda3/envs/sylph-0.6.1/bin/sylph-tax", line 21, in taxonomy_command
sylph_to_taxprof.main(args, config)
~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "Software/miniconda3/envs/sylph-0.6.1/lib/python3.13/site-packages/sylph_tax/sylph_to_taxprof.py", line 54, in main
taxonomy = spl[1].rstrip() + ';t__' + accession
~~~^^^
IndexError: list index out of range

I'm wondering if you have any idea what might be causing this error. I double checked that my taxonomy file does not include "t__STRAIN". However, many of my MAGs were novel at genus or species level (with g__;s__ for gtdb classification). I'm not sure if this might be the reason and if so should I modify the taxonomy file to manually assign ids to the unassigned genus/species rank?

@bluenote-1577
Copy link
Owner

@lingrongjin can you paste a few lines of your custom taxonomy file? see https://sylph-docs.github.io/sylph-tax-custom-taxonomies/ for the latest version of the document. You should not be including t__STRAIN.

Perhaps manually assigning ids would help...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants