Reports, import, and export
Vendor / .qtm in, Q. reports, Excel / PDF / method out.
Three doors around the same batch: bring methods and bottles in, build a spreadsheet that follows the current sample, and write Excel, PDF, and method packages out.
Import
Method → Load / Import
| Source | What you point at |
|---|---|
| Quanto package | .qtm (Replace or Append as AcqKey) |
| MassHunter method | .m / .quantmethod.xml |
| MassHunter method from data | .D folder |
| ChemStation method | .M + qdb.mth |
| OpenLab CDS method | .pmx processing method (expected compounds from OpenLab) |
| SCIEX method from data | .wiff |
OpenLab data (.dx / AcqData) is loaded with the bottles, not as a method file — see Compatibility. Acquisition .amx is not a quant method.
Batch → Add samples picks .D folders, OpenLab .dx data, WIFF files, or a sequence folder. Metadata from the file fills type / dose hints when present.
Append several vendor methods into one Quanto method: each import becomes an AcqKey (multi-instrument Key Review).
Reports
View → Report Designer — the workbook follows the current sample and current compound. Use Q. functions for sample, compound, keys, levels, calibration, and batch fields (Report formulas).
Per-sample report workbooks
On the Samples grid, each bottle can include checkboxes for which report workbooks should run for that sample. Multi-select the workbooks you want per bottle (or fill down the column) so a QC can run a different sheet set than a routine sample.
Export
| Action | Output |
|---|---|
| Method → Save Method | .qtm (+ responses + optional report workbooks) |
| Report export | Excel + PDF per sample, or parallel batch export (plots as pictures) |
| Grids | Copy / image |
Related
- Compatibility — OpenLab data vs
.pmxmethod - Set up an analysis
- Method design
- Report formulas