Tutorial: Working with MAF files (Mutation Annotation Format) from the TCGA (The Cancer Genome Atlas)
87
gravatar for Cyriac Kandoth
4.1 years ago by
Cyriac Kandoth4.5k
Memorial Sloan Kettering, New York, USA
Cyriac Kandoth4.5k wrote:

Update: (2/8/2017) This tutorial applies to TCGA MAFs in the GDC Legacy Archive. Most of this tutorial is still valid, but I'll need to update some notes and broken links.

Purpose

For folks familiar with the VCF format, TCGA's MAF files can be quite a pain to work with. You might just download the latest MAFs, pull loci and alleles for each variant, and redo annotations with ANNOVAR, snpEff, or Ensembl's VEP. Problem solved, right? Nope. You don't know the half of it! There are lots of caveats you should know about, and I try to document them below. Most of these caveats are handled with safe solutions in the MAFs at this page, and the specificity of variant calls are made more comparable across MAFs, at this page.

How TCGA MAFs are made

  1. Tumor-specific Analysis Working Groups (AWGs) take the auto-generated variant calls from the Genome Sequencing Centers (GSCs), and remove false-positive variants, or recover those missed by the GSCs. This is either done manually by experts, or by automated scripts or filters based on the extensive domain knowledge of said experts. So the quality of variant calls may differ wildly between TCGA GSCs and AWGs, and across samples as the pipelines get better over time
  2. In some tumor-types, and for some subsets of samples, mutations called from the first-pass of sequencing (usually exome-seq), are targeted by custom capture arrays, and re-sequenced. This results in much higher read-depths for the purpose of validating first-pass calls, for more accurate variant allele fractions (VAFs), or for finding calls that were missed
  3. The GSC-generated or AWG-curated MAFs are uploaded to the DCC under folders nested as */gsc/*/*/mutations/

Finding the correct MAF to use

The Ding lab at TGI, WashU track the best available MAFs in this spreadsheet for use in MuSiC analyses. TCGA tumor-types COAD (Colon) and READ (Rectum) are treated as the same tumor type "COADREAD" (Colorectal), resulting in 19 MAFs across 20 tumor-types. At this link, folks at Broad Institute maintain a list of MAFs to feed into Firehose

MAF-format caveats

  1. The 16th column in a MAF lists tumor sample barcodes in the form "TCGA-02-0021-01A-01D-0002-04". Different barcodes may be used for the same sample, if they were sequenced several times or by several GSCs. Be careful not to treat their variants as observed recurrence across patients
  2. Reducing the tumor IDs to the form "TCGA-XX-XXXX-XX" is useful to enumerate the real number of tumors studied, or to de-duplicate variants from the same tumor. And reducing IDs to the form "TCGA-XX-XXXX" helps to enumerate the distinct patients in the cohort. But note that MAF files will not list IDs of samples with zero reported mutations. So it helps to have a separate list of all samples in the cohort
  3. The breakdown of a TCGA barcode is here and their designations are tabulated here
  4. To re-annotate variants in a MAF (e.g. using maf2maf.pl), you'll only need column 4 for the reference genome used, columns 5-7 for genomic loci, and columns 11-13 for reference and variant alleles
  5. The variant alleles in columns 12 and 13 are not always reliable to determine zygosity (some variant callers or curators make bad assumptions). Whichever allele differs from column 11 (the reference allele) is the variant allele, and it may either be heterozygous or homozygous
  6. Almost everything in the TCGA MAFs are from targeted exome sequencing. 50 of the 200 LAML tumors were whole-genome sequenced, and the putative calls were targeted with custom capture arrays
  7. Per-sample coverage data can be found here. Genomic loci with sufficient depth to detect variants are listed in BED files, which can be used to correct for variant caller sensitivity. Exome-seq coverage can differ quite a bit between samples, and across the exome, as it has improved over time. But more importantly, several proprietary exome-capture technologies have been used across TCGA, with different targeted regions. And the 3 TCGA GSCs are not very transparent about their internal protocols either! So please make use of this coverage data if you can. It was not easy to collect/clean/liftover!

Tumor-type caveats

