Our work with sensor makers to ask them to provide calibration information in fully machine-readable json files has shown up that storing information about calibration date is uncontrolled and inconsistent.
At present, many DACs include some date information in
PREDEPLOYMENT_CALIB_COMMENT
by adding a date somewhere in that string, with whatever format they choose for the string. This is not machine parseable.
If sensor makers are going to supply the information and we think it is worth keeping, the cleanest thing would be a new variable
PREDEPLOYMENT_CALIB_DATE(N_PARAM, DATE_TIME)
The predeployment_calib variables are dimensioned on N_PARAM, so the date would be tied back to the sensor serial number identified by
PARAMETER_SENSOR(N_PARAM, STRING128)
Examples of PARAMETER_SENSOR are CTD_PRES, CTD_TEMP, CTD_CNDC
Here would be possible manual entries:
Name
PREDEPLOYMENT_CALIB_DATE
Definition
char
PREDEPLOYMENT_CALIB_DATE(N_P ARAM, DATE_TIME);
PREDEPLOYMENT_CALIB_DATE:long _name = "Date and time (UTC) of calibration";
PREDEPLOYMENT_CALIB_DATE:conventions = "YYYYMMDDHHMISS";
PREDEPLOYMENT_CALIB_DATE:_Fill Value = " ";
Comment
Date-time at which calibration coefficients were determined. If date only is known, pad with zeros for HHMISS.
Format : YYYYMMDDHHMISS Example : 20010203000000 : Feb 3rd 2001
If calibration date is not known, use "unknown" padded with 7 extra spaces.
If calibration date is not applicable for this parameter, use "not applicable".
Our work with sensor makers to ask them to provide calibration information in fully machine-readable json files has shown up that storing information about calibration date is uncontrolled and inconsistent.
At present, many DACs include some date information in PREDEPLOYMENT_CALIB_COMMENT by adding a date somewhere in that string, with whatever format they choose for the string. This is not machine parseable.
If sensor makers are going to supply the information and we think it is worth keeping, the cleanest thing would be a new variable PREDEPLOYMENT_CALIB_DATE(N_PARAM, DATE_TIME)
The predeployment_calib variables are dimensioned on N_PARAM, so the date would be tied back to the sensor serial number identified by
PARAMETER_SENSOR(N_PARAM, STRING128)
Examples of PARAMETER_SENSOR are CTD_PRES, CTD_TEMP, CTD_CNDC
Here would be possible manual entries:
Name
PREDEPLOYMENT_CALIB_DATE
Definition
char PREDEPLOYMENT_CALIB_DATE(N_P ARAM, DATE_TIME); PREDEPLOYMENT_CALIB_DATE:long _name = "Date and time (UTC) of calibration"; PREDEPLOYMENT_CALIB_DATE:conventions = "YYYYMMDDHHMISS"; PREDEPLOYMENT_CALIB_DATE:_Fill Value = " ";
Comment
Date-time at which calibration coefficients were determined. If date only is known, pad with zeros for HHMISS. Format : YYYYMMDDHHMISS Example : 20010203000000 : Feb 3rd 2001 If calibration date is not known, use "unknown" padded with 7 extra spaces. If calibration date is not applicable for this parameter, use "not applicable".