-
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
move CNDC to be an intermediate core parameter #46
Labels
Comments
It makes sense. @apswong, tell me when I have green light to update the parameters list |
Hi annie, I ve made the change and push cndc into an ic in the excel sheet
best
CAtherine
…--
Catherine Schmechtig
0681827411
LEFE-CYBER Database
http://www.obs-vlfr.fr/proof
BGC Argo
http://biogeochemical-argo.org/
https://github.com/catsch
OSU Ecce Terra
Sorbonne Université - CNRS - UMS 3455
4, Place Jussieu
75 252 Paris Cedex 05
Tour 45 - couloir 45-55
2eme etage - 207
De: "Annie Wong" ***@***.***>
À: "nvs-vocabs/ArgoVocabs" ***@***.***>
Cc: "Catherine Schmechtig" ***@***.***>, "Comment" ***@***.***>
Envoyé: Vendredi 9 Décembre 2022 21:28:56
Objet: [nvs-vocabs/ArgoVocabs] move CNDC to be an intermediate core parameter (Issue #46)
I would like to propose moving CNDC to be an "intermediate core" parameter. This proposal is supported by [ https://github.com/cabanesc | @cabanesc ] and [ https://github.com/coatanoan | @coatanoan ] .
CNDC is by nature an intermediate parameter, being an input to compute salinity. Most floats do not return this parameter; only some floats from the early days of Argo, and some experimental floats, do so. For the floats that do return CNDC, delayed-mode operators need to do a superficial step to fill CNDC_ADJUSTED with adjustments derived from salinity. This is an awkward step, as some salinity adjustments, such as the cell thermal lag correction, should not be applied to CNDC.
In the past, we were not able to designate parameters as "intermediate core". But now we can. Being an intermediate parameter means there is no need to include CNDC_ADJUSTED, CNDC_ADJUSTED_QC and CNDC_ADJUSTED_ERROR in the Argo data files.
—
Reply to this email directly, [ #46 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AEJ4NPWTBI4CF2YRIFJDWBDWMOJARANCNFSM6AAAAAASZXFCRM | unsubscribe ] .
You are receiving this because you commented. Message ID: <nvs-vocabs/ArgoVocabs/issues/46 @ github . com>
|
The parameters list is now published on ADMT web site : http://www.argodatamgt.org/Data-Mgt-Team/News/Argo-physical-parameters-list-updated7
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to propose moving CNDC to be an "intermediate core" parameter. This proposal is supported by @cabanesc and @coatanoan.
CNDC is by nature an intermediate parameter, being an input to compute salinity. Most floats do not return this parameter; only some floats from the early days of Argo, and some experimental floats, do so. For the floats that do return CNDC, delayed-mode operators need to do a superficial step to fill CNDC_ADJUSTED with adjustments derived from salinity. This is an awkward step, as some salinity adjustments, such as the cell thermal lag correction, should not be applied to CNDC.
In the past, we were not able to designate parameters as "intermediate core". But now we can. Being an intermediate parameter means there is no need to include CNDC_ADJUSTED, CNDC_ADJUSTED_QC and CNDC_ADJUSTED_ERROR in the Argo data files.
The text was updated successfully, but these errors were encountered: