Method | Data Stream | Content | Type | |
---|---|---|---|---|
recovered_wfp | vel3d_k_wfp_instrument | Data Products | Report M2M Stats | Science |
recovered_wfp | vel3d_k_wfp_metadata | Metadata | Report M2M | Engineering |
recovered_wfp | vel3d_k_wfp_string | String Data | Report M2M | Engineering |
telemetered | vel3d_k_wfp_stc_instrument | Data Products | Report M2M Stats | Science |
telemetered | vel3d_k_wfp_stc_metadata | Metadata | Report M2M | Engineering |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CP02PMCO-WFP01-01-VEL3DK000 |
For deployments 1, 6, 7 and 8 telemetered and recovered data have different timestamps and so data comparison could not be performed. By Leila Belabbassi, on 3/25/19 |
||
CP02PMCO-WFP01-01-VEL3DK000 |
vel3d_k_pressure (dbar) is an array of all fill values for every deployment. By Lori Garzio, on 8/8/19 |
||
CP02PMCO-WFP01-01-VEL3DK000 |
Annotation ID 1403 needs to be updated when the algorithm is fixed. By Lori Garzio, on 8/8/19 |
||
CP02PMCO-WFP01-01-VEL3DK000 |
There are several days during deployments 1, 2, and 3 where recovered_wfp data are not available but telemetered data are available. These data should be available in the recovered_wfp data streams. By Lori Garzio, on 8/8/19 |
||
CP02PMCO-WFP01 |
12/6/14, 12:00 AM | 5/2/15, 12:00 AM |
annotation ID 712 should be updated by adding that data quality is bad for this time range. By Leila Belabbassi, on 3/20/19 |
CP02PMCO-WFP01 |
12/6/14, 12:00 AM | 5/2/15, 12:00 AM | |
CP02PMCO Deployment: 8 |
Lat and Lon for deployment 8 are very far for what is the platform standard location. Please check? see redmine help desk ticket # 13757 (https://redmine.oceanobservatories.org/issues/13757) By Leila Belabbassi, on 3/19/19 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CP02PMCO-WFP01-01-VEL3DK000 Method: telemetered |
4/13/14, 1:29 PM | 10/7/14, 8:01 AM |
Deployment 1: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.
Id: 2082
By: swhite
|
CP02PMCO-WFP01-01-VEL3DK000 Method: telemetered Stream: vel3d_k_wfp_stc_instrument |
4/13/14, 1:50 PM |
During descending profiles, the vertical velocity estimates may be incorrect due to interference with beam 3 measurements arising from the nearby CTD sensor. Users should cross-compare these vertical velocity estimates with those derived from the CTD pressure record to determine profiles of possible concern. Good vertical velocity estimates will closely align with the CTD derived estimates. Regardless, there should be minimal impact on the estimates of the horizontal velocities. However, care should be taken with these estimates to confirm this conclusion.
Id: 1651
By: swhite
|
|
CP02PMCO-WFP01-01-VEL3DK000 Method: recovered_wfp Stream: vel3d_k_wfp_instrument |
4/13/14, 1:50 PM |
During descending profiles, the vertical velocity estimates may be incorrect due to interference with beam 3 measurements arising from the nearby CTD sensor. Users should cross-compare these vertical velocity estimates with those derived from the CTD pressure record to determine profiles of possible concern. Good vertical velocity estimates will closely align with the CTD derived estimates. Regardless, there should be minimal impact on the estimates of the horizontal velocities. However, care should be taken with these estimates to confirm this conclusion.
Id: 1652
By: swhite
|
|
CP02PMCO-WFP01-01-VEL3DK000 |
4/13/14, 2:00 PM | 2/14/19, 7:00 PM |
UPDATED, 2020-04-15: Corrected algorithm has been uploaded to the system and is active. * The algorithm supplied by the vendor to calculate water velocities is incorrect. Corrected code is currently in review. Id: 1403 By: swhite |
CP02PMCO-WFP01 Method: telemetered |
7/21/14, 2:10 PM | 10/6/14, 8:00 PM |
Telemetry was interrupted and no data are available via telemetry due to a time out error. The data files were too large to write and the system run out of time before it could get them through the inductive modem. Id: 711 By: leila |
CP02PMCO-WFP01 |
12/6/14, 10:00 PM | 4/30/15, 6:35 PM |
The profiler is stuck at the bottom of its range. Id: 712 By: leila |
CP02PMCO |
3/3/16, 5:40 AM | 5/20/16, 8:09 AM |
No telemetered data expected because communications were suspended after the battery was depleted. Id: 233 By: leila |
CP02PMCO-WFP01-01-VEL3DK000 Method: telemetered |
5/20/16, 1:43 PM | 11/6/17, 12:04 PM |
Deployment 6-8: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.
Id: 2083
By: swhite
|
CP02PMCO |
9/5/16, 5:05 AM | 10/2/16, 7:59 AM |
No telemetered data expected because communication were lost after the passge of tropical storm Hermine. Id: 234 By: leila |
CP02PMCO-WFP01-01-VEL3DK000 Method: telemetered Stream: vel3d_k_wfp_stc_instrument |
11/6/17, 8:11 PM | 4/10/18, 3:11 PM |
Deployment 9; During the times indicated by the start and end times of this annotation, the VEL3D instrument on the Profiler contained a firmware bug which caused beam 3 (downward-facing) to be on during ascents, and beam 1 (upward-facing) to be on during descents, instead of vice versa. Therefore the issue of incorrect vertical velocity estimates due to interference with the CTD noted in a previous annotation will affect the ascending profiles rather than the descending profiles.
Id: 1721
By: areed
|
CP02PMCO-WFP01-01-VEL3DK000 Method: recovered_wfp Stream: vel3d_k_wfp_instrument |
11/6/17, 8:11 PM | 4/10/18, 3:11 PM |
Deployment 9; During the times indicated by the start and end times of this annotation, the VEL3D instrument on the Profiler contained a firmware bug which caused beam 3 (downward-facing) to be on during ascents, and beam 1 (upward-facing) to be on during descents, instead of vice versa. Therefore the issue of incorrect vertical velocity estimates due to interference with the CTD noted in a previous annotation will affect the ascending profiles rather than the descending profiles.
Id: 1722
By: areed
|
CP02PMCO-WFP01-01-VEL3DK000 Method: telemetered |
11/2/18, 4:28 PM | 4/23/19, 12:12 PM |
Deploymnent 11: Recovered data should be used for analysis. Velocity data cannot be calculated from telemetered data because the beam information was not output.
Id: 2084
By: swhite
|
CP02PMCO-WFP01-01-VEL3DK000 |
1/31/19, 7:00 PM | 4/23/19, 12:12 PM |
Deployment 11: No telemetered data from WFP instruments expected from 2019-02-01 onward. Id: 1615 By: cdobson |
CP02PMCO |
4/23/19, 5:00 PM | 10/8/19, 8:02 AM |
UPDATED 2020-02-18: WFP and ADCP data were collected during the deployment and are available as recovered datasets; Deployment 12: No telemetered data expected after 4/24/19. Pesumed to be profiling and WFP data should be available after recovery. Id: 1578 By: cdobson |
CP02PMCO-WFP01 |
12/31/19, 7:00 PM | 6/10/20, 12:07 PM |
Deployment 13: Due to a clock rollover issue, all WFPs have ceased sampling on 1/1/2020. No WFP data are being collected after this date. A resolution is being researched by the vendor. Id: 1882 By: cdobson |