These caveats may change over time, but I'm listing what I know as of today, August 9th, 2014:

  1. The latest MAFs for PAAD, PRAD, THCA, and UCS are auto-generated GSC MAFs, and have not yet gone through AWG curation. Avoid these if your analysis is too sensitive to false positives
  2. Four of the tumors in the BRCA MAF are actually metastases (TCGA-XX-XXXX-06) of four other primary tumors (TCGA-XX-XXXX-01) in the same MAF. Be careful not to treat their variants as observed recurrence between different patients
  3. Similarly, the SKCM MAF has 2 metastases for 2 other primary tumors. But note that most samples in SKCM (melanoma) are from metastases, because primary SKCM tumors are hard to pinpoint
  4. Of the 200 sequenced LAML tumors, 3 had no reported exonic mutations. So you won't find them listed in the MAF. This is important to note, when measuring something like mutation frequency across samples. Of all the TCGA tumor types, LAML (Acute Myeloid Leukemia) has the lowest overall mutation frequency, and several known/suspected drivers are in the regulome. This was also the motive behind doing whole-genome sequencing for 50 of the 200 LAML tumors, while everything else in TCGA went through exome-seq
ADD COMMENTlink modified 3 months ago • written 4.1 years ago by Cyriac Kandoth4.5k
2

This is fantastically useful - thanks for posting.! Do you have anything similar for the copy-number data?

ADD REPLYlink written 4.1 years ago by david.wettmann30

No. But there are definitely fewer caveats to the copy-number data because it was all generated by the same folks, and analyzed by them too. You can find more at Broad Institute's copy number portal, which pulls data from Firehose runs.

ADD REPLYlink modified 2.5 years ago • written 4.1 years ago by Cyriac Kandoth4.5k
1

Thanks Cyriac. I was interested in your point #5 in "MAF-format caveats" about not always being able to call zygosity based on the variant alleles in columns 12 and 13. Would you be able to give a bit more detail about why this is the case please?

Thanks, Dave

ADD REPLYlink written 4.1 years ago by david.wettmann30

It's often assumed that somatic point mutations or small indels in cancer are infrequent enough, that they almost always result in a homozygous site becoming heterozygous. Combine that imperfect assumption with someone's good old fashioned indifference, and you get MAF columns 12 and 13. :)

ADD REPLYlink modified 4.1 years ago • written 4.1 years ago by Cyriac Kandoth4.5k

Thanks so much for this! Very very useful.

ADD REPLYlink written 3.3 years ago by Danielk530
1

Thanks for this write-up, it has been very helpful.  Regarding the CNV data, do you happen to know what the naming convention is for samples?  I can't figure out what the relationship is between mutation sample ids and CNV sample ids.  

ADD REPLYlink written 3.0 years ago by gregorymcinnes10

See again the breakdown of sample barcodes over here. CNV data will be generated from a different portion of the same sample... meaning a different barcode altogether. To match mutation data to CNV data for the same sample, reduce barcodes to the form TCGA-XX-XXXX-XX.

ADD REPLYlink modified 3.0 years ago • written 3.0 years ago by Cyriac Kandoth4.5k

Thanks for this wonderful post Cyriac!

I have been learning about the MAF Files very recently and I was wondering what is the correct MAF File to work with when I download the data from TCGA. I have downloaded the somatic mutation data for KIRP and see that there are different MAFs from Broad Institute - 1) BI__IlluminaGA_DNASeq , 2) BI__IlluminaGA_DNASeq_automated and 3) BI__IlluminaGA_DNASeq_curated . Why are these different and what to do you think is the best one to go ahead with the analysis.

Thanks, Yaseswini 

 

ADD REPLYlink written 2.6 years ago by yaseswini.neelamraju0

You're very welcome! See my answer below to Charles explaining why there are different MAFs. And see the spreadsheet from Ding lab in my post above for the "subjective best" MAF to use per tissue type, or the Broad Institute's MAF Dashboard for the "automated best" MAF to use. In a separate tab in the Ding lab spreadsheet, you'll also find the MAF curator's contact info. But in the case of KIRP, they'll likely point you to the HGSC MAF. If you want to choose one of the Broad MAFs, I'd go with one that says it's curated. They have a DESCRIPTION.txt that explains the differences between their uploaded MAFs.

ADD REPLYlink modified 2.6 years ago • written 2.6 years ago by Cyriac Kandoth4.5k

