<?xml version='1.0'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
	<title><![CDATA[BOL: vcf2maf convert !]]></title>
	<link>https://bioinformaticsonline.com/bookmarks/view/43663/vcf2maf-convert?</link>
	<atom:link href="https://bioinformaticsonline.com/bookmarks/view/43663/vcf2maf-convert?" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/43663/vcf2maf-convert</guid>
	<pubDate>Fri, 17 Dec 2021 03:20:01 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/43663/vcf2maf-convert</link>
	<title><![CDATA[vcf2maf convert !]]></title>
	<description><![CDATA[<p>To convert a <a href="http://samtools.github.io/hts-specs/">VCF</a> into a <a href="https://docs.gdc.cancer.gov/Data/File_Formats/MAF_Format">MAF</a>, each variant must be mapped to only one of all possible gene transcripts/isoforms that it might affect. But even within a single isoform, a <code>Missense_Mutation</code> close enough to a <code>Splice_Site</code>, can be labeled as either in MAF format, but not as both. <strong>This selection of a single effect per variant, is often subjective. And that's what this project attempts to standardize.</strong> The <code>vcf2maf</code> and <code>maf2maf</code> scripts leave most of that responsibility to <a href="http://useast.ensembl.org/info/docs/tools/vep/index.html">Ensembl's VEP</a>, but allows you to override their "canonical" isoforms, or use a custom ExAC VCF for annotation. Though the most useful feature is the <strong>extensive support in parsing a wide range of crappy MAF-like or VCF-like formats</strong> we've seen out in the wild.</p><p>Address of the bookmark: <a href="https://github.com/mskcc/vcf2maf" rel="nofollow">https://github.com/mskcc/vcf2maf</a></p>]]></description>
	<dc:creator>Surabhi Chaudhary</dc:creator>
</item>

</channel>
</rss>