Velocity Profiler (75 kHz)

Reference Designator
GP03FLMB-RIM01-02-ADCPSL007
Review Status
Review Complete
Note
Depth
500m
Class
ADCPS (Velocity Profiler (long range))
Make / Model
Teledyne RDI / WorkHorse LongRanger Sentinel 75khz - inductive

Dataset Reviews Last processed: 8/20/19, 3:43 PM

QC Check Info
Dep. Preferred Method Stream DD FD SG EG Gaps GD TS Rate (s) Pressure Comp. Time Order Valid Data Missing Data Data Comp. Missing Coords. Review
1 recovered_inst adcp_velocity_earth 330 329 0 0 0 0 7,889 3,600 501 / 10 1 Complete
2 recovered_inst adcp_velocity_earth 353 352 0 0 0 0 8,446 3,600 503 / 490 1 Complete
3 recovered_inst adcp_velocity_earth 392 392 0 0 0 0 9,381 3,600 519 / 513 1 Complete
4 recovered_inst adcp_velocity_earth 379 378 0 0 0 0 9,064 3,600 / 512 1 Complete
5 recovered_inst adcp_velocity_earth 377 377 0 0 0 0 9,019 3,600 / 516 1 Complete
Data Ranges Review Images

Test Notes

  1. no comparison: timestamps do not match

Data Coverage

Deployment: 12345
adcp_velocity_earth 100%100%100%100%100%

Lat/Lon Differences (km)

Deployment: 12345
1 0.00
2 0.220.00
3 0.260.110.00
4 0.340.220.110.00
5 9.599.809.869.920.00

System Annotations

Metadata Start Date End Date Comment
GP03FLMB-RIM01-02-ADCPSL007
Method: telemetered
Stream: adcps_jln_sio_mule_instrument
7/24/13, 2:32 AM

Telemetered inductive ADCP data is in pd12 format which does not include the depth-to-first-bin value which is needed for proper calculation of the data products. A nominal value is entered into the system so that telemetered data can be used when needed. For the best data the recovered data in pd0 format should be used.

Id: 1925 By: cdobson

GP03FLMB
7/24/13, 2:32 AM 6/17/14, 8:00 PM

Deployment 1: Mooring was deployed 5-10m shallower than planned.

Id: 154 By: lgarzio

GP03FLMB
6/19/14, 10:00 PM 6/6/15, 8:00 PM

Deployment 2: Mooring was deployed 10-15m shallower than planned. Upon recovery of platform, biofouling was apparent on shallow CTDs.

Id: 155 By: lgarzio

GP03FLMB
6/8/15, 5:25 PM 7/3/16, 2:35 PM

Deployment 3: Mooring was deployed 10m deeper than planned.

Id: 156 By: lgarzio

GP03FLMB
7/4/16, 7:07 PM 7/17/17, 11:02 AM

Deployment 4: Mooring was deployed 10m deeper than planned.

Id: 157 By: lgarzio

GP03FLMB-RIM01-02-ADCPSL007
7/14/17, 6:49 PM 7/25/18, 1:11 PM

Deployment 5: it was discovered upon recovery that the main controller ceased logging data from this instrument 2017-11-26. No recovered host data are available after this date. Due to the fact that gliders were not deployed at Papa this year, no telemetered data are availble for the deployment. Recovered instrument data are available for the entire deployment.

Id: 2177 By: cdobson
Flag: not_operational Exclude: No

GP03FLMB
7/14/17, 6:49 PM 7/25/18, 1:11 PM

Deployment 5: Telemetered data are not available for this deployment because gliders were not deployed.

Id: 142 By: lgarzio

Review Notes

Metadata Start Date End Date Comment
GP03FLMB
7/4/16, 11:07 PM 7/25/18, 5:11 PM

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

By Lori Garzio, on 1/3/19

GP03FLMB-RIM01-02-ADCPSL007
Deployment: 1

bin_depths are negative for this deployment - this should be investigated and fixed

By Lori Garzio, on 8/22/19

GP03FLMB
Deployment: 5

Annotation ID 1531: recovered_host data are not available for download (Redmine 13628). Issue should be addressed and annotation needs be updated.

By Lori Garzio, on 1/10/19

GP03FLMB
Deployment: 5
7/14/17, 10:49 PM 7/25/18, 5:11 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/4/19

New Note