Hi @ Cyriac Kandoth

I got a bit confused after reading the entire thread. I want to do some analysis with mutation data so I think this thread will be the best thread to put my query. I recently downloaded the MAFs which you provided the link here, but I see for all the different diseases there are different MAF files , which is obviously fine. But I want to know is there any file which catalogs all somatic mutations across major types of cancer? Or do I have to take in account all the MAF files and then from there create a MAF or a mutation file that will give me an overall data file that contains mutations across all cancer types. I actually want a somatic mutation file across most cancer type which I will use to map the mutations for my samples. Is there any such kind of file in TCGA. I could not find such from TCGA. If you can share some light.

ADD REPLYlink written 2.5 years ago by vchris_ngs3.2k

Several papers here have merged together TCGA MAFs for downstream analyses, but I worry that you might be using it wrong. Most cancer driving mutations do not share the same genomic locus between samples. Start a new post on Biostars detailing your project goals, and we can help. Be sure to tag it with keywords tcga and maf.

ADD REPLYlink written 2.5 years ago by Cyriac Kandoth4.5k

Hi Cyriac, thanks for this post. It is now 2016, do you have an updated version of the MAF files, I believe TCGA have more samples now.

ADD REPLYlink written 10 months ago by tangming20052.0k
4
gravatar for Charles Warden
3.4 years ago by
Charles Warden4.8k
Duarte, CA
Charles Warden4.8k wrote:

This is a big help.

Also, I've noticed that TCGA seems to have done a better job with presenting the public data for a given disease. For example, check out this site for colorectcal data:

https://tcga-data.nci.nih.gov/docs/publications/coadread_2012/

That said, I'm wondering what is the difference between the Broad and WashU MAF files? Why would you use one over the other? For example, there are two MAF files available to download for endometrial cancer (in addition to the somatic MAF file):

https://tcga-data.nci.nih.gov/docs/publications/ucec_2013/

FYI, I am accessing these links from this main page:

https://tcga-data.nci.nih.gov/docs/publications/

ADD COMMENTlink written 3.4 years ago by Charles Warden4.8k
6

Some backstory... TCGA has 3 DNA-sequencing centers (GSCs): WashU, Broad, and Baylor. And there are at least 4 centers that do automated mutation calling: UCSC, Broad, WashU, and Baylor. The tumor-specific AWGs are varied multi-institutional teams with experience in transcriptomics, proteomics, epigenetics, tumor-type experts, etc... but the somatic mutation analyses of each tumor-type are always led by one of the 3 GSCs. See the "GSC Analysis Leads" in this spreadsheet.

Originally, the plan was that 1 or more GSCs would do the sequencing for a tumor-type, and at least 3 centers would generate mutation calls in VCF format and pass those to the AWGs. The AWGs would then consolidate/curate these VCFs to shortlist the high confidence mutations, and annotate them to gene names in a final MAF that is used for subsequent analyses. As it turns out, that plan was all too idealistic!

None of the centers had much experience with VCFs, and inevitably wrote their pipelines around MAFs or some internal tab-delimited format. Only recently, did they modify their mutation calling pipelines to use VCFs at the core. VCFs have useful information straight from the variant callers that are important during curation... like read-depths, variant allele fractions, sequence context, reasons for filtering, genotyping info, etc. They may also contain all candidate calls making it easier to recover false negatives. All these are lost when you convert to a MAF. Some GSCs added these as additional columns to the tab-delimited MAF format, but there was no standard for column headers... which made it more of a headache when writing parsers.

As of today, only a lead GSC does the sequencing and mutation calling for each tumor-type. Other centers are invited to participate in "network mutation calling", but that doesn't always happen, and if it does, their calls may not make it in time to be incorporated into the final manuscript-ready MAF.

So Broad's MAF for UCEC that you pointed to here, is an auto-generated MAF straight out of their pipeline, that prioritizes sensitivity over specificity. While WashU's UCEC MAF went through a ton of manual and automated curation. UCSC also did mutation calling on this dataset, but they generated VCFs which are stored in protected access. WashU was the GSC analysis lead in UCEC, and made the decision to stick with the strictly curated WashU MAF for the final manuscript. Considering the high mutation rate of UCEC, it would have taken too much effort to curate the tens of thousands of additional calls from Broad/UCSC... a majority of which were at allele fractions <10%, or were indels near homopolymers. Some of those indels were important, and WashU restored them manually. Indels near homopolymers are associated with MLH1 loss, common in UCEC.

