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, write Excel, PDF, and method packages out.
Import
Methods
Method → Load / Import is one dialog.
| Source | What you get |
|---|---|
.qtm |
Full Quanto method: analytes, quants, doses, ISTD links, sample types, stored calibration responses, optional report workbooks |
| MassHunter method | Compounds, ISTD flags, transitions, expected RT |
| MassHunter data method | Method inferred from a .D data folder |
| ChemStation method | Compounds from .M / qdb.mth |
| SCIEX WIFF method | MRM compounds from the WIFF |
Replace swaps the current method (sample results are cleared). Append adds the import under a new AcqKey and keeps existing analytes. That is the start of Key Review across instruments.
You can append only selected AcqKey + name keys when the dialog offers a candidate list.
Samples
Batch → Add samples
- Agilent ChemStation / MassHunter
.Dfolders - SCIEX WIFF
- Sequence or folder pick; files already in the batch are skipped
The data provider fills name, acquired time, instrument, position, dilution when the file has them. Sample types and dose names are then matched from the method. Override on the Samples grid when the file label is wrong.
What import does not invent
Vendor methods do not set Quanto Calibration mode. New .qtm packages default to Initial calibration unless you change it. ISTD links are imported when the vendor method has them; ESTD vs ISTD is still a Quant setting you can edit.
Reports
View → Report opens the workbook for the current method. The live sheet follows current sample and current compound (the same selection other views publish).
What a report can show
| Need | Function / source |
|---|---|
| Batch header | Q.Batch("Name"), method, counts, last saved |
| This bottle | Q.Sample("SampleName"), Type, Dil, SmpKey, AcqKey, acquired |
| This analyte in this bottle | Q.Compound("Result.FinalConcentration"), flags, RT, ISTD |
| Winner across injections | Q.KeyCompound(..., Q.SmpKeys(), Q.CurrentCompound) |
| All keys in batch order | Q.SmpKeys() |
| Curve levels | Q.Level, Q.Levels, Q.AllLevels |
| Lists from the method | Q.Analytes, Q.Doses, Q.AcqKeys, Q.SampleTypes, Q.SumGroups |
| Chromatogram / curve picture | Q.VSample, Q.VCompound, Q.VCalibration, Q.VQualifier |
| Show or hide a block | HideIfError, HideIfBlank, HideIfFalse, ShowIfTrue |
Names-grid help in the designer documents every Source.Property (Sample, Compound, Result, Analyte, Batch, Level, KeyReview, …).
Designer
Report Designer (stock WPF + Fluent ribbon, not Fast.Wpf) edits the workbook. Define report names the template. Define export picks:
- Which sheets belong in the batch pack
- Which sheets belong in each sample file
- Optional export folder
- Optional post-export command (run once per written file)
Workbooks can be cached into the .qtm when you save the method, so the next batch opens the same report.
Export
| Destination | How | Contents |
|---|---|---|
Method .qtm |
Method → Save Method | Tables + calibration responses + optional report workbooks |
| Excel + PDF | Report export, current sample | Formulas calculated, Q.V* plots baked to pictures |
| Excel + PDF (many samples) | Batch report export | Same template, one pair of files per sample, in parallel |
| Grid | Copy / Copy with headers / Copy as image | Whatever is selected, including Key Review super-cells |
A single-sample export needs a selected sample. Batch export walks the samples you include.
Plots are converted to embedded pictures so the .xlsx opens without Quanto. The live report is not modified.
Typical path
- Import or append methods (analysis setup).
- Add samples, Analyze, review curves and Key Review.
- Open Report, bind
Q.KeyCompoundfor the official numbers. - Define export sheets. Export the batch.
- Save Method if the curve (and the report) should travel to the next batch.