LC-MS Scan Range Settings in Research Peptide Analytical Records
Importance of explicit scan range documentation
In peptide LC-MS analyses, precise capture of the instrument scan range and related parameters is essential for reproducible data processing, peak annotation, and retrospective reanalysis. Documenting LC-MS scan range settings reduces ambiguity when integrating raw files with conversion tools (for example, vendor formats to mzML) and aids automated pipelines that expect consistent mass-to-charge (m/z) bounds, resolution, and scan modes.
Recommended metadata fields and templates
A standardized metadata block should accompany every acquisition. At minimum, include: instrument make/model, method identifier and version, low and high m/z bounds for each scan event, scan type (full MS, MS/MS, SIM, PRM), acquisition polarity, resolution or resolving power setting, scan rate (Hz or scan/second), AGC/accumulation targets and maximum injection times, isolation window sizes for MS/MS, and mass calibration status (timestamped). Record whether data were acquired in profile or centroid mode, and any on-the-fly centroiding or deconvolution applied by the instrument firmware.
Provide these fields as machine-readable key:value pairs in an attached JSON or YAML sidecar file or embedded in the LIMS record. Example JSON keys: “scan_event_1”: {“type”:”full_MS”,”m_z_min”:350,”m_z_max”:1600,”resolution”:60000,”profile”:true}. Including method version and a checksum of the method file enables exact method retrieval.
Data provenance and file formats
To preserve provenance, retain original vendor raw files alongside converted open formats (such as mzML). When converting, include the conversion software name, version, command-line parameters, and conversion timestamp. For each converted file, store the mapping between raw scan indices and converted scan numbers. Where possible, embed the acquisition metadata into the mzML
Maintain an audit trail that links sample IDs, injection IDs, raw filename, method file checksum, operator, and instrument serial number. This audit trail is critical for validating that a particular scan range setting was active for a given injection and for tracing any deviations during batch reprocessing.
Practical workflows and versioning
Incorporate scan range documentation into routine workflow steps: method development, method freezing, pre-run checks, acquisition logging, and post-run verification. During method freezing, snapshot the method file and compute a cryptographic hash (e.g., SHA-256) stored in the LIMS. Pre-run checks should programmatically verify that the runtime m/z bounds match the frozen method; flag mismatches before sample processing proceeds.
For large studies, implement a versioning strategy where each analytic change to scan ranges or resolution increments the method version and triggers revalidation metadata. When reprocessing legacy data with updated mass ranges or new mass calibration, annotate the reprocessed dataset with the original acquisition scan range and the reprocessing parameters so downstream users can distinguish acquisition provenance from processing modifications.
Quality controls, validation and downstream considerations
Record QC injections and their acquisition parameters identically to sample injections, including scan-range settings. Log any in-run dynamic exclusion windows or targeted inclusion lists and their timestamps. For data sharing, provide a README that explains how scan events map to analytical questions (for example, full-scan for peptide discovery vs targeted MS/MS events for validation) without implying any application outside laboratory research.
Sources
- https://pubmed.ncbi.nlm.nih.gov/41731685/
- https://pmc.ncbi.nlm.nih.gov/articles/PMC2860270/
Not for human consumption. For laboratory research use only.