Another important difference between Broad/WashU MAFs is in the transcript annotation database and the gene names used, and in the selection of an isoform to map a variant's effect onto. Broad uses Oncotator on GAF while WashU uses their annotator on Gencode. As of June 2014, TCGA standardized to Gencode, and Broad has an internal version of Oncotator using Gencode. If you're looking for TCGA MAFs with standardized annotations and gene names try these. Or run your downloaded TCGA MAFs through the maf2maf.pl script in the vcf2maf repo.

ADD REPLYlink modified 18 months ago • written 3.4 years ago by Cyriac Kandoth4.5k

@ Charles: Great question.

@all: this video from this years TCGA Symposium about "Multi-Center Mutation Calling in TCGA" might be very informative, for those who are wondering about the multple MAF files and how they are produced. BTW: seems, that this is a great meeting. Great to have all talks online. 

@ Cyriac: you mentioned, that you "track the best available MAFs in this spreadsheet". I guess David Wheeler in the above video very briefly mentions that on slide 20 (15:15), but doesnt say anythiong about that. My question is: how are your "best available MAFs" produced?

ADD REPLYlink written 2.8 years ago by Sebastian Boegel370
1

Unfortunately, there is no good automated way to choose the best available TCGA MAF for a tumor type. Broad Institute has an automated way to fetch the latest curated MAF for use in their Firehose analyses. But the latest is not always the best. I keep the spreadsheet updated by staying posted on what the AWGs are up to, but I've been out of the loop recently. So the safest way is to email the AWG MAF curators listed in my spreadsheet, and wait for a reply. Most of them are quite responsive if you keep your email *really* short and specific.

ADD REPLYlink written 2.8 years ago by Cyriac Kandoth4.5k

Thanks for answering so fast and keeping trakc of all the information. Last question: are the MAFs in your spreadsheet the ones you used in your Nature publication?

ADD REPLYlink written 2.8 years ago by Sebastian Boegel370

Yea, but from an older version of the spreadsheet, and only 12 of the 20+ tumor types could be used in our paper because of a TCGA publication embargo. A data freeze of the MAFs used in the paper, and subsequent cleanup/filtering steps can be found here.

ADD REPLYlink written 2.8 years ago by Cyriac Kandoth4.5k
1
gravatar for Sebastian Boegel
3.1 years ago by
Germany
Sebastian Boegel370 wrote:

Thank you for the tutorial. Maybe this question is a bit off-topic, but does anyone know a nci wiki page (or so) where they describe how the called and subsequently validated somatic mutations?

All i found is:

https://wiki.nci.nih.gov/display/TCGA/Genome+Sequencing+Center

which doesnt help much.

Thank you

ADD COMMENTlink written 3.1 years ago by Sebastian Boegel370
1

The somatic calling methods used by the 3 TCGA GSCs have evolved a lot over the years. Sensitivity/specificity of the calls will differ between tumor-types, but is generally consistent across samples of the same tumor-type - Two known exceptions are OV and COAD/READ where multiple GSCs performed sequencing and/or variant calling.

WashU makes it's code public, so skimming through the POD of this module might give you some insight into their latest workflow. But in general, I would recommend reading the method's section of each marker paper listed here.

ADD REPLYlink modified 2.1 years ago • written 3.0 years ago by Cyriac Kandoth4.5k

Thanks a lot for your helpful answer.

ADD REPLYlink written 3.0 years ago by Sebastian Boegel370
1
gravatar for dario.r
2.6 years ago by
dario.r70
Italy, Trento, CIBIO
dario.r70 wrote:

I've got a question concerning caveat #2:
since samples with no reported mutations are not listed, where can I find the list of the entire cohort used?
Currently I'm using this list https://www.synapse.org/#!Synapse:syn416851 but I haven't found anything saying that all those samples have been analysed to detect mutations. 

ADD COMMENTlink written 2.6 years ago by dario.r70
1

Unfortunately, there's no simple way, but you shouldn't break your head over it, like I did! If a sample has zero mutations reported, it was most likely due to poor exome-sequencing coverage.

