Mass spectrometry file format conversion
Use when you have raw MS data files in vendor-native format (.raw, .d, .ms) from CE-MS or LC-MS instruments and need to process them through AriumMS or other open-source metabolomics pipelines that require standardized XML-based interchange formats.From its SKILL.md
npx -y skills add HolobiomicsLab/asb-skill-collections --skill mass-spectrometry-file-format-conversionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as CC-BY-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
6.8 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it
mass-spectrometry-file-format-conversion
Summary
Convert raw mass spectrometry data from vendor-native formats (.raw, .d, .ms) to open, standardized .mzXML or .mzML formats using msconvert, enabling downstream processing by untargeted metabolomics workflows such as AriumMS. This conversion is a mandatory prerequisite for multi-platform CE-MS and LC-MS data integration.
When to use
You have raw MS data files in vendor-native format (.raw, .d, .ms) from CE-MS or LC-MS instruments and need to process them through AriumMS or other open-source metabolomics pipelines that require standardized XML-based interchange formats. The conversion must occur before ROI extraction, preprocessing, or data augmentation steps.
When NOT to use
- Your MS data is already in .mzXML or .mzML format — conversion is redundant.
- Your downstream workflow accepts vendor-native formats directly (rare; most open-source tools require standardized formats).
- You lack the ProteoWizard suite installation or permission to run msconvert on your system.
Inputs
- Raw mass spectrometry data file (vendor-native format: .raw, .d, .ms)
- CE-MS or LC-MS instrument output
Outputs
- .mzXML file
- .mzML file
How to apply
Run msconvert (distributed with ProteoWizard) with the output format flag set to either .mzXML or .mzML, applying default centroiding and compression settings appropriate for your data type (CE-MS or LC-MS). After conversion, validate that output files are well-formed XML, contain expected metadata fields (scan count, mass range, retention time range), and match the input file count. The choice between .mzXML and .mzML is determined by your downstream tool's requirements; both are valid open formats. Centroiding reduces file size and noise while preserving peak information necessary for region-of-interest detection.
Related tools
- msconvert (Primary tool for converting raw MS data to standardized .mzXML or .mzML formats with configurable centroiding and compression) — http://proteowizard.sourceforge.net/download.html
- ProteoWizard (Suite containing msconvert; distributes the conversion tool) — http://proteowizard.sourceforge.net/download.html
- AriumMS (Downstream untargeted metabolomics workflow that consumes converted .mzXML or .mzML files for ROI extraction and data augmentation) — https://github.com/AdrianHaun/AriumMS
Examples
msconvert input_raw_file.raw --mzML --zlib --filter "peakPicking vendor msLevel=1-" # Converts .raw to .mzML with zlib compression and vendor centroiding
Evaluation signals
- Output files are well-formed XML and parse without schema validation errors.
- Output .mzXML or .mzML files contain non-empty metadata fields: scan count > 0, mass range min and max are numerically sensible for the instrument and analysis, retention time range reflects expected chromatographic window.
- File conversion completes without error messages or warnings from msconvert.
- Number of output files matches number of input files (1:1 conversion).
- File size of converted .mzXML or .mzML is smaller than raw input (compression applied) but contains all scans and peaks.
Limitations
- Vendor-specific metadata embedded in raw files may be lost or degraded during conversion to open formats; check that critical instrument parameters (ionization mode, analyzer type, resolution settings) are preserved in the converted file.
- msconvert requires the ProteoWizard suite to be installed and may not support all vendor formats; consult ProteoWizard documentation for supported input types.
- Centroiding settings (default vs. user-specified) affect downstream peak detection sensitivity and should be documented for reproducibility.
- Large raw files (>1 GB) may require extended conversion time; batch processing should use appropriate parallelization or scheduling.
Evidence
- [other] Raw MS data must be converted to .mzXML or .mzML file format using msconvert: "For MS Data conversion to .mzXML or .mzML file format use msconvert, distributed with the ProteoWizard Project"
- [other] Workflow step: obtain raw MS data in vendor-native format: "Obtain raw MS data files in vendor-native format (e.g., .raw, .d, .ms) from CE-MS or LC-MS instruments."
- [other] Workflow step: run msconvert with output format and centroiding settings: "Run msconvert (ProteoWizard) with output format set to .mzXML or .mzML, applying default centroiding and compression settings as appropriate for the data type."
- [other] Validation step: verify converted files contain expected metadata: "Verify converted files are valid .mzXML or .mzML and contain expected metadata (scan count, mass range, retention time range)."
- [readme] AriumMS requires converted .mzXML or .mzML as input: "All in one tool for untargeted Metabolomics by ROI and augmentation of multiple Data sets."
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.