![]() |
|
|||||||
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| bowtie SAM mapq field | rgregor | Bioinformatics | 2 | 12-19-2012 04:04 PM |
| Hyphens in CIGAR column of sam file? | GeneJockey | Bioinformatics | 3 | 05-08-2012 09:34 AM |
| The 'S' in CIGAR of sam file (bwa) | qixiaofei | General | 6 | 09-15-2011 11:28 PM |
| bowtie - invalid CIGAR string - wrong sam format | genome | Bioinformatics | 2 | 02-16-2011 01:36 PM |
| the meaning of CIGAR column in SAM file outputs by BWA | holywoool | Bioinformatics | 2 | 01-04-2011 04:34 AM |
![]() |
|
|
Thread Tools |
|
|
#1 |
|
Junior Member
Location: usa Join Date: Jun 2010
Posts: 4
|
In a SAM file generated from Bowtie, I found one entry has '*' in the CIGAR field. What does this mean, bad alignment?
Thanks |
|
|
|
|
|
#2 |
|
Senior Member
Location: Berlin Join Date: Jul 2011
Posts: 156
|
It means "not available" in the SAM spec. Typically, this happens when the read isn't aligned (RNAME - 3rd field - is also '*' and 0x4 is set in the FLAG field).
|
|
|
|
|
|
#3 |
|
Junior Member
Location: usa Join Date: Jun 2010
Posts: 4
|
Thanks, arvid.
To what extend, Bowtie sets the FLAG to 0x4 for a read, and make the CIGAR field "not abailable". What are the measure and threshold bowtie uses for setting this? Thanks |
|
|
|
|
|
#4 |
|
Senior Member
Location: Berlin Join Date: Jul 2011
Posts: 156
|
Well, using the settings (default or your specific choices), Bowtie found no reportable alignment for that read.
It is not possible to make a general statement about this behaviour here as it depends entirely on the settings you provided bowtie with and the nature of your reads and reference. Check the bowtie manual, typically you should look at alignment and reporting modes - these and their sub-options control alignment sensitivity and reporting filters. |
|
|
|
|
|
#5 |
|
Junior Member
Location: usa Join Date: Jun 2010
Posts: 4
|
Hi Arvid,
Thank you very much for the help. |
|
|
|
![]() |
| Thread Tools | |
|
|