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

Issues in KeyError: 'novel' #245

Open
kerrwelton opened this issue Sep 25, 2024 · 4 comments
Open

Issues in KeyError: 'novel' #245

kerrwelton opened this issue Sep 25, 2024 · 4 comments
Labels
duplicate This issue or pull request already exists

Comments

@kerrwelton
Copy link

Hi, thank you for developing this excellent software. I encountered an issue while running isoquant.py to analyze Oxford Nanopore data. Could you please let me know how to resolve it? I would greatly appreciate it.

Here are the parameters I used when running isoquant.py.
isoquant.py --reference GRCh38.p14.genome.fa
--genedb gencode.v46.annotation.gtf --complete_genedb
--bam memcd4.bam ncd4.bam ncd8.bam --labels memcd4 ncd4 ncd8
--data_type nanopore
-o isoquant_result
--threads 80
--check_canonical

The error message when running isoquant.py was saved in nohup.out.log, isoquant.log is the automatically generated by isoquant.py.
isoquant.log
nohup.out.log

@andrewprzh
Copy link
Collaborator

Hi @kerrwelton

Thanks for the feedback! Which version are you using? It seems I've seen issue in one of the previous IsoQuant versions and had been fixed since then.

Best
Andrey

@kerrwelton
Copy link
Author

I am using isoquant v2.2.0. Do I need to upgrade to a higher version?

@andrewprzh
Copy link
Collaborator

Yes, 2.2 is more than 2 years old, current version is 3.6, I highly recommend updating.

@andrewprzh andrewprzh added the duplicate This issue or pull request already exists label Sep 25, 2024
@kerrwelton
Copy link
Author

I updated isoquant to the latest version and rerun isoquant.py. Now it runs successfully with no error message. Thanks for you rapid and helpful response. :) :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants