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

issue with reference file #179

Closed
janeshen91 opened this issue Apr 30, 2024 · 6 comments
Closed

issue with reference file #179

janeshen91 opened this issue Apr 30, 2024 · 6 comments
Labels
bug Something isn't working third-party problem Problem is related to other tools, libraries, system etc

Comments

@janeshen91
Copy link

Hello I ran the following command

str="20240411_1157_X1_FAX08446_1caf24e2"
docker run -v /vaxart-batch-input/:/input
-v /vaxart-batch-output/$str:/output quay.io/biocontainers/isoquant:3.3.1--hdfd78af_0 isoquant.py
--bam /output/samtools/reference/${str}_sorted.bam
--reference /output/reference/reference.fa
--data_type nanopore
-o /output/isoquant --report_novel_unspliced

and encountered the output

2024-04-30 22:59:58,231 - INFO - Running IsoQuant version 3.3.1
2024-04-30 22:59:58,232 - WARNING - Output folder already exists, some files may be overwritten.
2024-04-30 22:59:58,327 - INFO - Novel unspliced transcripts will not be reported, set --report_novel_unspliced true to discover them
2024-04-30 22:59:58,327 - INFO - === IsoQuant pipeline started ===
2024-04-30 22:59:58,327 - INFO - Loading reference genome from /output/reference/reference.fa
2024-04-30 22:59:58,354 - CRITICAL - IsoQuant failed with the following error, please, submit this issue to https://github.com/ablab/IsoQuant/issuesTraceback (most recent call last):
File "/usr/local/bin/isoquant.py", line 698, in
main(sys.argv[1:])
File "/usr/local/bin/isoquant.py", line 692, in main
run_pipeline(args)
File "/usr/local/bin/isoquant.py", line 644, in run_pipeline
dataset_processor = DatasetProcessor(args)
File "/usr/local/share/isoquant-3.3.1-0/src/dataset_processor.py", line 339, in init
os.symlink(self.args.reference, symlink_name)
OSError: [Errno 524] Unknown error 524: '/output/reference/reference.fa' -> '/output/isoquant/reference.fa'

As it directs me to submit this issue to github, can you please help? Is there something wrong with symoblically linking the reference file?

Thanks
Jane

@andrewprzh
Copy link
Collaborator

Dear @janeshen91

Is there something wrong with symoblically linking the reference file?

I seems so. However, the log doesn't give much information besides "Unknown error".
I see you use docker, right? Could you check whether symlinks work there just as usual?

IsoQuant does make a symlink to the reference file, since pyfaidx lib needs to make an index and by default it builds the index in the same folder as the FASTA files, which might be read-only.
It seems that it's possible to avoid symlinking and build an index in another location. I'll try to fix this workaround in the next release.

Best
Andrey

@andrewprzh andrewprzh added bug Something isn't working third-party problem Problem is related to other tools, libraries, system etc labels May 1, 2024
@janeshen91
Copy link
Author

Thanks Andrey. It does seem like there is a problem with my server not allowing me to create symlinks as usual. I'm trying to fix that, but is there any other work around right now? I've tried copying the reference file to the isoquant output folder but it didn't seem to solve the problem.

@andrewprzh
Copy link
Collaborator

@janeshen91

  1. First workaround is to run samtools faidx /output/reference/reference.fa, which will create a .fai index right near the reference genome. In this case IsoQuant won't create symlinks and use existing index.

  2. Apply this commit: dbd6074

Best
Andrey

@janeshen91
Copy link
Author

I'll try those, thanks Andrey!

@andrewprzh
Copy link
Collaborator

There are no symbolic links in the new version IsoQuant 3.4. So should work fine.

@janeshen91
Copy link
Author

janeshen91 commented May 9, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working third-party problem Problem is related to other tools, libraries, system etc
Projects
None yet
Development

No branches or pull requests

2 participants