Format

Send to:

Choose Destination
See comment in PubMed Commons below
Anal Biochem. 2009 May 15;388(2):192-203. doi: 10.1016/j.ab.2009.03.005. Epub 2009 Mar 9.

Numerical bias estimation for mass spectrometric mass isotopomer analysis.

Author information

  • 1Computational Department, Genomatica Inc., 10520 Wateridge Circle, San Diego, CA 92121, USA. tyang@genomatica.com

Abstract

Mass spectrometric (MS) isotopomer analysis has become a standard tool for investigating biological systems using stable isotopes. In particular, metabolic flux analysis uses mass isotopomers of metabolic products typically formed from (13)C-labeled substrates to quantitate intracellular pathway fluxes. In the current work, we describe a model-driven method of numerical bias estimation regarding MS isotopomer analysis. Correct bias estimation is crucial for measuring statistical qualities of measurements and obtaining reliable fluxes. The model we developed for bias estimation corrects a priori unknown systematic errors unique for each individual mass isotopomer peak. For validation, we carried out both computational simulations and experimental measurements. From stochastic simulations, it was observed that carbon mass isotopomer distributions and measurement noise can be determined much more precisely only if signals are corrected for possible systematic errors. By removing the estimated background signals, the residuals resulting from experimental measurement and model expectation became consistent with normality, experimental variability was reduced, and data consistency was improved. The method is useful for obtaining systematic error-free data from (13)C tracer experiments and can also be extended to other stable isotopes. As a result, the reliability of metabolic fluxes that are typically computed from mass isotopomer measurements is increased.

PMID:
19275875
[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Icon for Elsevier Science
    Loading ...
    Write to the Help Desk