Velocity Profiler (75 kHz)

Reference Designator
GP03FLMA-RIM01-02-ADCPSL003
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:42 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,873 3,600 500 / 491 1 1 Complete
2 recovered_inst adcp_velocity_earth 354 353 0 0 0 0 8,466 3,600 500 / 487 2 Complete
3 recovered_inst adcp_velocity_earth 389 389 0 0 0 0 9,309 3,600 520 / 508 2 Complete
4 recovered_inst adcp_velocity_earth 383 32 0 350 0 0 765 3,600 / 517 1 1 Complete
5 recovered_inst adcp_velocity_earth 380 380 0 0 0 0 9,096 3,600 / 515 2 Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison
  2. no comparison: timestamps do not match

Data Coverage

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

Lat/Lon Differences (km)

Deployment: 12345
1 0.00
2 0.620.00
3 0.650.090.00
4 1.160.560.510.00
5 9.069.679.7210.220.00

System Annotations

Metadata Start Date End Date Comment
GP03FLMA-RIM01-02-ADCPSL003
Method: telemetered
Stream: adcps_jln_sio_mule_instrument
7/21/13, 6:44 PM

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: 1928 By: cdobson

GP03FLMA
7/21/13, 6:44 PM 6/14/14, 8:00 PM

Deployment 1: Mooring was deployed 10-15m shallower than planned. Telemetered data are not available for this deployment.

Id: 150 By: lgarzio

GP03FLMA
6/17/14, 2:00 AM 6/4/15, 8:00 PM

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

Id: 151 By: lgarzio

GP03FLMA
6/6/15, 6:40 PM 6/28/16, 3:10 PM

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

Id: 152 By: lgarzio

GP03FLMA
6/30/16, 9:07 PM 7/18/17, 11:13 AM

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

Id: 153 By: lgarzio

GP03FLMA
7/13/17, 7:00 PM 7/27/18, 6:14 PM

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

Id: 141 By: lgarzio

Review Notes

Metadata Start Date End Date Comment
GP03FLMA
7/1/16, 1:07 AM 7/27/18, 10:14 PM

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

By Lori Garzio, on 1/3/19

GP03FLMA-RIM01-02-ADCPSL003
Deployment: 4

Suspect data - data from the majority of the deployment is missing, eastward_seawater_velocities are suspect

By Lori Garzio, on 8/22/19

GP03FLMA
Deployment: 5
7/13/17, 11:00 PM 7/27/18, 10:14 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