-
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
CTD_TEMP_CNDC in R25 #50
Comments
@vpaba @tcarval I'd like to reactivate this Our work with sensor makers to distribute complete metadata that is consistent with NVS is maturing, and looks likely to involve live checking of some fields against NVS tables. Therefore the tables need to be complete, and CTD_TEMP_CNDC is needed in the online version of R25. |
@apswong , @BrianKingNOC : All temperature parameter names start with "TEMP" |
@tcarval : R25 is the list of SENSORs not PARAMETERs SENSORs tend to begin with something to do with the instrument, eg CTD_TEMP or STS_TEMP or TRANSMISSOMETER_CP660 So I would suggest the SENSOR should definitely be CTD_TEMP_CNDC, and yes it is a different device that measures temperature in a different place, and will likely have its own SENSOR_SERIAL_NO The PARAMETER it measures can be TEMP_CNDC, which sits in R03 alongside TEMP_DOXY and TEMP_CPU_CHLA, starting with TEMP |
My mistake, I'll add CTD_TEMP_CNDC in R25 |
I added CTD_TEMP_CNDC in R25 (both NVS and format checker)
New release of the format checker: |
I would like to request a new entry in R25 "SENSOR". It is CTD_TEMP_CNDC.
TEMP_CNDC is the internal temperature of the conductivity cell. For RBR CTDs, measurements for TEMP and TEMP_CNDC come from two separate thermistors. DACs will need CTD_TEMP_CNDC to record predeployment calibration information in the meta file separately from CTD_TEMP.
The text was updated successfully, but these errors were encountered: