Multi-batch dose responses

After a full initial calibration you can Save Method. The .qtm keeps the curve responses (the Y values at C1…C5), not only the recipe. Later batches can re-run some levels. Quanto keeps the others.

Multi-batch partial update of dose responses A saved method keeps C1–C5 responses. Later batches replace only the levels they re-ran. Partial update — each batch writes only the levels it ran Initial calibration can reuse responses stored in the method. A new batch replaces matching dose files and leaves the rest. Method after first full curve C1 kept C2 kept C3 kept C4 kept C5 kept Save Method (.qtm) stores these responses with the method. Batch A — only C3 was re-injected keep keep C3 update keep keep Analyze refits the curve: new C3 + method C1, C2, C4, C5. Batch B — C1 and C5 re-run, then Save Method C1 update keep C3 from A keep C5 update The method now mixes origins: C1 and C5 from B, C3 from A, C2 and C4 from the first curve. When this applies Calibration mode = Initial calibration (not bracketing). The batch has no full cal set, or only some levels. Quanto reuses method origins and response paths, then overwrites levels present in this batch. Bracketing never reuses saved origins. It fits only live calibration bottles in the run. Method levels stay; Batch A updates C3; Batch B updates C1 and C5

When to use it

• Daily work: one or two fresh standards, not a full curve.
• A level failed and you re-injected only that dose.
• Several batches should share one living method file.

This is Initial calibration only. Bracketing always refits from live cal bottles in that batch and never reads saved origins.

How a batch updates the method

1. First batch: full C1…C5 , Analyze, review the curve, Method → Save Method.
2. Next batch: add unknowns plus only the levels you want to refresh (for example C3).
3. Analyze. Missing levels are filled from the method’s stored responses and calibration-sample origins.
4. The new C3 response replaces the stored C3. C1, C2, C4, C5 stay.
5. Save Method again if this batch should become the new source for the next one.

Origins remember file path and acquisition time. A response is replaced when this batch contains that calibration path (or the same dose in the live set). Other doses are left alone.

What is stored

The method package records, per Quant:

• Dose names and concentrations
• Response values used on the curve
• Calibration-sample origins (path, acquired)
• Curve settings (fit, weight, origin, ISTD link)

It does not store unknown samples. Those stay in the .qtb batch.

Practical rules

• Keep dose names stable (C1 stays C1). A renamed dose will not match the stored point.
• If you change a concentration on the Dose table, re-run that level or accept that old responses now sit at a new X.
• A batch that contains a complete live cal set fits that set and does not need the stored origins.
• ISTD links still apply: a partial update of the target levels uses the ISTD response from the same file when present.

Reports and Key Review in each batch see the curve that batch actually fitted (mix of live + inherited points).