Processing BGC-Argo measurement timing information at the DAC level. Version 1.0, March 28th 2017.
Average rating votes
Bittig, Henry C.
MetadataShow full item record
Thermal lag or sensor time response corrections (e.g., ) require knowledge of the time of each individual sensor observation. In the Argo data system, the float's trajectory file is the natural place to put measurement timing information. Historically, only few levels of a float's profile have been timed, and DACs stored these sparse timed levels of the float profile in the trajectory already. Depending on the DAC, all measured paramters are stored with the timing information, or just the PRES variable is stored together with the time. With the need to have all observations timed, this approach leads to the following problems: a) With all parameters stored together with the timing information and put into the trajectory file, the trajectory file in effect duplicates all profiles. This contradicts the Argo data system's design to split profile and trajectory files and may pose a file size issue. b) With only PRES stored together with the timing information and put into the trajecto.....
PublisherIFREMER for Argo Data Management
Maturity LevelTRL 8 Actual system completed and "mission qualified" through test and demonstration in an operational environment (ground or space)
Best Practice TypeStandard Operating Procedure
CitationBittig, H.C.; Schmechtig, C.; Rannou, J-P. and Poteau, A. (2017) Processing BGC-Argo measurement timing information at the DAC level. IFREMER for Argo Data Management, 8pp. DOI: http://doi.org/10.13155/47998