-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NIST Temperature correction: feature only available for SN >= 42 & documentation #26
Comments
@mathieuboudreau please help me understand this:
In the code, we have a dictionary with 14 spheres, each one with reference T1 values at 16, 18, 20, 22, 24, and 26°C. If I understand well, these reference values correspond to phantom serial numbers >= 42 (see here): Lines 75 to 90 in 5e1e934
Based on this dictionary, we use the Line 134 in 5e1e934
Then, when we call Is this correct? If so, I don't understand what do you mean by replacing the T1 values of one for the other. |
Hi Juan, Sorry for the confusion. It's that the fits for >= 42 will be relative to the references T1 values (e.g. at 20 degrees C) of that version of the phantom (for serial numbers >=42). So in the case of serial numbers <42, we can make the assumption that the T1 will vary with temperature along the same curve as for >=42, but with a difference reference T1 value (e.g. at 20C). So I think for serial numbers of <42, we could just apply the fit as you're using already for >=42, but renormalize it to the reference T1 value for version 1 of t he phantom (serial numbers 42). Basically, I think if you apply the current algorithm as is for a measurement on a serial number <42, we would just need to divide the resulting T1 value by T1(SN>=42 at 20C) and then multiply by T1(SN<42 at 20C). You can verify if this would work for the case of temperature at exactly 20C for a SN<042; in this case, the outputed value should simply be T1(SN<42 at 20C) after the "fit" due to the renomarlization I explain here. If this is still confusing (which it might be, I'm typing this very late at night), then we could work through the steps (and write tests for it, which we should anyways) during a video call. Best, Mathieu |
@mathieuboudreau temperature correction is now available for phantom serial numbers <42. I created a pull request, but maybe we don't want to merge all commits ahead from the branch |
Was this merged? I can't recall. If so, please close this issue |
Hi @mathieuboudreau , I created the branch |
Ah ok perfect – thanks for catching me up to speed! I had recalled that we had pushed some changes related to to NIST temp in some repo for Katy, but that might have been a separate repo – do you recall where (and is this PR up to date with those changes)? Sorry for the confusion, I'll get myself back up to speed with this PR. |
Initially, I had pushed these changes to the existing branch |
Hi @jvelazquez-reyes ,
At a previous meeting together (or maybe in an email thread), we had discussed how to handle the temperature correction for serial numbers < 42. Katy Keenan had mentioned that their recommendation from NIST was to apply the fits for the temperature correction of serial numbers >= 42 to those of less than 42 (note that this is applying the polynomials of the fits from one to the other, not replacing the T1 values of one for the other). Below is here email:
I thought this was done, but just noticed that the tool is only working for serial numbers >42 at the moment (see here:
analysis/src/nist.py
Line 73 in 289e4c4
Also, it would be helpful if that function had some documentation at the top of the function (e.g. describing all the arguments, what it returns, and some sample usage). Katy asked if the function was available for sharing with other groups, so this would be useful information for them.
Thanks!
The text was updated successfully, but these errors were encountered: