Dissolved Oxygen

Reference Designator
GP03FLMB-RIS01-03-DOSTAD000
Review Status
Review Complete
Note
Depth
30m
Class
DOSTA (Dissolved Oxygen Stable Response)
Make / Model
Aanderaa / Optode 4831
Dependency
GP03FLMB-RIM01-02-CTDMOG060

Dataset Reviews Last processed: 7/25/19, 7:22 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_host 330 329 0 0 0 0 31,557 900 30 / 20 Complete
2 recovered_host 353 352 0 0 0 0 33,703 900 31 / 10 1 2 Complete
3 recovered_host 392 166 0 156 1 70 15,618 900 47 / 40 Complete
4 recovered_host 379 21 0 276 1 83 1,758 900 / 39 3 Complete
5 recovered_host 377 91 0 214 1 72 8,479 900 / 36 4 4 2 Complete
Data Ranges Review Images

Test Notes

  1. fail: data found in another stream (gaps: [1] days: [119])
  2. missing: ['pressure']
  3. fail: check ['DO - Pressure Temp Sal Corrected']
  4. no other streams for comparison

Data Coverage

Deployment: 12345
100%100%42%6%24%

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-RIS01-03-DOSTAD000
7/24/13, 2:32 AM 6/17/14, 8:00 PM

Deployment 1: Dissolved oxygen noise was high at various times throughout the deployment, possibly from biofouling.

Id: 776 By: lgarzio
Flag: suspect Exclude: No

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-RIS01-03-DOSTAD000
10/31/14, 8:00 PM 6/6/15, 8:00 PM

Deployment 2: Dissolved oxygen noise increased, possibly from biofouling.

Id: 777 By: lgarzio
Flag: suspect Exclude: No

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-RIS01-03-DOSTAD000
7/14/17, 6:49 PM 7/25/18, 1:11 PM

Deployment 5: it was discovered upon recovery that the secondary controller did not log any data for this instrument between 2017-09-25 and 2017-12-06 or after 2017-12-22. 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 available for the deployment.

Id: 2180 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-RIS01-03-DOSTAD000

Data gaps should be annotated.

By Lori Garzio, on 8/2/19

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-RIS01-03-DOSTAD000
Deployment: 1
7/24/13, 6:32 AM 6/18/14, 12:00 AM

Suspect data, likely due to biofouling - see annotation ID 776

By Lori Garzio, on 8/2/19

GP03FLMB-RIS01-03-DOSTAD000
Deployment: 2

There are 119 days for this deployment where dissolved_oxygen (umol kg-1) data are available in the telemetered stream and not in the recovered_host stream. These data should be available in the recovered_host data stream.

By Lori Garzio, on 8/2/19

GP03FLMB-RIS01-03-DOSTAD000
Deployment: 2
10/31/14, 12:00 AM 6/7/15, 12:00 AM

Suspect data likely due to biofouling - see annotation ID 777

By Lori Garzio, on 8/2/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