New instrument request

[willdrysdale]

Instrument Manufacturer

AERIS

Instrument Model

Ultra_CO_N2O

Instrument Serial Number

100861

Instrument Scientist Name

Katie Read

Instrument Scientist ORCID

0000-0002-4044-455X

Instrument Owner (and ROR ID)

National Centre for Atmospheric Science (https://ror.org/01wwwe276)

If "Other" selected above, please type the owner and ROR ID (if known) below.

No response

NCAS Observatory

CVAO

Instrument description

AERIS CO and N2O Mid IR absorption analyser.

Manufacturer website here.

Note the manufacturer doesn't seem to differentiate their range of "Ultra" instruments with any obvious model number, so I've appended CO, N2O here.

Suggested instrument name: ncas-co-aeris-1

[github-actions]

Thank you for submitting a request for a new instrument. The following need to be decided through discussion:

• NCAS instrument ID.
• Instrument descriptor.
• Data product(s).
• Instrument category.
• Host institution.
• List of previous instrument IDs (if any).

[joshua-hampton]

Hi @willdrysdale, Graham and I had a chat about this yesterday, couple of points on the instrument name:

• we're looking follow the general structure of ncas-<type-of-instrument>-<point-of-interest>-X for new instrument names going forward. Presumably in this case <point-of-interest> is co
• we also don't want to use instrument manufacturer/model info in the instrument name, and would prefer something that describes the general type of instrument (examples include radar, lidar, ceilometer e.t.c.). Have you any suggestions for what would be suitable for this instrument along those lines?

[willdrysdale]

I think point-of-interest being co is fine.

re: <type-of-instrument> this is a little harder. My instinct is to go with aeris-co as this clearly differentiates it from picarro-co and matches how we refer to the instruments in real life. It also fits more broadly with the rest of the instrument names that already exist at CVAO.

If you are looking for something more general, then ncas-gas_analyser-co but that seems verbose without gaining more information, or you could go for ncas-mid_ir-co , which would differentiate from the picarro (which would be ncas-crds-co in that scheme, not that I am advocating a name change).

ncas-aeris-co strikes me as the best middle ground to be semantically consistent with the existing data.

[gap736uk]

@joshua-hampton and I discussed this and would like to suggest we go with:
ncas-mid-ir-co-1: as our preference as we're trying to move to a state where the instrument names are about the function/type of operation rather than being reliant on referencing any specific manufacturer/model name [this info is held in the instrument metadata so this is really a reference back to that]. This follows the overall scheme we're migrating to over time, with clear separation from the previous instrument.

Not suggesting name changes for existing recored instruments in the instrument vocab, but as they are retired and we replace them with others we'll continue to introduce the names in the target form.

[just to clarify these are hyphen separated terms as in file naming convention the underscore character is used to separate file name components]

[willdrysdale]

Hi Graham - sorry for the delay.

FYI the folder was created as ncas-co-aeris-1 on 2024/08/12, and we have been saving data to this ever since. If you want to change the name I think it would be best you contact Katie first as this could impact her workflows.

For my own understanding I have a question re hyphens and underscores.
I suggested ncas-mid_ir-co-1 to follow the ncas-<type-of-instrument>-<point-of-interest>-X format - so that the type of instrument and point of interest can be extracted via a string split on -. splitting the mid-ir with a hypen would defeat this. Is there something else you are looking to achieve here? Calling it ncas-midir-co-1 would be ok if you wanted to preserve the string parsing and not use underscores?

[joshua-hampton]

Underscores are used to separate different sections of the file name in the netCDFs that you send to CEDA, hyphens are used to separate "words" in each of those sections (using the word "word" loosely).
The ncas-co-aeris-1 folder was set up at the time just so we had somewhere to save the data on JASMIN - I did mention at the time that the "official" name would be dependent on this conversation.