Non-targeted FIA-MS analysis with Thermo Orbitrap

This tutorial walks you through the workflow for analyzing non-targeted FIA-MS data starting from input file generation, to processing the data in SmartPeak, to reviewing the data in SmartPeak, to reporting the results for later use.

Objectives

1. Obtaining the SOP for the workflow.

2. Choosing a data set for demonstrating the workflow.

3. Creating an optimized SmartPeak input templates for running the workflow.

The Workflows include

1. Defining the accurate mass search database

2. Processing Unknowns

3. Reviewing the results

Steps

The tutorial includes the following steps :

1. Setting up the input files

   The data set used can be found here FIAMS FullScan Unknowns.

   The dataset includes a CHEMISTRY folder which contains HMDB (Human Metabolome Database) mapping files organized as follows:

   1. HMDB2StructMapping.tsv

   This tab seperated file contains mapping of HMDB IDs, IUPAC Name, Compound Summary (Synonyms), Canonical SMILES and InChl.

   1. HMDBMappingFile.tsv

   This tab seperated file contains the Monoisotopic Molecular Weight and the Chemical Formula mapped to their respective HMDB ID.

   1. negative_adducts.tsv

   This file contains negative ion modes including the charge.

   1. positive_adducts.tsv

   This file contains positive ion modes including the charge.

   The above files provided in the example are appropriate for applications involving human serum and other biosamples. For applications involving other organisms such as bacteria (e.g., E. coli), the use of organism specific databases are recommended to reduce the number of false positives. See FIA_MS_database_construction.ipynb for an example notebook demonstrating how to convert the metabolites in a genome-scale reconstruction to SmartPeak accurate mass mapping files.

   Furthermore, the parameters.csv file contains the following settings for this workflow:

   FIAMS Settings in parameters.csv

   function	name	type	value	default	restrictions	description	used_	comment_	comparator
   FIAMS	acquisition_start	float	0	0	0	The start time to use when extracting out the spectra windows from the MSExperiment	TRUE
   FIAMS	acquisition_end	float	30	30		The end time to use when extracting out the spectra windows from the MSExperiment	TRUE
   FIAMS	resolution	float	12000	120000		The instrument settings: resolution	TRUE
   FIAMS	max_mz	float	1500	1500		Maximum mz	TRUE
   FIAMS	bin_step	float	20	20		The size of the step to recalculated the bin size used for adding up spectra along the time axis	TRUE

2. Defining the workflow in SmartPeak

For FIAMS FullScan Unknowns analysis, the following steps are saved into the workflow.csv file. Alternatively, steps can be replaced, added or deleted direclty from SmartPeakGUI within the “workflow” tap in the right pane. A detailed explanation of each command step can be found in Workflow Commands.

• LOAD_RAW_DATA

• EXTRACT_SPECTRA_WINDOWS

• MERGE_SPECTRA

• PICK_MS1_FEATURES

• SEARCH_ACCURATE_MASS

• STORE_ANNOTATIONS

• STORE_FEATURES

• ESTIMATE_FEATURE_BACKGROUND_INTERFERENCES

• STORE_FEATURE_BACKGROUND_ESTIMATIONS

• FILTER_FEATURES_BACKGROUND_INTERFERENCES

• MERGE_FEATURES

• MERGE_INJECTIONS

• STORE_FEATURES_SAMPLE_GROUP

The workflow pipeline is initialized by loading the raw data followed by extracting the spectra windows based on the given parameters by the user then merging spectras over the time axis. Once done, the peak picking routine will be executed on the MS1 spectras followed by executing the mass search routine. As an intermediate workflow step, the mzTab annotations and feature lists are saved to disk as mzTab and featureXML file formats respectively. A major processing step in this workflow is to estimate the Background Interferences for component and component group feature filter as well as ion intensity attributes from blank samples followed by storing component and component group percent Background Interference estimations to disk. Then, filter transitions and transitions groups based on criteria provided by the user followed by creating merged features from the accurate mass search results as well as merging multiple injections of the same sample. An as the final step in the workflow pipeline, the features for the sample group is saved to disk as a featureXML file.

The Spectra for the two injection samples can be inspected after all workflow steps had been run, to do so please click on view and then “Spectra”. From the Injections tab check “Plot/Unplot All” select all injection samples and plot the mass to charge ratio relative to their respective intensities as shown below:

1. Reporting the results

To export the results, select “Report” from the “Actions” which will show the “Create Report” window:

Based in the data you wish to export, select the desired “Sample types” from the left pane and select the “Metadata” from the right pane then click on of the buttons below to create the report with the selected items in the csv format.

Other options to export the data includes “Group Feature DB” and “Group Pivot Table”. The Group Feature DB includes all sample_group_name, component_group_name, component_name and any other additional metadata such as peak_apex_int, peak_area, and mz values. While the Group Pivot Table would include component_name component_group_name, meta_value such as peak_apex_int and RT, and CM values.

More details on exporting the results can be found in Export report.

The resulting featureXML and mzTab are saved in the features folder. featureXML files describe the spectra data for a given injection sample which includes a list of features with a set of UserParam for each feature such as PeptideRef, native_id and scan_polarity. The mzTab file includes a summary of the accurate mass search. These files can be parsed and processed by the pyOpenMS Python package.