cchdo / params

The master DB of CCHDO parameters in an installable package
BSD 3-Clause "New" or "Revised" License
1 stars 2 forks source link

Add NMOL/L as acceptable unit for IODATE and UREA #19

Closed eaitoro closed 1 year ago

eaitoro commented 1 year ago

Specific cruise in question that reports these data in this unit, which matches up with their cruise report/figures: 49NZ20191205

DocOtak commented 1 year ago

The existing UREA param has units of umol/kg. The usual volume variant would be umol/l. Can you confirm that the nmol is correct/expected? I will often start looking at the oceanographic literature for external verification of expected ranges/units for some parameter.

eaitoro commented 1 year ago

For IODATE: https://doi.org/10.1016/j.dsr2.2011.02.002

For UREA: https://doi.org/10.1002/lom3.10026

DocOtak commented 1 year ago

This one gets a partial for now, the IODATE change goes in as proposed. I did some checks on UREA and the data we have already.

All the existing data at CCHDO have UREA in umol/kg, with ranges comparable to what is here proposed here, just smaller:

I'd like to ask our science advisors for... advice on this one. I have a desire to keep the prefix consistency, i.e. the final param is umol/l and we convert from nmol/l to umol/l so the only difference between our units is mass vs volume. Pointing out that the conversion between nmol/l and umol/l is exact.

DocOtak commented 1 year ago

Asked Jim and Sarah at the meting on August 23. Since this is an unambiguous conversion, the advise is to convert from NMOL to UMOL by simple division by 1000 (pure SI conversions).

DocOtak commented 1 year ago

@cberys Where would you like the above decision documented?

cberys commented 1 year ago

@DocOtak it should be mentioned in the monthly report

and also make an issue on the operations manual repo to add it (or you can add it somewhere but that needs a major overhaul/revision so I suggest just making an issue)

DocOtak commented 1 year ago

Closing since IODATE was added and the UREA decision now exists in the ops manual as an issue and won't be added as a name.