-
Notifications
You must be signed in to change notification settings - Fork 31
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
IndexError: list index out of range #358
Comments
Seem there are too many candidates identified in your sample. Chromosome X has approximately 156,040,895 base pairs and was split into 32 chunks for parallel processing. In your log, for each chunk, about 32% (1,607,233 out of 4,876,277) of genomic positions were classified as candidates, leading to an OOM issue. Could you please check the IGV of the BAM file to verify if the reads are aligned properly? |
Hi @zhengzhenxian With quick consensus, almost no SNP is found: |
The error rate of the provided BAM file is significantly higher than other HiFi datasets. We recommend using the latest HiFi data produced by PacBio if you are testing the performance of Clair3. |
Hello all
Both tumor and normal samples from PacBio Hifi fails at Clair3 with index out of range and memory errors. I was not expecting Clair3 to use more than 96GB of RAM for a long read run, but I'm not sure.
Setup
Operating system: Cluster - CentOS
Clair3 version: v1.0.9
Installation method (Docker, built from source, etc.): Singularity (latest version, v1.0.9)
Type of data: Pacbio Hifi -> from article https://genomebiology.biomedcentral.com/articles/10.1186/s13059-022-02803-x , tumor sample: https://www.ncbi.nlm.nih.gov/biosample/10102573 , SRX5735702
48 Threads available, running program with 32 threads and 192GB RAM
Any additional context:
Files have been mapped using minimap2 with -x map-hifi and a custom made reference: GRCh38_full_analysis_set_plus_decoy_hla.fa
Both tumor and normal BAMs seems to have the same pattern, but I can post one read here if necessary.
Command used:
Error:
The text was updated successfully, but these errors were encountered: