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,493 | 900 | 129 / 117 | Complete | ||||||
2 | recovered_inst | 353 | 266 | 0 | 0 | 11 | 95 | 24,255 | 900 | 129 / 111 | 1 | Complete | |||||
3 | recovered_inst | 389 | 389 | 0 | 0 | 0 | 0 | 37,234 | 900 | 149 / 134 | Complete | ||||||
4 | recovered_inst | 383 | 383 | 0 | 0 | 0 | 0 | 36,728 | 900 | / 143 | Complete | ||||||
5 | recovered_inst | 380 | 380 | 0 | 0 | 0 | 0 | 36,381 | 900 | / 141 | Complete |
Deployment: | 1 | 2 | 3 | 4 | 5 |
---|---|---|---|---|---|
100% | 75% | 100% | 100% | 100% |
Deployment: | 1 | 2 | 3 | 4 | 5 |
---|---|---|---|---|---|
1 | 0.00 | ||||
2 | 0.62 | 0.00 | |||
3 | 0.65 | 0.09 | 0.00 | ||
4 | 1.16 | 0.56 | 0.51 | 0.00 | |
5 | 9.06 | 9.67 | 9.72 | 10.22 | 0.00 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
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 |
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-CTDMOG044 Deployment: 2 |
6/21/14, 4:00 AM | 11/21/14, 8:00 AM |
Data are missing from the recovered_inst stream at relatively regular intervals from 2014-06-21T04:00:01 to 2014-11-21T08: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/GP03FLMA/GP03FLMA-RIM01-02-CTDMOG044/GP03FLMA-RIM01-02-CTDMOG044_sciencevar_comparison_summary.csv#L7-L11 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/GP03FLMA/GP03FLMA-RIM01-02-CTDMOG044/GP03FLMA-RIM01-02-CTDMOG044_file_summary.csv#L3 See Redmine ticket 13752 By Lori Garzio, on 1/7/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 |