Inferring zygosity information from MAF
1
1
Entering edit mode
8.1 years ago
newDNASeqer ▴ 750

I've heard that we can't infer heterozygosity or homozygosity for the mutations identified in MAF files, but I noticed that the MAF file's columns 11-13 may have information for inferring this info. For example

Reference_Allele     Tumor_Seq_Allele1     Tumor_Seq_Allele2
G                    G                     C
G                    G                     C
A                    A                     C
G                    G                     A
C                    C                     T
C                    C                     A

From a comparison of Ref and Tumor alleles, can we infer that all these mutations are heterozygous? because One tumor allele is the same as Ref allele. Is this understanding correct?

MAF • 3.3k views
ADD COMMENT
1
Entering edit mode
8.0 years ago

In an ideal world, yes. These fields are meant to represent zygosity. But for TCGA MAFs, as explained in this comment: 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.

A more reliable way to infer zygosity would be to look at REF/ALT allele counts or fractions. There is no standard column that stores these numbers in TCGA MAFs, but these are some of the various column headers I have seen used: t_alt_count, t_ref_count, NVarCov, NTotCov, tumors_var_reads, tumor_ref_reads.

ADD COMMENT
0
Entering edit mode

I am still veray confused .so what's the actual meaning of Tumor-Seq-Allele1 and Tumor-Seq-Aelle2

ADD REPLY
0
Entering edit mode

The two alleles observed in the tumor sequencing data which MAF format assumes is diploid.

ADD REPLY

Login before adding your answer.

Traffic: 1269 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6