The closest to an ideal solution would be to query or browse CGHub for all TCGA samples with WXS/WGS, but then you have to find out which samples were kicked out later by the AWG, because of a QC failure or low-level contamination.

If you just need something quick, you could use sample IDs from the per-sample coverage data collected here.

ADD REPLYlink modified 2.6 years ago • written 2.6 years ago by Cyriac Kandoth4.5k

OK, thank you very much for the quick and comprehensive reply.

ADD REPLYlink written 2.6 years ago by dario.r70

No worries. I also just remembered this nice GUI interface to lookup TCGA sequence data on CGHub. Here's a URL query that returns all WGS/WXS BAMs for TCGA AML. Deduplicate the sample IDs in the form TCGA-XX-XXXX-XX, and you should find a few more than just the 197 IDs seen in the TCGA AML MAF.

ADD REPLYlink modified 2.6 years ago • written 2.6 years ago by Cyriac Kandoth4.5k
0
gravatar for sviatoslav.kendall
2.2 years ago by
United States
sviatoslav.kendall400 wrote:

Can anyone explain what exactly is meant by "Nonstop_Mutation", a value seen in the "Variant_Classification" column of an MAF file? I don't understand how it would be different from a missense mutation or perhaps a silent mutation...

ADD COMMENTlink written 2.2 years ago by sviatoslav.kendall400
1

Always better to open a new thread for questions as specific as yours. Makes it easier for others to find it. Nonstop_Mutation is the same as stop_lost explained here.

ADD REPLYlink modified 2.2 years ago • written 2.2 years ago by Cyriac Kandoth4.5k
0
gravatar for t.kuilman
23 months ago by
t.kuilman280
Netherlands
t.kuilman280 wrote:

Hi guys,

Maybe I am missing something but it seems to me to be untrivial to convert a MAF file to a VCF one. In my MAF files, frameshift insertions are represented for instance like this:

9       107602665       Frame_Shift_Ins .       C       .       PASS    5d11fd9e-86e8-4e08-96cb-9ca66a7fa283

Instead, in vcf-files the annotation would include the information of the actual base at position 107602665 like for instance this

9       107602665  Frame_Shift_Ins      A       AC       .       PASS    5d11fd9e-86e8-4e08-96cb-9ca66a7fa283

Annovar will not digest vcf files created straight from MAF file format because of this discrepancy. The only thing I would like to do is to annotate the variants (preferably using Annovar). Does anyone know how to achieve this?

Thank you very much,

Thomas

ADD COMMENTlink written 23 months ago by t.kuilman280
Please create a new question on biostars, because comments go unnoticed. Anyway, use the maf2vaf script at http://github.com/ckandoth/vcf2maf
ADD REPLYlink written 23 months ago by Cyriac Kandoth4.5k
0
gravatar for qwertyuiop201320142015
23 months ago by

hello ,i am sorry to disturb you . I using the genome music calc-covg ,when I read the source code of calcovg.c,I have some problems .

can you  tell me the meaning of these parameters of this function?thank u

uint32_t tid, uint32_t pos, int n, const bam_pileup1_t *pl, void *data

static int pileup_func_1( uint32_t tid, uint32_t pos, int n, const bam_pileup1_t *pl, void *data ) \
{
  pileup_data_t *tmp = (pileup_data_t*)data;
  if( pos >= tmp->beg && pos < tmp->end ) /
  {
    // Count the number of reads that pass the mapping quality threshold across this base  /
    int  mapq_n = 0;i,
    for( i = 0; i < n; ++i )
    {
      const bam_pileup1_t *base = pl + i;
      if( !base->is_del && base->b->core.qual >= tmp->min_mapq )
        mapq_n++;
    }
    tmp->bam1_cvg[pos - tmp->beg] = ( mapq_n >= tmp->min_depth_bam1 );  //??
  }
  return 0;
}

 

who can tell me the meaning of these parameters of this function?thank u

uint32_t tid, uint32_t pos, int n, const bam_pileup1_t *pl, void *data

ADD COMMENTlink written 23 months ago by qwertyuiop2013201420150
2

Please post a new question on biostars. The point of the forum is to help other people who have the same question as yours.

ADD REPLYlink written 23 months ago by Cyriac Kandoth4.5k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1062 users visited in the last hour