<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for MassGenomics</title>
	<atom:link href="http://massgenomics.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://massgenomics.wordpress.com</link>
	<description>Medical genomics in the post-genome era</description>
	<pubDate>Sun, 06 Jul 2008 17:43:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by jhui</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-65</link>
		<dc:creator>jhui</dc:creator>
		<pubDate>Thu, 19 Jun 2008 20:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-65</guid>
		<description>SeqMap (http://biogibbs.stanford.edu/~jiangh/SeqMap/) - work like ELand, can do 3 or more bp mismatches and also insdel</description>
		<content:encoded><![CDATA[<p>SeqMap (http://biogibbs.stanford.edu/~jiangh/SeqMap/) - work like ELand, can do 3 or more bp mismatches and also insdel</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by Subcutaneous</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-64</link>
		<dc:creator>Subcutaneous</dc:creator>
		<pubDate>Thu, 19 Jun 2008 04:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-64</guid>
		<description>Somehow i missed the point. Probably lost in translation :) Anyway ... nice blog to visit.

cheers, Subcutaneous.</description>
		<content:encoded><![CDATA[<p>Somehow i missed the point. Probably lost in translation <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Anyway &#8230; nice blog to visit.</p>
<p>cheers, Subcutaneous.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by zayedi</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-63</link>
		<dc:creator>zayedi</dc:creator>
		<pubDate>Tue, 17 Jun 2008 09:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-63</guid>
		<description>I'm still not so keen on using eland in situations when my reads are less than 25bp but greater than 20bp e.g with microRNAs sequenced from Solexa.  The FP question can only reliably answered on testing various scenarios  where we actually know where our reads will map.  
Something I've also seen is that you may not align a read where there are ambiguous characters around the mid-section of the short sequence read. 
Using paired-end will definitely push up FP but with higher read errors, indels, etc, the curve for PE alignment may look better.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still not so keen on using eland in situations when my reads are less than 25bp but greater than 20bp e.g with microRNAs sequenced from Solexa.  The FP question can only reliably answered on testing various scenarios  where we actually know where our reads will map.<br />
Something I&#8217;ve also seen is that you may not align a read where there are ambiguous characters around the mid-section of the short sequence read.<br />
Using paired-end will definitely push up FP but with higher read errors, indels, etc, the curve for PE alignment may look better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by John Castle</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-62</link>
		<dc:creator>John Castle</dc:creator>
		<pubDate>Thu, 12 Jun 2008 00:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-62</guid>
		<description>Has anyone tested Biostrings (in Bioconductor) or qpalma(http://www.fml.tuebingen.mpg.de/raetsch/projects/qpalma/qpalma-final.pdf) [uses Vmatch]?</description>
		<content:encoded><![CDATA[<p>Has anyone tested Biostrings (in Bioconductor) or qpalma(http://www.fml.tuebingen.mpg.de/raetsch/projects/qpalma/qpalma-final.pdf) [uses Vmatch]?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About by Deanne Taylor</title>
		<link>http://massgenomics.wordpress.com/about/#comment-61</link>
		<dc:creator>Deanne Taylor</dc:creator>
		<pubDate>Fri, 23 May 2008 17:44:09 +0000</pubDate>
		<guid isPermaLink="false">#comment-61</guid>
		<description>Thanks for all the great posts! I think our interests overlap. :)</description>
		<content:encoded><![CDATA[<p>Thanks for all the great posts! I think our interests overlap. <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by Sparks</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-55</link>
		<dc:creator>Sparks</dc:creator>
		<pubDate>Thu, 22 May 2008 07:05:59 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-55</guid>
		<description>To:ac
I can think of two drawbacks on using Eland as a preprocess to maq.
First is that you won't pick up any short indels with Eland, only SNPs so if you remove NM reads you might miss any short indel polymorphisms.
Second is that Eland can align with max of 2 mismatches where maq can handle more. Again only problem if you remove NM reads.
You could consider retaining NM reads for input to maq.</description>
		<content:encoded><![CDATA[<p>To:ac<br />
I can think of two drawbacks on using Eland as a preprocess to maq.<br />
First is that you won&#8217;t pick up any short indels with Eland, only SNPs so if you remove NM reads you might miss any short indel polymorphisms.<br />
Second is that Eland can align with max of 2 mismatches where maq can handle more. Again only problem if you remove NM reads.<br />
You could consider retaining NM reads for input to maq.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by ac</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-54</link>
		<dc:creator>ac</dc:creator>
		<pubDate>Mon, 19 May 2008 15:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-54</guid>
		<description>"The main contributor (other is read quality) to FPs is repeats or near repeats so a read has alternative alignment locations. Sometimes this will result in one alignment which may turn out to be a FP. Sometimes we’ll get multiple alignments with the same score. With MAQ, its habit of randomly choosing one alignment from a set of equal scoring alignments introduces some FP and some extra (random) TP. Other tools just report the read as having multiple alignments which some evaluations report as a FN."

We generally get around this by providing only uniquely aligned reads from Eland as input to MAQ.  The obvious drawback to this is that you may be losing some reads.  However, I haven't seen any drop in depth beyond 1X unless it is a highly repetitive region.  Fortunately we did see some FPs go away with this approach but does anyone see any drawbacks?</description>
		<content:encoded><![CDATA[<p>&#8220;The main contributor (other is read quality) to FPs is repeats or near repeats so a read has alternative alignment locations. Sometimes this will result in one alignment which may turn out to be a FP. Sometimes we’ll get multiple alignments with the same score. With MAQ, its habit of randomly choosing one alignment from a set of equal scoring alignments introduces some FP and some extra (random) TP. Other tools just report the read as having multiple alignments which some evaluations report as a FN.&#8221;</p>
<p>We generally get around this by providing only uniquely aligned reads from Eland as input to MAQ.  The obvious drawback to this is that you may be losing some reads.  However, I haven&#8217;t seen any drop in depth beyond 1X unless it is a highly repetitive region.  Fortunately we did see some FPs go away with this approach but does anyone see any drawbacks?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by Justin</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-53</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Mon, 19 May 2008 03:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-53</guid>
		<description>I am under the impression that the random assignment protocol in MAQ for repeats results in a lower mapping quality score for such assigned reads.

Can anyone here point me in a direction to understand how SNP calling is conditioned on mapping quality score for MAQ?

I couldn't find it on the MAQ page.</description>
		<content:encoded><![CDATA[<p>I am under the impression that the random assignment protocol in MAQ for repeats results in a lower mapping quality score for such assigned reads.</p>
<p>Can anyone here point me in a direction to understand how SNP calling is conditioned on mapping quality score for MAQ?</p>
<p>I couldn&#8217;t find it on the MAQ page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by MB</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-52</link>
		<dc:creator>MB</dc:creator>
		<pubDate>Fri, 16 May 2008 20:47:37 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-52</guid>
		<description>At the current version, eland itself does not do paired end alignment, but there is other scripts in the GAPipeline which can achieve this by post-processing eland output. Another script calculate mapping qualities. Unfortunately, not many people know how to use them as they have not been well documented, so far as I know.

In addition, it is easy to benchmark alignment, but it is quite hard to bechmark SNP calling with simulation. A lot of troubles that cause wrong SNPs can hardly be simulated accurately as people are simply not aware of them.</description>
		<content:encoded><![CDATA[<p>At the current version, eland itself does not do paired end alignment, but there is other scripts in the GAPipeline which can achieve this by post-processing eland output. Another script calculate mapping qualities. Unfortunately, not many people know how to use them as they have not been well documented, so far as I know.</p>
<p>In addition, it is easy to benchmark alignment, but it is quite hard to bechmark SNP calling with simulation. A lot of troubles that cause wrong SNPs can hardly be simulated accurately as people are simply not aware of them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Short Read Aligners: Maq, Eland, and Others by Sparks</title>
		<link>http://massgenomics.wordpress.com/2008/05/14/short-read-aligners-maq-eland-and-others/#comment-50</link>
		<dc:creator>Sparks</dc:creator>
		<pubDate>Fri, 16 May 2008 00:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://massgenomics.wordpress.com/?p=15#comment-50</guid>
		<description>The main contributor (other is read quality) to FPs is repeats or near repeats so a read has alternative alignment locations. Sometimes this will result in one alignment which may turn out to be a FP. Sometimes we'll get multiple alignments with the same score. With MAQ, its habit of randomly choosing one alignment from a set of equal scoring alignments introduces some FP and some extra (random) TP. Other tools just report the read as having multiple alignments which some evaluations report as a FN.</description>
		<content:encoded><![CDATA[<p>The main contributor (other is read quality) to FPs is repeats or near repeats so a read has alternative alignment locations. Sometimes this will result in one alignment which may turn out to be a FP. Sometimes we&#8217;ll get multiple alignments with the same score. With MAQ, its habit of randomly choosing one alignment from a set of equal scoring alignments introduces some FP and some extra (random) TP. Other tools just report the read as having multiple alignments which some evaluations report as a FN.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
