-
Notifications
You must be signed in to change notification settings - Fork 6
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
ERROR: CIGAR and query sequence are of different length #1
Comments
Hi @michieitel , is there a way to send us the data you used so we can try to recreate this issue on our side? Thanks |
Hi @jmaricb - Cheers, |
Hi @ghelman91 , I am currently looking into it. What dataset and reference were you using? Thanks |
Hi @jmaricb - This is the command and output: I had also used the extend cigar option just to see if I could figure out what was going on but no luck. Here is my problem line: I might be able to directly send files if that would be helpful. Cheers, |
The same problem here! "CIGAR and query sequence are of different length" (graphmap2 (v.0.6.01)) [bhegedus@node2 map_all_03]$ samtools view -Sb -@60 full_length_barcode01_05_scaffold_1.sam > full_length_barcode01_05_scaffold_1.bam |
@ghelman91 @michieitel @HegedusB Could you try with the newest commit? I have fixed the cigar length bug. |
dear @jmaricb , I currently encounter the same issue with ONT reads using the Graphmap2 0.6.4. release. I do not succeed in converting my .sam graphmap2 output into sorted .bam files using samtools sort nor the comments described above. Thank you in advance. |
Can you share the dataset and the reference you are using and still getting different CIGAR and query lengths? I would like to run it and try to find the error. Thank you. |
Dear Josip
Thank you for your quick response. Can you tell me how to share this dataset the best with you? (preferably contained between us).
Thank you in advance.
Best regards,
Nick Vereecke
|
@menickname Well if you can, can you just send me one or several reads that have wrong CIGAR length? You don't need to send me the whole dataset. Just tell me which reference are you using then. |
DearJosip Thank you for your quick response. Below an example of the filtered/trimmed ONT reads. The used reference genome can be found at https://www.ncbi.nlm.nih.gov/nuccore/NC_045512.2 .
I did use following command: I have used the same dataset with the Graphmap pipeline and this did not give any problems in further sorting and indexing. The Graphmap2 issue appeared both on our local computer as well as our HPC infrastructure. Thank you in advance. |
Are you aligning RNA reads or DNA? If you are aligning RNA reads you should use '-x rnaseq' option. If you are aligning DNA reads then actually there is no difference between Graphmap and Graphmap2, so you could continue using Graphmap. I will take a look anyway. |
@jmaricb we are aligning DNA sequences. We like to work with the most-up-to-date versions of the available software. Please keep me posted if the issue got solved, then I could try to run it with Graphmap2 as well. |
I will let you know. It should work with Graphmap2 too. It's just that Graphmap2 has only updates for RNA reads so it should be the same regarding DNA reads. |
@HegedusB Do you solve the issue? I have the same problem: |
Hi!
I am getting an error when converting the
graphmap2
(v 0.6.0) generated sam file (of nanopore cDNA reads mapped to a reference assembly) to bam.These are the logs of the run:
my commands were as follows:
The line it complains about is this one (in the sam):
Can you please help me to figure out what went wrong? I specified to include extended CIGARs with
thanks
Michael
The text was updated successfully, but these errors were encountered: