issuesTraceback (most recent call last): File "/lustre/home/jianghao/mambaforge/envs/isoquant/bin/isoquant.py", line 808, in <module> main(sys.argv[1:])
i check all of requirements.txt, so what's wrong?
isoquant.py --test
commond line: ~/mambaforge/envs/isoquant/bin/isoquant.py --test
=== Running in test mode ===
Any other option is ignored
2024-08-02 21:01:57,137 - INFO - Running IsoQuant version 3.4.2
2024-08-02 21:01:57,265 - INFO - Novel unspliced transcripts will not be reported, set --report_novel_unspliced true to discover them
2024-08-02 21:01:57,265 - INFO - === IsoQuant pipeline started ===
2024-08-02 21:01:57,265 - INFO - gffutils version: 0.13
2024-08-02 21:01:57,265 - INFO - pysam version: 0.22.1
2024-08-02 21:01:57,266 - INFO - pyfaidx version: 0.8.1.1
2024-08-02 21:01:57,286 - INFO - Checking input gene annotation
2024-08-02 21:01:57,305 - INFO - Gene annotation seems to be correct
2024-08-02 21:01:57,305 - INFO - Converting gene annotation file to .db format (takes a while)...
2024-08-02 21:01:57,331 - CRITICAL - IsoQuant failed with the following error, please, submit this issue to https://github.com/ablab/IsoQuant/issuesTraceback (most recent call last):
File "/lustre/home/jianghao/mambaforge/envs/isoquant/bin/isoquant.py", line 808, in
This looks like a disk I/O problem. Is there a chance your run IsoQuant on some network disk, e.g. NFS share?
Best Andrey
This looks like a disk I/O problem. Is there a chance your run IsoQuant on some network disk, e.g. NFS share?
Best Andrey
thank you! i don't know why, Maybe it was caused by lustre? Best wish for you. Jhin
I guess it can. IsoQuant uses gffutils, which creates and SQL database from the gene annotation on disk. Unfortunately, it is not possible to create a database connection on network disks.
Thus, I suggest to run test in some other location, i.e. local storage. If you need to run IsoQuant using lustre, you may use --genedb_output <local folder> option. This will create a database in a local folder, but the rest of the output will be in main output folder.
Best Andrey
I guess it can. IsoQuant uses gffutils, which creates and SQL database from the gene annotation on disk. Unfortunately, it is not possible to create a database connection on network disks.
Thus, I suggest to run test in some other location, i.e. local storage. If you need to run IsoQuant using lustre, you may use
--genedb_output <local folder>option. This will create a database in a local folder, but the rest of the output will be in main output folder.Best Andrey
I understand, it can be used after I specify the dir in the /tmp directory. Thank you very much!!!
I guess it can. IsoQuant uses gffutils, which creates and SQL database from the gene annotation on disk. Unfortunately, it is not possible to create a database connection on network disks.
Thus, I suggest to run test in some other location, i.e. local storage. If you need to run IsoQuant using lustre, you may use
--genedb_output <local folder>option. This will create a database in a local folder, but the rest of the output will be in main output folder.Best Andrey
I'm getting this error again and using --genedb_output <local folder>option doesn't help. Can I provide the .db file input converted with gfftuils? How to do that? I only saw the sentence You can also provide gffutils database manually , but I don’t know how to do it.
@JhinJhinJhin
You can provide the database using the same --genedb option.
Best Andrey
Also, IsoQuant contains a script for GTF <-> database conversion: src/gtf2db.py