retention-time-window-tolerance-checking
Summary
Automated verification that internal standards and target analytes elute within user-defined retention time windows during LC-MS analysis, as a core QC checkpoint for flagging runs with chromatographic drift or peak misidentification. This skill detects retention time violations that indicate instrument malfunction, column degradation, or sample preparation issues.
When to use
Apply this skill when you have acquired LC-MS data and need to verify run quality before proceeding to metabolite identification or quantification. Retention time checking is essential when: (1) you have established expected retention time ranges for known internal standards or reference compounds; (2) you need to detect chromatographic drift across a sample batch; (3) you want to flag runs where peaks appear outside their expected elution windows, suggesting column problems or injection failures.
When NOT to use
- Untargeted discovery experiments where no reference retention times are available for the analytes of interest.
- Data from instruments with known chromatographic instability that makes fixed retention time windows unreliable within a single batch.
- Already-processed feature tables or integrated peak lists where original retention time data has been discarded.
Inputs
- Processed LC-MS data (mzML format or vendor-specific raw files)
- Retention time window definitions (compound name, expected retention time, tolerance bounds in minutes)
- Internal standard or target analyte list with assigned m/z and retention time expectations
Outputs
- Per-sample retention time pass/fail status
- Flagged retention time violations (compound, expected window, observed retention time)
- QC report with retention time diagnostic metrics across sample batch
How to apply
Load processed LC-MS data in mzML or vendor format (converting via MSConvert if necessary). Define retention time windows for each internal standard and target analyte—these windows typically reflect ±tolerance around a reference retention time established from prior calibration runs. During or after data acquisition, execute automated checks that extract the detected retention time for each compound from the processed data and compare it against the defined window bounds. Aggregate results per sample: a sample passes if all monitored compounds fall within their respective windows; flag violations when any compound's retention time falls outside its window. Export per-sample pass/fail status with flagged violations and actual retention times for diagnostic review.
Related tools
Examples
rapidqcms
Evaluation signals
- All internal standards in passing samples have retention times within their defined windows; violations are consistently flagged in failing samples.
- Retention time pass/fail decisions are reproducible across re-runs of the same raw data with identical window definitions.
- QC report retention time metrics (mean, min, max, standard deviation across batch) show expected clustering for samples from same instrument session; outliers correspond to flagged failures.
- Samples flagged for retention time violations can be manually inspected in raw chromatographic data to confirm peak position outside window bounds.
- Trend analysis of retention times across sequential samples reveals monotonic drift or sudden shifts that correlate with known maintenance events or column age.
Limitations
- Retention time windows must be pre-established from calibration runs or prior knowledge; the method cannot auto-discover appropriate windows for novel compounds.
- Fixed retention time windows assume stable chromatographic conditions within a batch; significant column degradation or temperature drift can render windows too narrow, causing false failures.
- Thermo Fisher mass spectrometers and RAW file format have been extensively tested; other vendor formats (Agilent, Bruker, Sciex, Waters) may exhibit bugs or incompatibilities in retention time extraction.
- Requires manual installation of MSConvert and MS-DIAL dependencies; Windows platform is required for full functionality, though MacOS users can view results.
- Retention time checking alone cannot distinguish between true peak misidentification and legitimate chromatographic variance; integration with m/z accuracy and intensity checks is recommended for robust QC.
Evidence
- [other] Define QC criteria (retention time windows, m/z tolerances, intensity thresholds) for internal standards and target analytes.: "Define QC criteria (retention time windows, m/z tolerances, intensity thresholds) for internal standards and target analytes."
- [other] Execute automated QC checks against each sample: verify internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance.: "Execute automated QC checks against each sample: verify internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance."
- [readme] Rapid QC-MS provides automated and user-defined quality control checks during LC-MS instrument runs: "Automated and user-defined quality control checks during instrument runs"
- [readme] Interactive data visualization of internal standard retention time, m/z, and intensity across samples: "Interactive data visualization of internal standard retention time, m/z, and intensity across samples"
- [readme] Rapid QC-MS was designed to run on Windows platforms because of its dependency on MSConvert for vendor format data conversion and MS-DIAL for data processing and identification.: "Rapid QC-MS was designed to run on Windows platforms because of its dependency on MSConvert for vendor format data conversion and MS-DIAL for data processing"
1---2name: retention-time-window-tolerance-checking3description: Use when you have acquired LC-MS data and need to verify run quality before proceeding to metabolite identification or quantification. Retention time checking is essential when: (1) you have established expected retention time ranges for known internal standards or reference compounds;4license: CC-BY-4.05---67# retention-time-window-tolerance-checking89## Summary1011Automated verification that internal standards and target analytes elute within user-defined retention time windows during LC-MS analysis, as a core QC checkpoint for flagging runs with chromatographic drift or peak misidentification. This skill detects retention time violations that indicate instrument malfunction, column degradation, or sample preparation issues.1213## When to use1415Apply this skill when you have acquired LC-MS data and need to verify run quality before proceeding to metabolite identification or quantification. Retention time checking is essential when: (1) you have established expected retention time ranges for known internal standards or reference compounds; (2) you need to detect chromatographic drift across a sample batch; (3) you want to flag runs where peaks appear outside their expected elution windows, suggesting column problems or injection failures.1617## When NOT to use1819- Untargeted discovery experiments where no reference retention times are available for the analytes of interest.20- Data from instruments with known chromatographic instability that makes fixed retention time windows unreliable within a single batch.21- Already-processed feature tables or integrated peak lists where original retention time data has been discarded.2223## Inputs2425- Processed LC-MS data (mzML format or vendor-specific raw files)26- Retention time window definitions (compound name, expected retention time, tolerance bounds in minutes)27- Internal standard or target analyte list with assigned m/z and retention time expectations2829## Outputs3031- Per-sample retention time pass/fail status32- Flagged retention time violations (compound, expected window, observed retention time)33- QC report with retention time diagnostic metrics across sample batch3435## How to apply3637Load processed LC-MS data in mzML or vendor format (converting via MSConvert if necessary). Define retention time windows for each internal standard and target analyte—these windows typically reflect ±tolerance around a reference retention time established from prior calibration runs. During or after data acquisition, execute automated checks that extract the detected retention time for each compound from the processed data and compare it against the defined window bounds. Aggregate results per sample: a sample passes if all monitored compounds fall within their respective windows; flag violations when any compound's retention time falls outside its window. Export per-sample pass/fail status with flagged violations and actual retention times for diagnostic review.3839## Related tools4041- **MSConvert** (Vendor format data conversion to standardized mzML format prior to retention time checking) — https://proteowizard.sourceforge.io/tools/msconvert.html42- **MS-DIAL** (Data processing and peak detection to extract retention time values for QC evaluation) — http://prime.psc.riken.jp/compms/msdial/main.html43- **Rapid QC-MS** (Complete QC orchestration platform that implements and automates retention time window checking with interactive visualization and real-time alerts) — https://github.com/czbiohub-sf/Rapid-QC-MS4445## Examples4647```48rapidqcms49```5051## Evaluation signals5253- All internal standards in passing samples have retention times within their defined windows; violations are consistently flagged in failing samples.54- Retention time pass/fail decisions are reproducible across re-runs of the same raw data with identical window definitions.55- QC report retention time metrics (mean, min, max, standard deviation across batch) show expected clustering for samples from same instrument session; outliers correspond to flagged failures.56- Samples flagged for retention time violations can be manually inspected in raw chromatographic data to confirm peak position outside window bounds.57- Trend analysis of retention times across sequential samples reveals monotonic drift or sudden shifts that correlate with known maintenance events or column age.5859## Limitations6061- Retention time windows must be pre-established from calibration runs or prior knowledge; the method cannot auto-discover appropriate windows for novel compounds.62- Fixed retention time windows assume stable chromatographic conditions within a batch; significant column degradation or temperature drift can render windows too narrow, causing false failures.63- Thermo Fisher mass spectrometers and RAW file format have been extensively tested; other vendor formats (Agilent, Bruker, Sciex, Waters) may exhibit bugs or incompatibilities in retention time extraction.64- Requires manual installation of MSConvert and MS-DIAL dependencies; Windows platform is required for full functionality, though MacOS users can view results.65- Retention time checking alone cannot distinguish between true peak misidentification and legitimate chromatographic variance; integration with m/z accuracy and intensity checks is recommended for robust QC.6667## Evidence6869- [other] Define QC criteria (retention time windows, m/z tolerances, intensity thresholds) for internal standards and target analytes.: "Define QC criteria (retention time windows, m/z tolerances, intensity thresholds) for internal standards and target analytes."70- [other] Execute automated QC checks against each sample: verify internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance.: "Execute automated QC checks against each sample: verify internal standard detection, peak intensity within acceptable range, retention time within defined window, and mass accuracy within tolerance."71- [readme] Rapid QC-MS provides automated and user-defined quality control checks during LC-MS instrument runs: "Automated and user-defined quality control checks during instrument runs"72- [readme] Interactive data visualization of internal standard retention time, m/z, and intensity across samples: "Interactive data visualization of internal standard retention time, _m/z_, and intensity across samples"73- [readme] Rapid QC-MS was designed to run on Windows platforms because of its dependency on MSConvert for vendor format data conversion and MS-DIAL for data processing and identification.: "Rapid QC-MS was designed to run on Windows platforms because of its dependency on MSConvert for vendor format data conversion and MS-DIAL for data processing"
HolobiomicsLab