|
|
|
|
|
| Scanderbeg, Megan; Rannou, Jean-philippe; Wong, Annie; Klein, Birgit; Schmid, Claudia; King, Brian; Van Wijk, Esmee. |
| This DAC cookbook is to include instructions for the DACs on how to calculate different variables for the Argo profile files. This is especially true for some of the additional sensors that are being added to Argo floats. The extra variables increase the complexity of the profile file and extra instructions may be necessary, depending on float and sensor type. It is separate from other data manuals because users do not need to understand all these details, but that it is important that all DACs to be calculating the variables in the same manner. There are instructions in this cookbook that apply to all floats and some that apply to only certain float types. Look through the table of contents for the specific float types included. |
| Tipo: Text |
|
| Ano: 2019 |
URL: https://archimer.ifremer.fr/doc/00300/41151/66479.pdf |
| |
|
| |
|
|
| Bittig, Henry C.; Schmechtig, Catherine; Rannou, Jean-philippe; Poteau, Antoine. |
| Thermal lag or sensor time response corrections (e.g., [1]) 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... |
| Tipo: Text |
|
| Ano: 2017 |
URL: http://archimer.ifremer.fr/doc/00369/47998/48031.pdf |
| |
|
| |
|
|
| Rannou, Jean-philippe. |
| This document describes the format of the NetCDF files produced by the Coriolis DAC to store auxiliary data. Auxiliary data are transmitted by Argo floats (or computed from transmitted data) but are too specific or outside the framework of Argo to be stored in the regular Argo NetCDF files. The Argo floats of Coriolis DAC produce up to four NetCDF files types (depending on float type, version and configuration): - A meta data file - A technical data file - Individual profile data files - A trajectory data file The Argo user’s manual [RD1] should be read and understood before the present one. |
| Tipo: Text |
|
| Ano: 2017 |
URL: http://archimer.ifremer.fr/doc/00408/51995/52655.pdf |
| |
|
|
|
