-
Notifications
You must be signed in to change notification settings - Fork 52
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
Fail to run with test.bam file #32
Comments
@icymiktreize |
@tanghaibao I get the same problem with icymiktreize . and I am sure that the bam file I used is in my current folder .so how can i fix the problem ? is there any other ways ? |
I fix my problem, by BWA-mem against hg38 reference not hg19 reference ,then I got the HLA type . now, I want to ask if xHLA only support hg38 reference not hg19 reference ? |
@yaruchen Currently yes - and ideally for consistency, the hg38 reference should not contain ALTs or any HLA contigs. Otherwise, the reads may need to be realigned. See discussion here. https://github.com/humanlongevity/HLA/wiki/BAMs-compatible-with-xHLA |
I'm experiencing the same problem I think. I'm using a CRAM file from Nebula. I converted CRAM to BAM:
then indexed bam file:
Then, with all files in a single folder, tried this:
but get error message: [16/Nov/2020 18:31:02] INFO - Xie Chao's HLA typing algorithm Appreciate if anyone can tell me what I'm doing wrong? |
Quick follow up to my question above - the problem was that the docker container couldn't access files outside the container. I revised the syntax to this, which worked: |
I was able to generate BAM/index files and process them following @rhdolin's information above, and I was also able to run Nebula CRAM files directly. The following format simplified things for me and seemed to work well: sudo docker run -it -v `pwd`:`pwd` -w `pwd` humanlongevity/hla --sample_id NG1092V0RF --input_bam_path NG1092V0RF.cram --output_path temp From Docker command line docs: "The -v flag mounts the current working directory into the container. The -w lets the command being executed inside the current working directory, by changing into the directory to the value returned by pwd. So this combination executes the command using the container, but inside the current working directory." |
I get an error when trying to run your test.bam (tests/test.bam) on Docker. It said:
[E::hts_open_format] fail to open file 'tests/test.bam'
samtools view: failed to open "tests/test.bam" for reading: No such file or directory
The script I ran is as below:
docker run -v
pwd
:pwd
-wpwd
humanlongevity/hla --sample_id test --input_bam_path tests/test.bam --output_path testYou can see the whole stack trace in the attached file. Can you help to run the script as I am not familiar with Docker? Thank you very much.
The text was updated successfully, but these errors were encountered: