-
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
HM4000 and Xuanwu (HM6000) new entries in R23 and R08 #34
Comments
Note that : |
Also, I am a bit confused between R08 and R23. I understand than when new platform_type is accepted in R23, A R08 (instrument_type) code must be delivered at the same time ? Do you need extra information on the standard sensor onboard to deliver R08 code ? |
Hi Victor. R08 is based on WMO codes and is a number whereas R23 is a text field and is maintained by Argo. |
Hi Victor. R08 is a subset of WMO code table 1770. In the past, when a new platform emerged and we needed a new WMO_INST_TYPE in Ref Table 8 (now R08), Mathieu Belbeoch (in his former capacity at JCOMMOPS) was the person who would request a new code from WMO. So you may want to ask him how that should be done now. As an aside: I was told that the current R08, which combines float platform/sensor, is not a good way to go, as it is multiplying the need for new codes (e.g. instead of one code for APEX floats, we now have APEX with SBE, APEX with RBR, etc.). Can we please open a new Github ticket for that issue? |
Hi Annie, Megan, |
@mscanderbeg just to be clear, the request form Zenghong Liu and the QNLM is to name the float "HM4000" and "Xuanwu" following this : |
Hi @vturpin, @mscanderbeg and @apswong, Thanks for the comments and discussion. We should absolutely go ahead and create HM4000 and Xuanwu in R23. One thing that's not yet clear to me is the associated PLATFORM_TYPE_KEY code. This is currently captured in the description fields for each R23 term (http://vocab.nerc.ac.uk/collection/R23/current/) My first question is whether this is something still useful that we want to continue maintaining? |
Hello, please note that the two R23 entries were created, alongside a new R24 (platform maker) entry. These are described in GitHub issues #111 and #113. Once we know about the PLATFORM_TYPE_KEY code for the new R23 entries, I will update their description accordingly. Will leave this issue open until we have the new entries requested created in R08/WMO as well, as followed up by @vturpin. Good point about R08 @apswong, we should involve the relevant contact at WMO to have this discussion with, as Victor suggested. Please let me know if you spot any issues with the new NVS creations. |
Message from Thierry to Zenghong ref_table-23: ref_table-24: Can you now send me samples files for Xuanwu and Xuanwu deep floats ? |
Message for Thierry to Zenhong and Victor Hello Zenghong and Victor, Zenghong, is the mention of HSOE and QNLM correct in ref_table-23 (HSOE is the manufacturer, QNLM the customer) ? With the additions below in the reference tables, HM4000 and HM6000 files will be accepted on GDAC. Thierry ref_table-23: ref_table-8: ref_table-27: |
Hi Thierry, Zenghong, I pushed this issue on the appropriate repository: wmo-im/CCT#110 Previous request took about 4 month to be accepted. |
Message from Zenghong |
It will not be possible to change the manufacturer from HSOA to QNLM; if you want to have both possibilities (HSOA for now and QNLM in the future), we'll have to create a new instrument code for QNLM floats. |
The file format checker on Coriolis GDAC is updated to accept Xuanwu files (see see https://data-argo.ifremer.fr/dac/csio/2902879). The new entries in the reference tables are: ref_table-23 ref_table-8 ref_table-27 |
Remaining actions
|
The two reference have been added to the WMO Common Code Table C-3 Instrument make and type for water temperature profile measurements. The issue can be closed |
Maybe we should wait to see "HM4000" and "Xuanwu" here : https://github.com/wmo-im/CCT/blob/master/C03.csv before closing |
Hi @vturpin and @tcarval, I am just reviewing the Argo collections and noticed that the XUANWU/HM6000 concept is a special case in R23, as the ID (XUANWU) is different from the Alt Label (HM6000). For all other concepts in R23, ID = Alt Label. The same can be said for numerous (but not all) Argo collections. I was wondering - what are DACs using to populate the PLATFORM_TYPE (or what does the manufacturer would like DACs to use) - XUANWU or HM6000? If the former, would you be happy with replacing the Alt Label with XUANWU? HM6000 is mentioned in the description: http://vocab.nerc.ac.uk/collection/R23/current/XUANWU/ This would make this entry consistent with all others in R23; and also clarify things for DACs and M2M programs as well. Happy to discuss this in case. Thanks for your help, |
Shall we ask Zenghong Lui about it maybe ? On the other hand, what is the use of alt_label if it must be similar to ID? |
HM4000 and Xuanwu (HM6000) are registered in R23 and R08 tables. |
Last year QNLM (National Lab. for Marine Science and Technology, Qingdao) deployed 9 HM4000 floats in the NW Pacific.
It's a pilot deployment for China Deep Argo. Those floats are equipped with SEB61 and RBR deep CTDs, and some of them
have obtained reliable T/S profiles.
They are now ready to submit observations into GDACs via CSIO DAC.
Could we add HM4000 and HM6000 (i.e. Xuanwu and deep Xuanwu) into R23 for data distribution?
Suggested code :
ID | Pref label | definition
HM4000 | HM4000 float | HM4000 float
Xuanwu | Xuanwu Deep float | HM6000 float
The text was updated successfully, but these errors were encountered: