-
Notifications
You must be signed in to change notification settings - Fork 415
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
sarek v3.1.2 -- error for ascat #977
Comments
I ran it with GRCh37 and other default settings. |
Hey! This looks like an error with the ASCAT tool. Can you attach the The parameter |
Here you go. Take note I edited the file to mask my actual working directory. command.err.txt |
Just for you information, I also encountered issues with msisensorpro and deepvariant, but only for GRCh37. It worked okay with GRCh38. |
Actually, this sounds more like an issue with cancerit/alleleCount than Ascat. There are some issues mentioned on their github repo. Can you check out if any of those are of help? |
Just an update, the error can be due to this "connection time out" error: [W::find_file_url] [W::find_file_url] Failed to open reference "https://www.ebi.ac.uk/ena/cram/md5/96e414eace405d8c27a6d35ba19df56f": Connection timed outFailed to ope I'm not sure exactly what's going on. The connection timeout seems to be intermittent. I tried running the pipeline a few times, and each time some samples were cleared. It could be that our server is blocking too-frequent access to external data, or EBI is denying my connection. For now, I guess, when this happens, I'll just rerun the pipeline. |
I was referring to GRCh38. For GRCh37, the issue persisted. |
Dear user, Hello, I resolved it! Check if the chromosomes in your BAM file have the "chr" prefix. In that case, you need to modify the "ascat_loci" in the igenome.config file. Please refer to the bottom of the following page for information on "'chr'-based versus non 'chr'-based reference": |
I have encountered the following error. I have tried both with out without --save_output_as_bam. It didn't help. I also ensured sufficient memory (256G) is available.
Thank you!
The text was updated successfully, but these errors were encountered: