Application notes

You are currently browsing the archive for the Application notes category.

We have developed an new flow for processing Thermo RAW files that works both with the most recent XCalibur V2.1, as well as with earlier versions. This flow has been giving good results in internal testing, and we are now releasing it for beta testing to any interested, actively supported Sorcerer customer.

Thermo LTQ Velos users will have noticed the major changes to the XCalibur software that were introduced at version 2.1. The installation process is different, and requires a new component called Thermo Foundation, and some of the file names and locations have changed. All of these changes are no longer compatible with the ReAdW program that is used within the CrossOver environment by Sorcerer. One workaround which has been commonly suggested in the Thermo field is to down-rev the XCalibur used on the instrument to V2.0 and to continue using the old software for analysis. This remains a viable option, but with our newly developed solution, it is now also possible to use 2.1 RAW files on Sorcerer.

We are moving to a new spectrum extractor called msconvert (part of the ProteoWizard suite)  which works with a different version of the Thermo libraries, and for which we have developed a new integration in the CrossOver environment. We are offering this as a beta release to our in-warranty customers. This solution  entails a few Linux operations to reinstall CrossOver with the latest release, to configure the required libraries and to install a new Sorcerer workflow script; it is fairly straightforward for people comfortable with the Linux environment, or alternatively, we can do it for you if you give us remote access to your system. Please contact us at support@sagenresearch.com for more information.

We’ve developed a new Muse workflow for target-decoy analysis and false discovery rate estimation, based on our integration of DTASelect from the Yates lab. DTASelect can now use target-decoy FASTA files that are installed on Sorcerer to support its statistical analysis. It provides an easy-to-interpret results report complete with match statistics and estimated false discovery rates.

Our DTASelect on Sorcerer page on this blog has been updated to describe the target-decoy workflow, in addition to the existing material on installing, configuring and running DTASelect and the Muse script. Please visit it to get links to the latest scripts and for a detailed How-To.

Three of the world’s leading experts on MS-MS protein identification came together recently at Sage-N Research’s annual user group meeting, and presented methods and results for the techniques and tools with which they are associated:

  • Jimmy Eng, co-inventor of Sequest and developer of many proteomics tools, presented tips for Sequest analysis
  • Josh Elias, who pioneered the systematic use of decoy databases for FDR estimation, gave a talk on how to use that technique to address Peptide ID signal-to-noise.
  • Alexey Nesvizhskii spoke about the tools he co-authored, in “Peptide identification and protein inference using PeptideProphet and ProteinProphet”

Their talks were very wide-ranging and full of practical insights for the proteomics user community, and they explored the different research interests, data sets, analysis methods and workflows in the individual labs.  However, they all had this in common: they had kept a careful eye on their search settings, monitored sensitivity and error rates, and come to a common, if perhaps not entirely intuitive, conclusion: the most sensitive search and the lowest error rates for shotgun proteomics are achieved when using semi-enzymatic searches — that is, when one end, but not both, of the peptide is allowed to diverge from the expected cleavage site.

Read the rest of this entry »


Jimmy Eng (left) of University of Washington receives a thank-you gift from David Chiang after his talk.

During our Translational Proteomics 2.0 Meeting, we were privileged to have Jimmy Eng (University of Washington) give us his uncommon insights into using SEQUEST with the Trans-Proteomic Pipeline (TPP).

This talk will be invaluable for advanced users of the SEQUEST search engine for sensitive translational proteomics analysis. All active SEQUEST users should listen to this talk!

Researchers will benefit by increasing their sensitivity and decreasing their false discovery rates when identifying proteins and post-translational modifications using proteomics mass spectrometers like the Orbitrap.

Jimmy is one of the most prolific proteomics developers over almost two decades, as the co-inventor (with John Yates) of proteomic search engines and SEQUEST, as well as the developer of a number of TPP tools.

Conclusions from slides:
- Semi-tryptic searches are better
- Use monoisotopic masses for fragment ions
(Use monoisotopic masses for precursor ions if data from a high-res instrument)
- Narrow mass tolerance searches better if search considers precursor mass isotope assignment error

The talk is available at:  http://www.scivee.tv/node/11920 (31 minutes).

I recommend using the “full screen” mode so you can view the slides, which are also available as a download from the site.

Many of our customers have found DTASelect to be a very useful postprocessing tool for Sequest results, and have reported success using it with Sorcerer output. Up until now, however, these customers have generally run the tool manually on a separate desktop computer. Now we have developed a Muse script to make it easy to do this automatically, on Sorcerer itself.

See our DTASelect on Sorcerer page on this blog for a detailed How-to on installing, configuring and running DTASelect and the Muse script.

Here’s a how-to for technically advanced users who need to update the Java platform on Sorcerer. It’s not required for the base Sorcerer software, including ScaffoldBatch, but it may be necessary for Phenyx installation. Please consult our technical support staff before deciding to do the update.

These instructions assume that you have a recent 64-bit Sorcerer operating platform (either RHEL 5.2 or Centos 5-based), and that your Sorcerer software is at V3.5.

Here are the steps:

  1. Get the latest Java Development Kit (JDK)  (currently v6 update 18) from http://java.sun.com/javase/downloads/index.jsp. Click on the ‘Download JDK’ button. Get the Linux x64 platform, and download the non-rpm file which has a name like jdk-6u18-linux-x64.bin
  2. Log in as root in a terminal window and type: cd /opt
  3. Copy the file you downloaded to /opt, and unpack it:  /bin/sh jdk-6u18-linux-x64.bin
  4. Note the name of the pathname to java in the unpacked directory for use in the next step, e.g. /opt/jdk1.6.0_18/bin/java
  5. Type:  /usr/sbin/alternatives --install /usr/bin/java java /opt/jdk1.6.0_18/bin/java 2
    • This sets up a system of links from /usr/bin/java to the new installation
  6. Type: /usr/sbin/alternatives --config java
    • Enter ‘2′ at the prompt to select the newly installed alternative
  7. Check you have the latest java by typing:  java -version

(Optional) Update Firefox Java plugin:

  1. Create a plugins directory in the Firefox installation directory if the plugins directory does not exist. Please check your version of Firefox to determine the correct path to use: mkdir /usr/lib64/firefox-3.x.x/plugins
  2. Create a symbolic link to the new Java plugin. Again please check your Firefox and JRE version for the correct paths: ln -s /opt/jdk1.6.0_18/jre/lib/amd64/libnpjp2.so /usr/lib64/firefox-3.0.5/plugins/

APEX (’Absolute Proteomics Expression’) is a technique developed by Lu et al. for label-free quantitation of proteins based on MS-MS spectral counting of peptides. Unlike basic methods of this sort which suffer from variable detection probabilities that depend on the physiochemical properties of the peptides, APEX includes correction factors that predict the detection rates of the peptides for a better protein quantitation result.

There is an open source APEX Quantitative Proteomics Tool that implements this technique and that can use Sequest-based protein IDs as analyzed by the Trans-Proteomic Pipeline. Sorcerer users had the idea of using the tool in conjunction with Sorcerer, and now we have developed a workflow and MUSE script to help other users use this combination.

For more information, please read the application note ‘Sorcerer Workflow for the APEX Quantitative Proteomics Tool’.

Here are some notes from the TPP support group on using Tandem Mass Tags (i.e. similar to iTRAQ):

http://groups.google.com/group/spctools-discuss/browse_thread/thread/98dcb28f8dfa2349?hl=en

Here is Thermo’s TMT information:

http://www.thermo.com/com/cda/article/general/1,,20815,00.html

Note that TMT pre-dates iTRAQ, and is a significantly larger molecular tag. At present, iTRAQ has a larger marketshare than TMT.

MSQuant, from the Centre for Experimental Bioinformatics (DK), is a leading tool used by the Matthias Mann group and others for quantitative proteomics, and in particular, SILAC analysis. It is a Windows program that is designed to take MS-MS raw files and protein IDs in the form of a Mascot Peptide Summary Report. So up until now, if you wanted to use MSQuant, the only practical way of doing it was to have Mascot installed and run it first.

Now, however, there another option: MSQuant users can use a Sequest/TPP-based toolchain for protein ID, and using a conversion utility, they can transform the ProtXML/PepXML files from TPP into a format which MSQuant can load.  Using Sorcerer’s scripting environment, MUSE, the transform can be done automatically as post-processing of a Sorcerer search. A further advantage of doing it this way is that the Sequest/TPP toolchain needs no special preparation of the input peaklist files to extract all the information that MSQuant requires for links to the scans in the raw file.

Read the rest of this entry »

Electron transfer dissociation (ETD) is a promising dissociation technology for analyzing labile post-translational modifications (PTMs) such as phosphorylation. Unlike CID, ETD generates positively charged c and z* (z-radical) ions instead of b and y ions. There are two caveats in using standard SEQUEST for ETD tandem mass spectra:

  1. Standard c/z option doesn’t compute z* ions correctly.
  2. Standard SEQUEST allows only low charge states, and would not work for highly charged, long peptides.

It is important to note that z* ions are not the same as z ions, and have an extra hydrogen (1.08 Da monoisotopic mass). This means that the standard SEQUEST option of searching c/z ions will not search ETD spectra correctly, since the computed z ions will have the wrong mass. On SORCERER, correct c/z* ions can be obtained using user-defined static peptide terminus modifications on standard b/y searches, as described below. As well, SORCERER-SEQUEST* allows very high precursor charge states (up to +255) in order to accommodate highly charged species. Here is how to search ETD spectra using SORCERER …

1. Define peptide terminus mods that shift b/y ions to c/z* ions, and use these for ETD searches.

Define the following static peptide terminus modifications using the web interface (click “Add/edit modifications…” on the Search page, then click “New/edit modifications” on top):

  • Name: “BtoC” with Mono Mass: “17.02655″ and Type=”N-Terminus”
  • Name: “YtoZrad” with Mono Mass “-16.01872407″ and Type=”C-Terminus”

In both cases, Residue is left blank.

2. Define a new search profile that incorporates the above peptide terminus mods.

In the Search page under “(2) Choose a Search profile”, select the most similar existing search profile, then click “Edit this profile…”. Be sure to name it something different and memorable, then select the above 2 mods under “Terminus modifications” and “Static”. Select other applicable options.

3. Include a MUSE script to generate a Excel-readable tab-delimited text (TDT) summary file of the SEQUEST top peptides.

In many cases, it can be useful to have a TDT file of the SEQUEST outputs for your Excel analysis, especially for ETD analysis of purified proteins or very simple mixtures. (See note below.) Simply include the MUSE script “sorcout.mu” (part of Sorcerer PE v3.5) as follows: Click Advanced Options “Expand”, and type “sorcout.mu” into the MUSE custom script box. (From now on, any submitted search will have a “sorcout.tdt” file automatically created in the appropriate ‘output’ directory.) Save the search profile. It is now ready for SEQUEST searches on ETD spectra.

4. Try the search using this test DTA file.

Download the following ETD test DTA file and search against SwissProt.

Right Click to Download Sample ETD DTA file

If using built-in TPP’s Spectrum Viewer, simply set the display options to “c” and “z” ions (here, “z” really means “z*”). The z* ions should match pretty well against peptide “KLYNKEPSEIVELK”.

 

Note that many common post-SEQUEST probability re-scoring algorithms, such as PeptideProphet or Scaffold, are not tuned for ETD scores. From first principles, we believe that the resulting probabilities may not be wrong per se, but rather be lacking in specificity. Therefore, particularly for ETD analysis of PTMs in purified proteins or other simple mixtures, we recommend downloading the SEQUEST scores to an Excel spreadsheet for manual interpretation rather than using CID-tuned tools. *The Yates Lab’s version of SEQUEST has 2 code modifications for ETD. The first is the increased charge state (same as in SORCERER-SEQUEST). The second is exclusion of the Proline cleavage, which is not implemented in standard SORCERER-SEQUEST. However, this can be done with a MUSE post-processing step in the future if it is found to have a large effect. As always, in-warranty clients can contact our TechTeam for help on this and other advanced capabilities.

N-linked protein glycosylation is a common post-translational modification (PTMs) in many cellular processes. Atwood et al (RCMS 2005) describe a tandem mass spec-based methodology to analyze N-linked glycopeptides.

Enriched glycopeptides are treated with peptide N-glycosidase F, which removes the carbohydrate moieties from the peptide backbone. Deglycosylated peptides are analyzed with a tandem mass spec. The resulting MS/MS spectra are searched against a modified protein sequence database that allows only PTMs on N’s within the consensus sequence N-x-y, where x is any residue other than proline, and y is either serine or threonine.

To analyze this PTM on the deglycosylated peptides on SORCERER, we need to search for a monoisotopic mass shift of 0.9840 Da on N’s only in the {N[^P][ST]} consensus sequence.

To search this PTM on the SORCERER, we do the following 2 steps:

1) Create a new protein sequence database that replaces ‘N’ with ‘J’ in the consensus sequence.

2) Prepare this new sequence database for searching by defining ‘J’ to have the same mass as ‘N’ using a static modification setting on ‘J’.

3) Submit a search on SORCERER with a variable modification search on ‘J’ with a mass shift of +0.9840 Da.

Create New Protein Database

Use the MUSE script ‘nlinkglyco-fasta.mu’ (part of SORCERER PE v3.5) to create a new protein sequence database that replaces each N in the consensus sequence with J.

Simply log onto SORCERER, go to directory ‘/home/sorcerer/fasta/’ where the protein sequences are, and create a new fasta file from an existing one (for example, create ‘ipi.human_n2j.fasta’ from ‘ipi.HUMAN.fasta’) . Then use prepare this new fasta file for searching as you would any other protein sequence file.

Once you log onto the SORCERER, and type the following 2 commands (do not type the ’sorc$’ which is the SORCERER prompt):

   sorc$ cd /home/sorcerer/fasta/

   sorc$ nlinkglyco-fasta.mu < ipi.HUMAN.fasta > ipi.human_n2j.fasta

The latter command literally means to run the MUSE script using “standard input” from file ipi.HUMAN.fasta (after the ‘<’ symbol) and sending the “standard output” to the new file ipi.human_n2j.fasta (after the ‘>’ symbol).

(The script may be easily copied and modified for another consensus sequence. Contact TechTeam for details.)

Prepare Database for Searching

When the new protein sequence database is prepared for searching, assign a static modification ‘MakeN’ of -9885.95707256 Da. This will cause the final ‘J’ mass to be the monoisotopic mass of 114.04292744 Da. (The normally unused codes ‘J’ and ‘U’ are set at 10,000 Da to flag any inadvertent usage.) The resulting peptide database will be used for subsequent searching.

SORCERER Search

The search can now be submitted by creating a user-defined variable modification ‘Nlinkglyco’ with mass of 0.9840 Da on the residue ‘N’ against the new peptide database.

 

We thank Dr. Rebekah Gundry from the Van Eyk Lab at Johns Hopkins for bringing this SORCERER application to our attention!

Reference: Atwood et al (Rapid Comm Mass Spec 2005; 19: 3002-3006 DOI: 10.1002/rcm.2162)

Probability scores make search engine results easier to interpret. However, it is important to understand what they mean in order to avoid assigning more significance to the data than there is.

We continue to find researchers who mistakenly believe that there is only one correct way to compute a probability, and that the probability calculated by well-respected programs must be correct.

In fact, there can be as many different statistical models as there are modellers, and some of the best-known probability scores are simply scores and not true probabilities. The difference? Probabilities need to sum to 1 for mutually exclusive outcomes, while scores do not.

For instance, before a horse race, it helps greatly to know that your favorite horse has less than 2% probability of “not winning” (i.e. 98% probability of winning). However, it would not help nearly as much to know that your horse has a 2% probability of “matching the characteristics of a winning horse by random chance” (i.e. within the acceptable height and weight as known winning horses), since several contenders may score similarly. The first is a true probability, while the second is simply a score expressed in probabilistic terms.

Mowse/Mascot Ionscores are not Probabilities

The Mowse score, used in peptide mass fingerprinting, is a “similarity score” derived using a statistical model that calculates the “probability of matching N peaks by random chance”. It does so by assigning such a probability value to each matched m/z peak using a training set ofprotein sequences, and multiplying all such probability values to compute the composite probability P, which for convenience is expressed as -10logP.

It is a useful scoring method that provides a higher score when there are more matched peaks or when a peak is judged to be more rare.

However, the Mowse score is a score and not a true probability, since there is no requirement that a higher score for one protein sequence will reduce the score for other protein sequences.

The Mascot ionscore is directly derived from Mowse. It uses the Mowse scoring methodology on each ion series individually, and picks the highest score among all the ion series as the composite score. Like Mowse, Mascot assumes that all the m/z peaks in an ion series (say all the b+ ions) are independent, which is a mathematical simplification that is clearly inconsistent with tandem mass spec data.

The Mascot score has proven to be especially useful for scoring tandem mass spectra with high-accuracy (< 10 ppm) fragment mass data, where the significance of each matched peak is high. (The Mascot model does not vary the assigned peak probability with fragment mass accuracy, which may limit its theoretical applicability for ion trap spectra of poorer quality.)

While Mowse and Mascot ionscores have proven their usefulness where they apply, they are not true probabilities and should not be treated as such. For example, it is meaningless to talk about error bars when using these values.

This is true for other useful statistically based similarity scores as well, such as for phosphorylation site localization (Beausoleil et al, Nature Biotech 2006 doi:10.1038/nbt1240) and for combined MS2/MS3 scoring (Olsen & Mann, PNAS 2004 Sep 14).

Neither are P-Values

The P-Value (and its close cousin the E-Value) is a useful statistical construct adopted from the genomics world. Unlike a similarity score that measures how close the top peptide candidate matches the measured spectrum, the P-Value is a “dissimilarity score” that measures how different the top peptide candidate is from the rest of the search space at large. (For those familiar with SEQUEST, the parameter “deltaCn” does a similar function, albeit in a less sophisticated manner and is not probabilistic in value.)

We believe P-Values and E-Values were first introduced into proteomics with the X! Tandem search engine (Fenyo and Beavis, Anal Chem 2003, 75).

The E-Value is an empirically derived “expected value” of how many peptides can achieve a particular score by random chance for a particular spectrum, which is computed by extrapolating the decaying exponential distribution of all the peptide scores for that spectrum. The P-Value is the probability analog computed by dividing the E-Value by the number of candidates.

(It is interesting to note that the genomics field has a more rigorous approach to statistics than proteomics today, and would not mistakenly call similarity scores or P-Values “probabilities.” It helps that top genomics practitioners like Stephen Altschul and Eric Lander got their math PhDs long before they did much biology.)

Like the similarity score, the P-Value is also a score and not a probability.

PeptideProphet computes Probabilities

Unlike the similarity scores and “dissimilarity scores” above, the values computed by the PeptideProphet algorithm (Keller, Nesvizhskii, et al, Anal Chem 2002, 74) from rescoring peptide search engine results from SEQUEST, Mascot, X!Tandem, and now Phenyx are probabilities.

This by itself doesn’t mean that the computed values are necessarily correct (depends on the data and underlying assumptions), or that there cannot be other equally valid ways to model the statistics. However, at least the definition matches what is expected of a probability.

Much like a teacher may put the test scores on a curve to convert numerical scores into a more meaningful measure, PeptideProphet assumes the score distribution arises from a large “false positive” distribution superimposed on a smaller “true positive” distribution, and uses curve-fitting to compute the resulting probabilities. Where the FP and TP curves intersect is the 50% probability point.

As with any other statistical tool, its results are only as valid as its assumptions. There is always a chance of “garbage-in, garbage-out,” and the results depend on clean, well-fitting data.

PeptideProphet was originally designed to work with SEQUEST, where a “discriminant score” is derived by combining the similarity score (XCorr) and the “dissimilarity score” (deltaCn). Ideally, the discriminant score should incorporate both elements (the case for rescoring SEQUEST results), so that the highest probability is assigned where (1) the top candidate very closely matches the spectrum and (2) the top candidate is very dissimilar from the others in the search space.

It has since been adapted for Mascot (albeit using only the similarity score) and other search engines. PeptideProphet is part of the Trans-Proteomic Pipeline, while the same algorithm has been re-implemented in commercial products like Scaffold and Elucidator.

It should be noted that a probability rescoring at the peptide assignment stage is not the only way to filter the search engine results. Other methods, notably using decoy (reversed) protein sequence databases, can be employed with parameter-based filtering, such as with DTASelect from the Yates Lab. These methods allow the final false positive rates to be computed without requiring individual peptide assignments to be probabilistically determined. In the future, we expect that many of these different methodologies can be integrated to achieve the highest level of results quality in advanced “Proteomics 2.0″ analysis driving the upcoming “BiotechIndustrial Revolution.”

The Ascore algorithm was developed by the Gygi Lab at Harvard for phosphorylation site localization. It re-analyzes phosphopeptide search engine results to assign a confidence value to each phosphorylated site.

http://ascore.med.harvard.edu/

Sage-N Research offers a commercially developed and supported version, called SORCERER-ASCORE, that is integrated into the Sorcerer systems.

Reference

Beausoleil et al, “A probability-based approach for high-throughput protein phosphorylation analysis and site localization”, Nature Biotech, 10/06, doi:10.1038/nbt1240.

Steve Gygi (Harvard Medical School) writes…

We don’t find this to be a problem anymore. There used to be two problems:1) the precursor mass in the header was sometimes from the pre-scan (15K resolution) in the Orbi and not the one in the actual MS scan.

2) Sometimes (for large peptides) the second isotope (1st carbon-13 isotope peak) was
chosen for MS/MS (because its larger for peptides with masses above 1800).

Both of these problems are fixed by Xcalibur software when the radio checkbox is checked under the “exclude charge states” tab that says “Undetermined charge states.”

The mass spectrometer doesn’t collect MS/MS information if it doesn’t know the charge state. If it knows the charge state, then the right information gets put into the headers almost all the time. We always check that box now.

Finally, one can always check how well this works by just doing a search at 1.1 Da tolerance (instead of 50 ppm) and then examining the PPM values for the best-scoring peptides. Usually only one out of a hundred or so will be right (very high Xcorr) and have a PPM value that corresponds to exactly a 1.003355 Da shift.

Jimmy Eng (University of Washington) writes …

Regarding the question of ReAdW vs. extract_msn and the observation that ReAdW masses are almost always +10 to +15 ppm higher than extract_msn:

The current version of ReAdW is being distributed with the Trans-Proteomic Pipeline (TPP) and can also be individually downloaded directly from here:
http://sourceforge.net/project/showfiles.php?group_id=69281&package_id=68160

However, there is an imminent TPP release (3.5.1) which will include a new ReAdW which is the first update for this tool in well over a year. The new ReAdW incorporates a fix to profile scans that get centroided. Previously, centroided peaks were off by both m/z and intensity and we recently became aware of a proper Thermo function call to extract correct centroided data for Orbi/FT data using their Xcalibur Developer’s Kit (XDK) API. This new ReAdW also supports zlib peak compression which will generate in the range of 20-40% smaller files.

There is no change to the precursor mass determination though. For scans with a more precise precursor mass available, ReAdW reports what it gets out of the Thermo API (Monoisotopic M/Z Trailer Extra Value; I presume it’s the same accurate mass also visible in the scan header when viewing a spectrum in Qual Browser). There appears to be newer Thermo function calls to extract (more accurate?) precursor masses but the latest ReAdW continues to use the “Trailer Extra Value” masses for now. On one dataset I tested, the newer precursor mass function generated more accurate precursor masses within the high quality identifications. It had precursor mass accuracies in the range of 0-6PPM with distribution centered around 2PPM versus an error range of 0-12PPM with distribution centered around 4PPM for the “Trailer Extra Value” masses. But testing by others showed that there were enough scans where the new mass function failed so the precursor mass determination is left as-is for the time being.

Read the rest of this entry »

According to Mike Senko of Thermo, there are two complexities with determining the precursor mass using the Extract-MSn program within Bioworks.The first is the occasional +1 Da that is included in the reported precursor monoisotopic mass. The second is the random mass error that is estimated to be between 5 to 10 PPM.

In a Orbitrap or FT acquisition, the instrument tries to determine the monoisotopic m/z while it picks precursors based on abundance. If the m/z can be confidently inferred, it will be listed in the scan header (also called the trailer) as “Monoisotopic M/Z”. If it cannot, a ‘0′ is listed.

For the first complexity, the occasional extra +1 Da in the precursor mass arises when Extract-MSn is used to generate the peaklist and a ‘0′ is encountered. In those cases, the mass of the most abundant isotopic peak is chosen, which is the M+1 peak for precursor masses higher than about 1700 Da. Therefore, the extra +1 Da arises not from the instrument itself, but from the way Extract-MSn extracts the information. The potential for this error still exists today.

For the second complexity involving the random mass error, the issue is that the analytical scan is not done when the data dependent scan decisions are made, which is during the first 25% of the time domain signal (called the Preview Scan). For this reason, the listed masses for the precursor and isotopic M/Z will not match those values in the analytical scan. In that case, Extract-MSn will go back to the analytical scan to extract the more accurate values. This capability is reportedly in Extract-MSn version 3.2 or later.

[Editor’s Note: Mike is a research scientist at Thermo responsible for optimizing the interface between the LTQ and Orbitrap/FT sections of hybrid instruments. We thank Mike for providing the above information, which we summarized for this newsletter.]