Closed vpaba closed 2 months ago
Hello @nvs-vocabs/reference-tables - after some thought and discussions with partners and manufacturers, there are still some details to iron out regarding the granularity of information we would like to see stored in this NVS collection, without compromising its consistency.
According to the manual, the CONTROLLER_BOARD_TYPE_PRIMARY NetCDF field should be structured in the following way:
"Argo controller board type and generation [free-text additional float-model specific information]"
The 'Argo controller board type and generation' should be picked from the controlled list in R28 (currently the table at page 99 of the manual), and the additional, float-model specific information should be added within square brackets [] as free text.
From @nvs-vocabs/oceanops review in the Argo spreadsheet, the guidance above was never followed in a literal sense - and the way that this NetCDF field has been populated across float types and DACs has been inconsistent, with a wide range of details (from e.g. 'APF' to 'Apf9iSbe41cp7.2.5-SBD-DT-FDT-111').
From discussions on the R27 SENSOR_MODEL collection on whether the firmware version should be moved to a separate field (see GitHub issue - @apswong ), we could avoid duplicating this issue in R28 by only including the controller board types and generations, with any additional detail added as free text in square [] brackets when the NetCDF is generated, as suggested by the manual, at least for as long as a new dedicated NetCDF field is created for this purpose, if ever decided.
Based on the above, I would like to propose the following structure for the controller board vocabulary on the NVS:
NVS collection metadata Collection identifier: R28 Title: Argo controller board types and generations Alternative title: CONTROLLER_BOARD_TYPE Description: List of controller board types and generations
NVS collection example concepts:
Id | Preferred label | Alternative label | Definition |
---|---|---|---|
N1 | N1 controller board | N1 | Seabird Navis 1st generation board controls functions such as integrating the sensor data streams, operating the buoyancy engine, and passing the telemetry to the iridium transmitter |
N2 | N2 controller board | N2 | Seabird Navis 2nd generation board controls functions such as integrating the sensor data streams, operating the buoyancy engine, and passing the telemetry to the iridium transmitter |
GG32 | GG32 controller board | GG32 | GG32 controller board |
HC12 | HC12 controller board | HC12 | HC12 controller board |
APF8 | APF8 controller board | APF8 | APF controller board, generation 8 |
Please note that the definitions are not final yet. Thank you, please let me know what you think,
Hi,
I am fine with the suggestion. Shall we link vocabularies with Float Models too in the definition for each vocab ?
Could you also confirm that CONTROLLER_BOARD_TYPE_PRIMARY correspond to the naviguation and tranmission board. While CONTROLLER_BOARD_TYPE_SECONDARY correspond to the sientific data board ? CONTROLLER_BOARD_TYPE_SECONDARY is relevant for BGC float only if I understand well.
Best, V.
Hi @vturpin, thanks for your comment and apologies for the late acknowledgment. Unfortunately we haven't had the chance to make much progress on this vocabulary in the past couple of months, and won't be able to for another few weeks. However, this is high in our list and will get in touch when we pick it up again. Thanks for your patience.. V.
I renamed "Review of Argo Reference Table 28 and preparation for NVS load" into" Review of Argo Reference Table 28" as the table 28 was uploaded on NVS.
Objective: Load Argo Reference Table 28 onto the NVS as the R28 collection.
Phase I
Assess the state of Argo Reference Table 28 from the Argo User Manual and linked Excel spreadsheet (‘CONTROLLER_BOARD’ sheet).
Liaison with OceanOps is of particular importance, as related work is being carried out.
Phase II
Compile complete list of terms and definitions to be included in the new NVS collection R28.
Phase III
Review of work.
Phase IV
NVS load.