Platform Controller

Reference Designator
Start Depth
End Depth
Current Status
SIOEN (Platform Controller)
Science Discipline
Subsurface mooring controller
M2M Example
Method Data Stream Content Type
recovered_host sio_eng_control_status_recovered Control Status Data Report M2M Engineering
telemetered sio_eng_control_status Status Data Report M2M Engineering
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 Review KN221-04 09/11/2014 08/16/2015 CGMGI-02HYPM-00001 CGCON-SIOCON-13277 59.9753 -39.4818 2602 2678
2 Review AT30-01 08/16/2015 07/16/2016 CGMGI-02HYPM-00002 CGCON-SIOCON-13284 59.9727 -39.5248 2602 2667
3 Review AR7-01 07/11/2016 08/10/2017 CGMGI-02HYPM-00003 CGCON-SIOCON-13283 59.9695 -39.4886 2583 2673
4 Review AR21 08/06/2017 06/16/2018 CGMGI-02HYPM-00004 CGCON-SIOCON-13992 59.9733 -39.9256 2570 2659
5 Review AR30-03 06/09/2018 08/10/2019 CGMGI-02HYPM-00005 CGCON-SIOCON-13993 59.9697 -39.49 2570 2669
6 Review AR35-05 08/06/2019 CGMGI-02HYPM-00006 CGCON-SIOCON-12368 59.9729 -39.5308 2570 2664
Metadata Start Date End Date Comment

I submitted a helpdesk question on 11/12/2018 regarding an offset between recovered and telemetered data for all global HYPMs: "There appears to be a substantial offset between data with the same timestamps from recovered_wfp and telemetered methods for all deployments of all global WFP CTDs, and I have included information from two representative deployments of two different profilers as examples. It looks like the values recorded for the first common timestamp are exactly the same, and as the profiler moves along in time the offset between the values recorded for the same timestamp become increasingly more offset. Then, the profiler reaches the end of the profile (either at its shallowest or deepest point), resets, and the pattern begins again. This is most easily seen in the pressure data, but there is an offset for all science parameters.

GI02HYPM-WFP02-04-CTDPFL000 deployment 1
GP02HYPM-WFP02-04-CTDPFL000 deployment 3

The *_intersect.csv files attached contain data where recovered and telemetered timestamps intersect. For each timestamp and science parameter there are recorded values (from .nc files downloaded from the system) and the difference. For each parameter, the difference between the values at the bottom and top of the profiler's range are exactly zero, and (particularly for pressure) the differences steadily increase until they are reset at zero at the bottom/top of the profile. This pattern continues throughout the deployment. The plots attached are zoomed in to one upcast and one downcast, and highlight the offset in the data between the two methods."

Redmine 13743

By Lori Garzio, on 8/5/19

New Note

No annotations yet.