CTD (30 m)

Reference Designator
GP03FLMB-RIM01-02-CTDMOG060
Review Status
Review Complete
Note
Annotation ID 584 should be modified to indicate why recovered data from deployment 2 aren't available
Depth
30m
Class
CTDMO (CTD Mooring (Inductive))
Make / Model
Sea-Bird / SBE 37IM
Children
GP03FLMB-RIS01-03-DOSTAD000

Dataset Reviews Last processed: 12/12/18, 4:30 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 329 329 0 0 0 0 31,557 900 30 / 20 Complete
2 telemetered 352 143 0 209 0 0 845 14,400 31 / 17 1 1 Complete
3 recovered_inst 392 392 0 0 0 0 37,525 900 47 / 39 Complete
4 recovered_inst 379 379 0 0 0 0 36,256 900 / 37 Complete
5 recovered_inst 377 377 0 0 0 0 36,073 900 / 43 1 1 Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison

Data Coverage

Deployment: 12345
100%100%100%100%
41%

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

Example Composite Data Plot

System Annotations

Metadata Start Date End Date Comment
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-RIM01-02-CTDMOG060
6/19/14, 10:00 PM 6/6/15, 8:00 PM

Deployment 2: Recovered data are not available for this deployment.

Id: 584 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-CTDMOG060
7/14/17, 6:49 PM 7/25/18, 1:11 PM

Deployment 5: It was discovered upon recovery that the inductive line was broken during this deployment and no data were sent from the CTDs to the controller. Due to this, and the fact that gliders were not deployed at Papa this year, no recovered host or telemetered data are available for this instrument. Recovered instrument data are available.

Id: 2165 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-CTDMOG060
Deployment: 2
6/20/14, 2:00 AM 6/7/15, 12:00 AM

Annotation ID 584 should provide more information regarding why recovered data are not available for deployment 2.

By Lori Garzio, on 1/9/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