| Method | Data Stream | Content | Type | |
|---|---|---|---|---|
| recovered_wfp | vel3d_l_wfp_instrument_recovered | Data Products | Report M2M Stats | Science |
| recovered_wfp | vel3d_l_wfp_metadata_recovered | Metadata | Report M2M | Engineering |
| telemetered | vel3d_l_wfp_instrument | Data Products | Report M2M Stats | Science |
| telemetered | vel3d_l_wfp_sio_mule_metadata | Metadata | Report M2M | Engineering |
| Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 Review | AT26-29 | 02/19/2015 | 12/25/2015 | CGMGS-02HYPM-00001 | CGVEH-GWFPGX-10407 | CGINS-VEL3DL-01118 | -54.4683 | -89.3684 | 4402 | 4650 |
| 2 Review | NBP1511 | 12/15/2015 | 12/11/2016 | CGMGS-02HYPM-00002 | CGVEH-GWFPGX-45202 | CGINS-VEL3DL-01253 | -54.4701 | -89.24 | 4341 | 4515 |
| 3 Review | NBP1610 | 11/30/2016 | 12/01/2017 | CGMGS-02HYPM-00003 | CGVEH-GWFPGX-10406 | CGINS-VEL3DL-01117 | -54.4693 | -89.3191 | 4335 | 4583 |
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GS02HYPM |
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: 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 |
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GS02HYPM |
2/19/15, 6:00 PM | 12/25/15, 7:50 AM |
Deployment 1: Due to delays on deck during deployment, the profiler's first dive began before the anchor was dropped. Once the dive started, the winch roller engaged and the profiler began its descent, which in this case meant winching back toward the boat/anchor. This may have damaged the winch mechanism or started the profiler into a non-standard deployment mode. The upper profiler (WFP02) indicated an error condition upon recovery, and a large number of profiles failed to log any CTD data. The lower profiler's battery voltage dropped rapidly near profile 300, which appears to have slowed down the profiling speed and increased the profile duration. Id: 750 By: lgarzio |
|
GS02HYPM-WFP03 |
11/30/16, 2:29 PM | 12/1/17, 7:01 AM |
Deployment 3: The lower profiler was lost during the mooring recovery attempt. Recovered data from the main controller were processed, rather than from the profiler (as is customary). Id: 373 By: lgarzio |
|
GS02HYPM |
11/30/16, 2:29 PM | 12/1/17, 7:01 AM |
Deployment 3: Data were not transmitted via satellite telemetry. Id: 377 By: lgarzio |