Standard % Deviation Custom Field Calculation
I have created a custom field to display % deviation values from my bracketed standards in the peaks tab for the purpose of making data review more convenient for my users.
I have used the following calculation: %.%.%((Entered X Value(Area/B)/Entered X Value)*100, Search order: Result Set Only, Sample Type: Standards Only.
The issue I have is that when the data is processed my
custom field results give different values to the % deviation value to that in
the calibration point tables.
Annoyingly I know why it’s doing this, my understanding is that the custom field calculation is being applied to each standard injection sequentially as it’s being processed, meaning that as the first standard is being processed it cannot calculate the slope of the calibration curve as one hasn’t been generated yet. Which is why the first value is 0.000 and the last value of -1.327 is correct.
Now I know also how to get around it. When processing if I select “Quantitate Only” and not “Calibrate & Quantitate” it already has the curve available to calculate the slope and therefore the % deviations…
My problem is that this workaround is not part of our SOP and users are required to process using “Calibrate & Quantitate” to ensure old calibration curves are not used for new data.
Is there a way to have the custom field calculation apply to my Result Set AFTER the calibration curves have been generated not during?
Answers
-
Why doesnt the reviewer just look at the inbuilt % deviation column which updates per standard injection instead of having to make a custom field to replicate this?0
-
Hi, thank you for your reply. The % deviation field in the peaks tab remains un-populated, after processing. which is why I resorted to trying to re-create it in a custom field.
The current working practice for viewing this data is to put it into a report method which will display it correctly however I want to remove that step for my users so they can access the information quicker.
How do I get this default %deviation field to populate in the peaks tab in this case?
0