Tools¶
The software ecosystem around mzPeak is open source. This page lists the utilities built on top of the format; for the read/write libraries themselves, see Implementations.
Converters¶
- mzML2mzPeak — converts imzML / mzML to mzPeak (and back), with full
round-trip verification. It reads input through
mzdata. - Roadmap: a direct vendor RAW → mzPeak path (for example inside
ProteoWizard
msconvert) so every vendor format converts in a single step, embedding the original acquisition method as provenance.
Validation¶
- mzPeakValidator — a language-independent, profile-driven conformance
validator (
mzpeak-validate file.mzpeak). It checks index-file structure, schema consistency, JSON-schema compliance, CV accession/name agreement, reasonable data types, and cross-file consistency (for example that the declared number of data points matches the signal table).
Viewers¶
- mzPeak Explorer — opens any
.mzpeakfile directly in the browser, streamed over HTTP range requests with no download. Built on the TypeScript implementation. - mzPeakIV — an imaging viewer for mass-spectrometry imaging (MSI) datasets.
It streams a
.mzpeakfile in place and can assign masses to RGB channels to reconstruct tissue anatomy directly in the browser.
Example data¶
- Example data corpus ↗
— a public, browsable set of real
.mzpeakfiles converted from open datasets across vendors, instruments, and modalities (LC-/GC-MS, imaging MS, and studies shipping SDRF / ISA sample metadata), each alongside its original. Every file opens directly in a browser viewer over HTTP range requests.
Validator follows the API specification
The conformance validator is developed alongside the common cross-language API (see Implementations); semantic validation follows mzML precedent.