GP02HYPM-MPM01-02-ZPLSGA009

Bio-acoustic Sonar (Global)

Reference Designator: GP02HYPM-MPM01-02-ZPLSGA009
Review Status: Will Not Review
Note: Not Delivered Via uFrame - Missing Parser

Depth: 150m
Class: ZPLSG (Bio-acoustic Sonar (Global))
Make / Model: ASL Environmental Sciences / AZFP

Dataset Reviews

No reviews found.

System Annotations Show

Metadata	Start Date	End Date	Comment
GP02HYPM	6/20/14, 11:28 PM	6/21/14, 10:14 PM	Deployment 2: Platform was deployed on 6/16/2014, recovered on 6/21/2014 at 03:28 UTC due to firmware issue and re-deployed with updated firmware on 6/22/2014 at 02:14 UTC Id: 580 By: lgarzio Flag: not_operational Exclude: No
GP02HYPM	7/15/17, 5:25 PM	7/26/18, 6:15 PM	Deployment 5: Telemetered data are not available for this deployment because gliders were not deployed. Id: 140 By: lgarzio

Review Notes

Metadata	Start Date	End Date	Comment
GP02HYPM			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. Examples: 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/8/19* Review Images
GP02HYPM	7/3/16, 2:05 AM	7/26/18, 10:15 PM	Deployments 4 and 5 don't have deployment depths defined in asset management. By Lori Garzio, on 1/3/19
GP02HYPM Deployment: 2	6/16/14, 2:15 AM	6/22/14, 12:00 PM	Excluding data from the beginning of deployment 2 from the final statistics as the mooring was recovered and re-deployed (annotation ID 580) By Lori Garzio, on 1/3/19
GP02HYPM Deployment: 5	7/15/17, 9:25 PM	7/26/18, 10:15 PM	The mooring was deployed 9 - 10 km from the location of the previous 4 deployments of this mooring. If this location is correct, the platform should be annotated to inform the users as to why the deployment location changed. By Lori Garzio, on 1/2/19

Metadata

Start Date

End Date

Comment

GP02HYPM

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.

Examples:
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/8/19

Review Images

GP02HYPM

7/3/16, 2:05 AM

7/26/18, 10:15 PM

Deployments 4 and 5 don't have deployment depths defined in asset management.

By Lori Garzio, on 1/3/19

GP02HYPM
Deployment: 2

6/16/14, 2:15 AM

6/22/14, 12:00 PM

Excluding data from the beginning of deployment 2 from the final statistics as the mooring was recovered and re-deployed (annotation ID 580)

By Lori Garzio, on 1/3/19

GP02HYPM
Deployment: 5

7/15/17, 9:25 PM

7/26/18, 10:15 PM

The mooring was deployed 9 - 10 km from the location of the previous 4 deployments of this mooring. If this location is correct, the platform should be annotated to inform the users as to why the deployment location changed.

By Lori Garzio, on 1/2/19