-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Parsing SAM to BAM from genome alignment #440
Comments
#231 has long been fixed. Are you using nohup or LSF/Slurm/etc? If unsure, use PS: samtools is complaining about line 3. What does that line look like? |
Hi You can see the line 3 using following link https://transfer.ipk-gatersleben.de/upload2/6uOsyohX/ |
You are hitting the limit of BAM format. In BAM, the max CIGAR operator length is |
Hi $minimap --MD -L -2 -ax asm5 -f 0.005 -t $threads -I $size -K $mem $ref $qry -o chr2_parts.sam When I convert into bam I got same issue in other line, [E::sam_parse1] CIGAR and query sequence are of different length The error line can be seen at https://transfer.ipk-gatersleben.de/upload2/SkcrBWb0/. if its related to CIGAR length issue, Would you please recommend a good way to align large chromosomes and get the output in bam which is required for downstream analysis. Thanks!!! |
Your last clipping again goes beyond 268435456. My recommendation is: don't use BAM. If you have to, split the chromosomes to length shorter than the threshold. As this is not a minimap2 issue, I am closing this now. |
Hi,
I aligned two chromosome sequences using minimap2 (version 2.17-r941) as below,
$minimap --MD -L -2 -ax asm5 -f 0.005 -t $threads -I $size -K$mem $ref $qry > chr2.sam
It produced the SAM output. However, this file was unable to convert to bam. I got below error,
$samtools view -@ $threads -bS chr2H.sam
| $samtools sort -@ $threads - -o chr2H_srt.bam
[E::sam_parse1] CIGAR and query sequence are of different length
[W::sam_read1] Parse error at line 3
[main_samview] truncated file.
Although this bug was similar to #231 it was not resolved with asm5 option. Could you please recommend something to fix this issue ?
The text was updated successfully, but these errors were encountered: