-
Notifications
You must be signed in to change notification settings - Fork 25
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
Error about reference index #14
Comments
I am facing the same issue as the OP. When I run the command bamsnap -bam BAMs/NA18-281_CID21-7767_B21-613.BAM_ETC-RUO.bam -bed regions.bed -out snapshots I get the error as follows: I have tried both the dockerized container and running locally by installing bamsnap from the pypi. I get the same errors for both the cases. Any information/help regarding the issue will be helpful. Thanks. |
Apparently this issue was caused by the bed file I was using as input. The formatting of bed file was not appropriate and when the lines were split based on tabs (in the _options.py file line 127), the function wasn't able to split the lines properly. By reformatting the bed files, I was able to resolve this issue. Once again, thanks for this awesome tool! :) |
my command was
bamsnap -bam ./NA12878.final.cram -pos chr11:12314 -out ./test.png
It worked well but suddenly it didn't work with error below.
Traceback (most recent call last):
File "/usr/lib64/python3.6/multiprocessing/process.py", line 258, in _bootstrap
self.run()
File "/usr/lib64/python3.6/multiprocessing/process.py", line 93, in run
self._target(*self._args, **self._kwargs)
File "/home/sylee/.local/lib/python3.6/site-packages/bamsnap/bamsnap.py", line 227, in run_process_drawplot_bamlist
refseq = rseq.get_refseq(pos1)
File "/home/sylee/.local/lib/python3.6/site-packages/bamsnap/bamsnap.py", line 535, in get_refseq
refseq = self.get_refseq_from_ucsc(pos1)
File "/home/sylee/.local/lib/python3.6/site-packages/bamsnap/bamsnap.py", line 575, in get_refseq_from_ucsc
refseq[gpos] = seq[i]
IndexError: string index out of range
how can I fix this problem?
The text was updated successfully, but these errors were encountered: