Logbook Button Displays a menu where you can choose to view, open, clear, save, or print a particular logbook. Help Button Displays a menu where you can select an online help. † File export is also supported (in the case of JCAMP, for 1D NMR only) We strive to support future analytical data format standardization efforts, such as AnIML. We are members of the Allotrope Partner Network participating in the creation of a standard analytical data framework (ADF), and support the Allotrope data format.adf (beta version).
Mass spectrometry is a scientific technique for measuring the mass-to-charge ratio of ions. It is often coupled to chromatographic techniques such as gas- or liquid chromatography and has found widespread adoption in the fields of analytical chemistry and biochemistry where it can be used to identify and characterize small molecules and proteins (proteomics). The large volume of data produced in a typical mass spectrometry experiment requires that computers be used for data storage and processing. Over the years, different manufacturers of mass spectrometers have developed various proprietary data formats for handling such data which makes it difficult for academic scientists to directly manipulate their data. To address this limitation, several open, XML-based data formats have recently been developed by the Trans-Proteomic Pipeline at the Institute for Systems Biology to facilitate data manipulation and innovation in the public sector. These data formats are described here.
This format was one of the earliest attempts to supply a standardized file format for data exchange in mass spectrometry. JCAMP-DX was initially developed for infrared spectrometry. JCAMP-DX is an ASCII based format and therefore not very compact even though it includes standards for file compression. JCAMP was officially released in 1988.[1] JCAMP was found impractical for today's large MS data sets, but it is still used for exchanging moderate numbers of spectra. IUPAC[2] is currently in charge and the latest protocol is from 2005.[3]
The Analytical Data Interchange Format for Mass Spectrometry is a format for exchanging data. Many mass spectrometry software packages can read or write ANDI files. ANDI is specified in the ASTM E1947 Standard.[4] ANDI is based on netCDF which is a software tool library for writing and reading data files. ANDI was initially developed for chromatography-MS data and therefore was not used in the proteomics gold rush where new formats based on XML were developed.
mzData was the first attempt by the Proteomics Standards Initiative (PSI) from the Human Proteome Organization (HUPO) to create a standardized format for Mass Spectrometry data.[5] This format is now deprecated, and replaced by mzML.[6]
mzXML is a XML (eXtensible Markup Language) based common file format for proteomics mass spectrometric data.[7][8] This format was developed at the Seattle Proteome Center/Institute for Systems Biology while the HUPO-PSI was trying to specify the standardized mzData format, and is still in use in the proteomics community.
As two formats (mzData and mzXML) for representing the same information is an undesirable state, a joint effort was set by HUPO-PSI, the SPC/ISB and instrument vendors to create a unified standard borrowing the best aspects of both mzData and mzXML, and intended to replace them. Originally called dataXML, it was officially announced as mzML.[9] The first specification was published in June 2008.[10] This format was officially released at the 2008 American Society for Mass Spectrometry Meeting, and is since then relatively stable with very few updates. On 1 June 2009, mzML 1.1.0 was released. There are no planned further changes as of 2013.
Below is a table of different file format extensions.
Company | Extension | File type |
---|---|---|
Agilent Bruker | .D (folder) | Agilent MassHunter, Agilent ChemStation, or Bruker BAF/YEP/TDF data format |
Agilent/Bruker | .YEP | instrument data format |
Bruker | .BAF | instrument data format |
Bruker | .FID | instrument data format |
Bruker | .TDF | timsTOF instrument data format |
ABI/Sciex | .WIFF | instrument data format |
ABI/Sciex | .t2d | 4700 and 4800 file format |
Waters | .PKL | MassLynx peak list format |
Thermo PerkinElmer | .RAW* | Thermo Xcalibur PerkinElmer TurboMass |
Micromass**/Waters | .RAW* (folder) | Waters MassLynx |
Chromtech Finnigan*** VG | .DAT | Finnigan ITDS file format; MAT95 instrument data format MassLab data format |
Finnigan*** | .MS | ITS40 instrument data format |
Shimadzu | .QGD | GCMSSolution format |
Shimadzu | .qgd | instrument data format |
Shimadzu | .lcd | QQQ/QTOF instrument data format |
Shimadzu | .spc | library data format |
Bruker/Varian | .SMS | instrument data format |
Bruker/Varian | .XMS | instrument data format |
ION-TOF | .itm | raw measurement data |
ION-TOF | .ita | analysis data |
Physical Electronics/ULVAC-PHI | .raw* | raw measurement data |
Physical Electronics/ULVAC-PHI | .tdc | spectrum data |
(*) Note that the RAW formats of each vendor are not interchangeable; software from one cannot handle the RAW files from another.
(**) Micromass was acquired by Waters in 1997
(***) Finnigan is a division of Thermo
There are several viewers for mzXML, mzML and mzData: MZmine,[11] PEAKS,[12]Insilicos,[13] MS-Spectre,[14] TOPPView (mzXML, mzML and mzData),[15] Spectra Viewer,[16] SeeMS,[17] msInspect,[18] jmzML[19] and Mascot Distiller.[20]
There is a viewer for ITA images.[21] ITA and ITM images can be parsed with the pySPM python library.[22]
Known converters for mzData to mzXML:
Known converters for mzXML:
Known converters for mzML:
Converters for proprietary formats:
Currently available converters are :