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

10 Annotating amino acid sequences #49

Open
ccbaumler opened this issue Apr 22, 2022 · 3 comments · May be fixed by #80
Open

10 Annotating amino acid sequences #49

ccbaumler opened this issue Apr 22, 2022 · 3 comments · May be fixed by #80

Comments

@ccbaumler
Copy link
Contributor

Hello,

Just above the challenge portion of section 10 annotating amino acid sequences the instructions dictate installing KEGGDecoder. When attempting this I received this error:

note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

 × Encountered error while trying to install package.
╰─> numpy

After some different attempts, I found that KEGGDecoder's installation section suggests operating in python=3.6.

#changed the python version in kofamscan environment to 3.6
(kofamscan) baumlerc@bm14:~/2020_rotation_project/kofamscan$ python --version
Python 3.10.4
(kofamscan) baumlerc@bm14:~/2020_rotation_project/kofamscan$ conda install python=3.6

Best,
Colton

@ctb
Copy link
Member

ctb commented Apr 22, 2022 via email

@taylorreiter
Copy link
Member

we should probably update this to use eggnog mapper in hmm mode, and then pick a new viz

@taylorreiter
Copy link
Member

Actually I changed my mind -- eggnog doesn't assign kegg orthologs directly -- instead it assigns a COG term, and then I think uses DB joins to assign possible KOs. This process results in potentially multiple KOs per gene, without the scoring info to determine which has the best score or domain information to tell what part of the protein the KO corresponds to. kofamscan assigns a single kegg ortholog by default (the one with the best match), and can provide more detailed info on request. Having a best match dramatically simplifies downstream analysis for biological interpretation.

we should still probably pick a different viz though, something more stable..shrug.

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

Successfully merging a pull request may close this issue.

3 participants