-
Notifications
You must be signed in to change notification settings - Fork 1
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
A problem of version 0.12.2 #2
Comments
Thanks, I'll refer to the answer for this error on the previous issue: ...I will leave this issue open to track an improved error message update for you. |
Hi, after running Sawfish v0.12.2, the previous error in #1 has been fixed. However, I got another error regarding 'discover' step.
all bam files were aligned by minimap2 with code my script to run sawfish is attached below:
I initially thought this was due to a memory issue and I increased it to 144 GB on a 30x coverage BAM file, and sawfish failed again. Because you mentioned the mem per core should be less than 8 gb, in which case I may need instruction from your side. Thanks again for your time, |
Copied this report into a new issue #3 |
Related to the original issue on this thread, the v0.12.3 release fixes the error to a (non-panic) message describing that hard-clipped input is not currently accepted. |
I am running sawfish-v0.12.2 on this bam file https://s3-us-west-2.amazonaws.com/human-pangenomics/working/HPRC_PLUS/HG002/analysis/aligned_reads/hifi/GRCh38/HG002_aligned_GRCh38_winnowmap.sorted.bam using the command line:
sawfish discover --threads 16 --ref Homo_sapiens_assembly38.fasta --bam HG002_aligned_GRCh38_winnowmap.sorted.bam --output-dir HG002_discover_dir
The following error happens:
thread '<unnamed>' panicked at src/refine_sv/trimmed_reads.rs:197:5: assertion failed: !is_hard_clipped(&record.cigar())
Below is the full running log:
I am wondering whether this version can be upgraded to bypass this issue?
Thank you.
The text was updated successfully, but these errors were encountered: