[water] bad calibrations pass through qa/qc checks #31
Labels
bug
Something isn't working
Comments
|
Many of these would be identifiable w/ a screening criterion for slope and/or R^2. Should explore, but I expect ~0.9 - 1.1 is a reasonable range for the regression slope parameter. Maybe start there? |
rfiorella
added a commit
that referenced
this issue
Feb 25, 2020
As noted in #31, bad calibrations pass through this script and are reflected in the calibrated data. Commit adds a requirement that R^2 must be above 0.9 to be used in calibration - though this might be too permissive. @bumbanian suggested a slope check as well - will look through the sites to see if there's a suitable range that works for all sites. Given that NEON seems to calibrate the instrument's slope/intercept parameters at some frequency (once a year maybe?), the suggestion of a 0.9-1.1 tolerance might work.
|
Currently no r2 threshold in calibrate_ambient_water_isotopes - seems an obvious place to start to improve this, and would make code structure more consistent w/ carbon calibration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bad calibration values are passed through qa/qc checks currently, and produce implausible (or impossible) isotope ratios.
The text was updated successfully, but these errors were encountered: