Why is the processing order of injections for the Calibrate and Quantitate functions in the sample set method not guaranteed to be the order in which they were acquired? - WKB223215

ENVIRONMENT

• Empower

ANSWER

The issue is that some custom fields in the results are dependent on the standard result being calculated first.

The order in which a group of injections are processed by the Calibrate and Quantitate functions in the sample set method is not guaranteed to be the order in which they were acquired. If the order in which the injections are processed is important, you can use the Label Reference field in the Calibrate and Quantitate functions to ensure the correct processing order.

1. Modify the Label Reference field for the Calibrate function such that the STD result is processed before all the results that depend on it.
2. Add a second Calibrate function after the first Calibrate function and set the Label Reference for the first Calibrate function to STD and the Label Reference for the second Calibrate function to the samples/controls that depend on the STD result.
3. Changing a custom field to All or Nothing is one way to address the problem, but that would require re-validation of any custom field changed.

ADDITIONAL INFORMATION

Initially, summary calculations were designed to do simple calculations such as averaging Amount or Area values. However, as usage has become more widespread, the complexity of the formulas has also increased. This means that the calculations might not be operating in the intended order, so that the update step is not occurring properly.

See - https://www.waters.com/waters/support.htm?lid=10134314&lcid=10134313&type=TECN

Having the Replace Area custom field nested within another CF is making this look inconsistent (unstructured). Replace means 'if this value hasn't been determined', use zero. All or Nothing is recommended when Replace is used so that we don't use a value before something is calculated.