chromatographic-peak-isolation-and-refinement
Summary
Refine and expand the boundaries of total ion current (TIC) peaks identified by sliding-window analysis using the isolatePeaks function, producing improved peak boundary estimates (start time, end time, apex position) for subsequent parameter extraction. This skill bridges coarse sliding-window peak detection with fine-grained parameter estimation in untargeted metabolomics data processing.
When to use
After sliding-window analysis has identified candidate TIC peaks but before extracting chromatographic parameters (retention time, peak width, intensity) from extracted ion chromatograms. Use this skill when you need to refine peak boundaries around initial window-detected regions to reduce false positives and improve parameter estimation accuracy for downstream XCMS or MZmine2 feature detection.
When NOT to use
- Raw mass spectra have not yet been converted to an open format (mzML, mzXML, CDF) or preprocessed by MSconvert — isolatePeaks requires the AutoTuner object initialized from converted data.
- Sliding-window analysis has not been run or returned zero peaks — isolatePeaks operates on existing window-detected signals and cannot generate peaks de novo.
- Peak boundaries have already been manually inspected and validated by an expert — re-running isolatePeaks on finalized peaks adds no analytical value.
Inputs
- AutoTuner object containing sliding-window-identified TIC peaks
- returned_peaks parameter (integer, e.g., 10)
- Raw mass spectral data (mzML, mzXML, or CDF format, preprocessed by MSconvert)
Outputs
- Isolated peaks object with refined boundary estimates
- Peak boundary table (start time, end time, apex position for each peak)
- CSV export of peak boundaries for validation
How to apply
Load the AutoTuner object containing sliding-window-identified peaks into R and call the isolatePeaks function with the returned_peaks parameter (e.g., 10) specifying the number of peaks to return. The function expands each sliding-window-detected region to obtain improved boundary estimates. Extract the resulting peak boundary table (start time, end time, apex position) for each of the returned peaks and export to CSV for review and subsequent EICparams parameter extraction. The rationale is that isolatePeaks uses statistical inference to widen the initial narrow window boundaries, capturing the full peak shape and improving robustness to noise-induced boundary artifacts.
Related tools
- Autotuner (R package providing the isolatePeaks function and AutoTuner class for TIC peak detection and boundary refinement) — https://github.com/KujawinskiLaboratory/Autotuner
- XCMS (Peak detection software that Autotuner parameters are tuned to optimize)
- MZmine2 (Peak detection software that Autotuner parameters are tuned to optimize)
- MSconvert (Converts raw mass spectrometer data to open formats (mzML, mzXML, CDF) required for AutoTuner input)
- R (Programming environment for running isolatePeaks and AutoTuner workflows)
Examples
library(Autotuner); isolated <- isolatePeaks(autotuner_object, returned_peaks = 10); write.csv(isolated$peaks, 'peak_boundaries.csv')
Evaluation signals
- Peak boundary table contains exactly returned_peaks rows (e.g., 10) with valid start time, end time, and apex position columns; apex is between start and end.
- Expanded boundaries are wider than the original sliding-window boundaries (visual inspection or boundary width delta > 0).
- All boundary time values are within the chromatographic run duration and in ascending order (start < apex < end).
- Export to CSV is successful and table is readable by downstream EICparams parameter extraction step without format errors.
- Refined peaks show reduced overlap or clustering compared to raw sliding-window peaks, indicating effective boundary separation.
Limitations
- isolatePeaks depends on the quality of initial sliding-window peak detection; if the window analysis is misconfigured (lag, threshold, influence parameters), boundary refinement cannot recover missing or spurious peaks.
- Performance has been validated only on qTOF, Orbitrap, and Fourier transform ion cyclotron resonance mass analyzers; performance on other instrument types is untested.
- Requires at least 3 raw samples and a metadata spreadsheet linking samples to experimental factors; isolated peaks are not meaningful if AutoTuner has not been initialized with multi-sample data.
- No changelog or version history is available in the repository, limiting traceability of boundary refinement algorithm changes across releases.
Evidence
- [other] The isolatePeaks function accepts an AutoTuner object, a returned_peaks parameter specifying the number of peaks to return (e.g., 10), and signals from the sliding window analysis, then outputs isolated peaks with expanded boundary estimates for subsequent parameter estimation.: "The isolatePeaks function accepts an AutoTuner object, a returned_peaks parameter specifying the number of peaks to return (e.g., 10), and signals from the sliding window analysis, then outputs"
- [intro] The first part of AutoTuner involves the identification of peaks within the total ion current (TIC) of the samples loaded up into AutoTuner.: "The first part of AutoTuner involves the identification of peaks within the total ion current (TIC) of the samples"
- [intro] Autotuner will expand each of these regions to obtain improved estimates on the bounds within the isolatePeaks function: "Autotuner will expand each of these regions to obtain improved estimates on the bounds within the isolatePeaks function"
- [intro] AutoTuner is designed to work directly with raw mass spectral data that has been processed by using MSconvert.: "AutoTuner is designed to work directly with raw mass spectral data that has been processed by using MSconvert"
- [readme] AutoTuner has been tested on untargeted data generated on qTOF, orbitrap and Fourier transform ion cyclotron resonance mass analyzers.: "AutoTuner has been tested on untargeted data generated on qTOF, orbitrap and Fourier transform ion cyclotron resonance mass analyzers"
- [readme] AutoTuner requires at least 3 samples of raw data converted from proprietary instrument formats (eg .mzML, .mzXML, or .CDF).: "AutoTuner requires at least 3 samples of raw data converted from proprietary instrument formats (eg .mzML, .mzXML, or .CDF)"
1---2name: chromatographic-peak-isolation-and-refinement3description: Use when after sliding-window analysis has identified candidate TIC peaks but before extracting chromatographic parameters (retention time, peak width, intensity) from extracted ion chromatograms.4license: CC-BY-4.05---67# chromatographic-peak-isolation-and-refinement89## Summary1011Refine and expand the boundaries of total ion current (TIC) peaks identified by sliding-window analysis using the isolatePeaks function, producing improved peak boundary estimates (start time, end time, apex position) for subsequent parameter extraction. This skill bridges coarse sliding-window peak detection with fine-grained parameter estimation in untargeted metabolomics data processing.1213## When to use1415After sliding-window analysis has identified candidate TIC peaks but before extracting chromatographic parameters (retention time, peak width, intensity) from extracted ion chromatograms. Use this skill when you need to refine peak boundaries around initial window-detected regions to reduce false positives and improve parameter estimation accuracy for downstream XCMS or MZmine2 feature detection.1617## When NOT to use1819- Raw mass spectra have not yet been converted to an open format (mzML, mzXML, CDF) or preprocessed by MSconvert — isolatePeaks requires the AutoTuner object initialized from converted data.20- Sliding-window analysis has not been run or returned zero peaks — isolatePeaks operates on existing window-detected signals and cannot generate peaks de novo.21- Peak boundaries have already been manually inspected and validated by an expert — re-running isolatePeaks on finalized peaks adds no analytical value.2223## Inputs2425- AutoTuner object containing sliding-window-identified TIC peaks26- returned_peaks parameter (integer, e.g., 10)27- Raw mass spectral data (mzML, mzXML, or CDF format, preprocessed by MSconvert)2829## Outputs3031- Isolated peaks object with refined boundary estimates32- Peak boundary table (start time, end time, apex position for each peak)33- CSV export of peak boundaries for validation3435## How to apply3637Load the AutoTuner object containing sliding-window-identified peaks into R and call the isolatePeaks function with the returned_peaks parameter (e.g., 10) specifying the number of peaks to return. The function expands each sliding-window-detected region to obtain improved boundary estimates. Extract the resulting peak boundary table (start time, end time, apex position) for each of the returned peaks and export to CSV for review and subsequent EICparams parameter extraction. The rationale is that isolatePeaks uses statistical inference to widen the initial narrow window boundaries, capturing the full peak shape and improving robustness to noise-induced boundary artifacts.3839## Related tools4041- **Autotuner** (R package providing the isolatePeaks function and AutoTuner class for TIC peak detection and boundary refinement) — https://github.com/KujawinskiLaboratory/Autotuner42- **XCMS** (Peak detection software that Autotuner parameters are tuned to optimize)43- **MZmine2** (Peak detection software that Autotuner parameters are tuned to optimize)44- **MSconvert** (Converts raw mass spectrometer data to open formats (mzML, mzXML, CDF) required for AutoTuner input)45- **R** (Programming environment for running isolatePeaks and AutoTuner workflows)4647## Examples4849```50library(Autotuner); isolated <- isolatePeaks(autotuner_object, returned_peaks = 10); write.csv(isolated$peaks, 'peak_boundaries.csv')51```5253## Evaluation signals5455- Peak boundary table contains exactly returned_peaks rows (e.g., 10) with valid start time, end time, and apex position columns; apex is between start and end.56- Expanded boundaries are wider than the original sliding-window boundaries (visual inspection or boundary width delta > 0).57- All boundary time values are within the chromatographic run duration and in ascending order (start < apex < end).58- Export to CSV is successful and table is readable by downstream EICparams parameter extraction step without format errors.59- Refined peaks show reduced overlap or clustering compared to raw sliding-window peaks, indicating effective boundary separation.6061## Limitations6263- isolatePeaks depends on the quality of initial sliding-window peak detection; if the window analysis is misconfigured (lag, threshold, influence parameters), boundary refinement cannot recover missing or spurious peaks.64- Performance has been validated only on qTOF, Orbitrap, and Fourier transform ion cyclotron resonance mass analyzers; performance on other instrument types is untested.65- Requires at least 3 raw samples and a metadata spreadsheet linking samples to experimental factors; isolated peaks are not meaningful if AutoTuner has not been initialized with multi-sample data.66- No changelog or version history is available in the repository, limiting traceability of boundary refinement algorithm changes across releases.6768## Evidence6970- [other] The isolatePeaks function accepts an AutoTuner object, a returned_peaks parameter specifying the number of peaks to return (e.g., 10), and signals from the sliding window analysis, then outputs isolated peaks with expanded boundary estimates for subsequent parameter estimation.: "The isolatePeaks function accepts an AutoTuner object, a returned_peaks parameter specifying the number of peaks to return (e.g., 10), and signals from the sliding window analysis, then outputs"71- [intro] The first part of AutoTuner involves the identification of peaks within the total ion current (TIC) of the samples loaded up into AutoTuner.: "The first part of AutoTuner involves the identification of peaks within the total ion current (TIC) of the samples"72- [intro] Autotuner will expand each of these regions to obtain improved estimates on the bounds within the isolatePeaks function: "Autotuner will expand each of these regions to obtain improved estimates on the bounds within the isolatePeaks function"73- [intro] AutoTuner is designed to work directly with raw mass spectral data that has been processed by using MSconvert.: "AutoTuner is designed to work directly with raw mass spectral data that has been processed by using MSconvert"74- [readme] AutoTuner has been tested on untargeted data generated on qTOF, orbitrap and Fourier transform ion cyclotron resonance mass analyzers.: "AutoTuner has been tested on untargeted data generated on qTOF, orbitrap and Fourier transform ion cyclotron resonance mass analyzers"75- [readme] AutoTuner requires at least 3 samples of raw data converted from proprietary instrument formats (eg .mzML, .mzXML, or .CDF).: "AutoTuner requires at least 3 samples of raw data converted from proprietary instrument formats (eg .mzML, .mzXML, or .CDF)"
