Bio-acoustic Sonar (Global)

Reference Designator
Start Depth
End Depth
Mid-Water Platform
Current Status
Will Not Review
ZPLSG (Bio-acoustic Sonar (Global))
Science Discipline
ASL Environmental Sciences
M2M Example

No streams found

Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
3 Review AR7-01 07/11/2016 08/10/2017 CGMGI-02HYPM-00003 CGINS-ZPLSGA-55095 59.9695 -39.4886 131 2673
4 Review AR21 08/06/2017 06/16/2018 CGMGI-02HYPM-00004 CGINS-ZPLSGA-55108 59.9733 -39.9256 150 2659
5 Review AR30-03 06/09/2018 08/10/2019 CGMGI-02HYPM-00005 CGINS-ZPLSGA-55111 59.9697 -39.49 150 2669
6 Review AR35-05 08/06/2019 CGMGI-02HYPM-00006 CGINS-ZPLSGA-55066 59.9729 -39.5308 150 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

Metadata Start Date End Date Comment
7/11/16, 10:22 AM 8/10/17, 6:18 AM

Deployment 3: The battery pack had pressure built up inside the pressure housing from the degradation of the battery pack. No sign of flooding, and the instrument was still sampling at recovery.

Id: 1499 By: lgarzio