z-logo
Premium
Comparing Computational Methods for Identification of Allele‐Specific Expression based on Next Generation Sequencing Data
Author(s) -
Liu Zhi,
Yang Jing,
Xu Huayong,
Li Chao,
Wang Zhen,
Li Yuanyuan,
Dong Xiao,
Li Yixue
Publication year - 2014
Publication title -
genetic epidemiology
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.301
H-Index - 98
eISSN - 1098-2272
pISSN - 0741-0395
DOI - 10.1002/gepi.21846
Subject(s) - biology , allele , reference genome , genetics , computational biology , genome , identification (biology) , genomics , transcriptome , gene , gene expression , botany
ABSTRACT Allele‐specific expression (ASE) studies have wide‐ranging implications for genome biology and medicine. Whole transcriptome RNA sequencing (RNA‐Seq) has emerged as a genome‐wide tool for identifying ASE, but suffers from mapping bias favoring reference alleles. Two categories of methods are adopted nowadays, to reduce the effect of mapping bias on ASE identification—normalizing RNA allelic ratio with the parallel genomic allelic ratio (pDNAar) and modifying reference genome to make reads carrying both alleles with the same chance to be mapped (mREF). We compared the sensitivity and specificity of both methods with simulated data, and demonstrated that the pDNAar, though ideally practical, was lower in sensitivity, because of its lower mapping rate of reads carrying nonreference (alternative) alleles, although mREF achieved higher sensitivity and specificity for its efficiency in mapping reads carrying both alleles. Application of these two methods in real sequencing data showed that mREF were able to identify more ASE loci because of its higher mapping efficiency, and able to correcting some seemly incorrect ASE loci identified by pDNAar due to the inefficiency in mapping reads carrying alternative alleles of pDNAar. Our study provides useful information for RNA sequencing data processing in the identification of ASE.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here