17. Update User Manual with instructions on how to populate SENSOR_MODEL .nc variable

[vpaba]

Current instructions are that, going forward, new sensor models added to R27/SENSOR_MODEL should not include the manufacturer's name in the label.
We will not be changing the name of existing concepts that contain the manufacturer's name in their label.

[tcarval]

This recommendation is for the NVS editors, not for Argo users.
@vpaba , can we update the R27 description http://vocab.nerc.ac.uk/search_nvs/R27/?searchstr=&options=identifier,preflabel,altlabel,status_accepted&rbaddfilter=inc&searchstr2=

Description	Terms describing sensor models in Argo NetCDF arrays

Description	Terms describing sensor models in Argo NetCDF arrays. Note: avoid using the manufacturer name in new entries when possible

[vpaba]

Hi @tcarval, @danibodc has kindly made this update, which should be visible on the web interface from tomorrow

[vpaba]

@tcarval on second thought, shall we extend the description to say that firmware version should also not be included in future entries?

Description	Terms describing sensor models in Argo NetCDF arrays. Note: avoid using the manufacturer name and firmware version in new entries when possible

[mscanderbeg]

Glad to see this updated description going into the R27 NVS table. Will the owners, @tcarval @ClareBellingham , @MKrieger29 and @roswri please try and keep this in mind when reviewing new requests for SENSOR_MODEL?

[tcarval]

@tcarval on second thought, shall we extend the description to say that firmware version should also not be included in future entries?

There are 11 entries for SBE61 sensor. I guess that each of these firmware version have differences that matter.
So in my opinion, we should keep the firmware in the sensor code. Otherwise, we should manage sensor code + a new firmware code.

SBE61CP_V5.0.1
SBE61
SBE61_V4.5.2
SBE61_V4.5.3
SBE61_V5.0.0
SBE61_V5.0.1
SBE61_V5.0.2
SBE61_V5.0.3
SBE61_V5.0.9
SBE61_V5.0.10
SBE61_V5.0.12