Coverage overview for pesticide, environmental, and odor/VOC workflows
MRM Method Builder currently covers 1,161 unique CAS in the main GC library for pesticide and environmental workflows, plus 527 odor/VOC compounds with method-aware support across WAX and 5ms libraries.
Coverage means the platform can match a compound to a supported internal record and return workflow-relevant output. It does not replace method suitability checks or lab-side validation.
Main GC library
Unique CAS used across the current pesticide and environmental GC workflow library.
Odor/VOC library
Unique CAS available in the odor/VOC dataset with method-aware support reporting.
Odor WAX support
Current WAX library support count in the odor dataset.
Odor 5ms support
5ms currently excludes 33 compounds that remain WAX-only.
What “coverage” means here
Coverage means the platform can match an input compound to a supported internal record and provide workflow-relevant output for the selected category or method.
Coverage does not mean universal support across every instrument setup, matrix, regulation, or lab SOP. It also does not remove the need to verify RT behavior, ion ratios, matrix suitability, and method acceptance criteria in your own environment.
How unsupported compounds are handled
Unsupported compounds should stay visible during review so users can audit the result set, correct names or CAS values, or switch methods when appropriate.
This matters most in odor/VOC workflows, where method choice changes support coverage across WAX and 5ms libraries.
Main library coverage for pesticide and environmental workflows
The current main GC library is a shared dataset used for pesticide and environmental workflow support. In practice, it includes pesticide analytes, pollutants, and related screening targets rather than two completely separate static databases.
That is why this page reports a combined library total for the current production dataset and then shows the dominant compound classes present in that library.
Top classification groups in the main GC library
| Classification | Unique CAS |
|---|---|
| Pollutant | 350 |
| Insecticide | 290 |
| Herbicide | 212 |
| Fungicide | 140 |
| Breakdown | 46 |
| Microbiocide | 10 |
Odor/VOC coverage by method
| Method library | Supported unique CAS | Notes |
|---|---|---|
| WAX (PEG, polar) | 527 | Covers the full odor dataset in the current project build. |
| 5ms (5% phenyl, low-polarity) | 494 | 33 compounds remain unavailable in 5ms and should stay visible as unsupported during review. |
Odor/VOC workflows are method-aware. Users should be able to switch methods, see unsupported compounds explicitly, and decide whether to proceed with matched compounds only.
Source data and update status
Coverage values on this page are derived from the active project datasets rather than hand-maintained marketing numbers.
For the current normalization and build logic behind these counts, read the methodology page.
Validation limits still apply
Coverage is a screening and method-building signal, not a substitute for laboratory validation.
Users remain responsible for checking:
- RT behavior under their own method conditions
- ion ratios and transition suitability
- matrix effects and acceptance criteria
- instrument-specific method fit before routine use
Coverage FAQ
Does coverage mean the compound is validated on my instrument?
No. Coverage means the platform can match the compound to a supported record and return workflow-relevant output. Instrument suitability, matrix effects, RT behavior, and final acceptance criteria still require lab-side validation.
Why can a compound appear in WAX but not in 5ms?
Odor/VOC support is method-aware. Some odor compounds are available only in the WAX library in the current dataset, so they remain visible as unsupported when 5ms is selected.
What happens if my CAS or compound name does not match?
Unmatched inputs should remain visible during review so you can correct the name, try a canonical CAS number, or continue with the matched compounds only.
How often is the coverage page updated?
Coverage values should track the active project datasets. As the underlying libraries are updated, the coverage page should be refreshed to reflect the production data in use.
Ready to check your own list?
Use the generator to validate your own compound names or CAS numbers, review supported matches, and move into the workflow that fits your target class.