CTD (60 m)

Reference Designator
GP03FLMB-RIM01-02-CTDMOG062
Review Status
Review Complete
Note
Deployment 2 data gaps should be investigated.
Depth
60m
Class
CTDMO (CTD Mooring (Inductive))
Make / Model
Sea-Bird / SBE 37IM

Dataset Reviews Last processed: 12/12/18, 4:32 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 60 / 50 Complete
2 recovered_inst 352 284 0 0 17 85 25,000 900 62 / 47 1 Complete
3 recovered_inst 392 392 0 0 0 0 37,520 900 78 / 69 Complete
4 recovered_inst 379 379 0 0 0 0 36,256 900 / 98 Complete
5 recovered_inst 377 377 0 0 0 0 36,073 900 / 74 2 2 Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [5] days: [30])
  2. no other streams for comparison

Data Coverage

Deployment: 12345
100%81%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

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
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-CTDMOG062
7/4/16, 7:15 PM 7/17/17, 11:00 AM

Deployment 4: Instrument's planned deployment depth was 60m, but it slid to approx. 100m at deployment. This was confirmed upon recovery of the mooring.

Id: 158 By: lgarzio

GP03FLMB-RIM01-02-CTDMOG062
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: 2167 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-CTDMOG062
Deployment: 2
6/26/14, 8:00 AM 5/17/15, 3:45 PM

Data are missing from the recovered_inst stream at relatively regular intervals from 2014-06-26T08:00:01 to 2014-11-06T12:00:01, but data are available in the telemetered stream for those chunks. There are no recovered_host data from deployment 2 for additional comparison. Full list of recovered_inst data gaps (where telemetered data are available) found here in the missing_data column: https://github.com/ooi-data-lab/data-review-tools/blob/master/data_review/output/GP03FLMB/GP03FLMB-RIM01-02-CTDMOG062/GP03FLMB-RIM01-02-CTDMOG062_sciencevar_comparison_summary.csv#L12-L16

There are additional gaps in the recovered_inst dataset that should be investigated. Full list of recovered_inst data gaps for the entire deployment found here in the file_time_gaps column: https://github.com/ooi-data-lab/data-review-tools/blob/master/data_review/output/GP03FLMB/GP03FLMB-RIM01-02-CTDMOG062/GP03FLMB-RIM01-02-CTDMOG062_file_summary.csv#L3

See Redmine ticket 13752

By Lori Garzio, on 1/10/19

GP03FLMB-RIM01-02-CTDMOG062
Deployment: 4
7/4/16, 11:07 PM 7/17/17, 3:02 PM

As confirmed with the pressure data, the instrument slid to approx. 100m at deployment (annotation ID 158). Excluding this dataset from the final statistics.

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