Click here for a pdf version of this page.
Figure showing float cycle and the cycle timing variables with primary and mandatory ones in red. Floats can profile either on descent or ascent. Most floats profile on ascent. Their path is shown with a solid black line. Some floats profile on descent as shown by the dashed line.
Floats that profile on ascent would have the following primary & mandatory cycle timings:
Floats that profile on descent might have the following cycle timings:
- DST, DET, PET, DDET, AST, AET, TST, all surface times and TET
NOTE: if a float is programmed to experience a primary cycle timing event, but no timing information is sent back and no estimate is possible, fill value should be inserted in the JULD array with the measurement code corresponding to the primary cycle timing event.
- DST, DDET, DAST, DET, PET, AST, AET, TST, all surface times and TET
Examples of this include:
NOTE: the diagram above shows the chronological order of timing events for an Argos float. Iridium floats have a different chronological order of timing events. In either case, times in the JULD variable should be arranged chronologically.
- SOLO and APEX APF8 floats which send back no cycle timing information should have fill value for the primary measurement codes unless an estimated time can be determined
- Ice detection floats that detect ice at the surface and then do not surface should have fill value for measurement codes 600-704 for the affected cycles.