| Method | Data Stream | Content | Type | |
|---|---|---|---|---|
| recovered_host | ctdmo_ghqr_offset_recovered | Offset Data | Report M2M | Engineering |
| recovered_host | ctdmo_ghqr_sio_mule_instrument | Data Products | Report M2M Stats | Science |
| recovered_inst | ctdmo_ghqr_instrument_recovered | Data Products | Report M2M Stats | Science |
| telemetered | ctdmo_ghqr_sio_mule_instrument | Data Products | Report M2M Stats | Science |
| telemetered | ctdmo_ghqr_sio_offset | Offset Data | Report M2M | Engineering |
| Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 Review | MV-1309 | 07/24/2013 | 06/18/2014 | CGMGP-03FLMB-00001 | CGINS-CTDMOG-10216 | 50.3317 | -144.401 | 60 | 4145 | |
| 2 Review | MV-1404 | 06/20/2014 | 06/07/2015 | CGMGP-03FLMB-00002 | CGINS-CTDMOG-11641 | 50.3313 | -144.398 | 62 | 4145 | |
| 3 Review | TN-323 | 06/08/2015 | 07/03/2016 | CGMGP-03FLMB-00003 | CGINS-CTDMOG-11652 | 50.3303 | -144.398 | 78 | 4145 | |
| 4 Review | RB-16-05 | 07/04/2016 | 07/17/2017 | CGMGP-03FLMB-00004 | CGINS-CTDMOG-10216 | 50.3293 | -144.398 | 4146 | ||
| 5 Review | SR17-10 | 07/14/2017 | 07/25/2018 | CGMGP-03FLMB-00005 | CGINS-CTDMOG-10221 | 50.3777 | -144.515 | 4169 | ||
| 6 Review | SR1811 | 07/24/2018 | 09/27/2019 | CGMGP-03FLMB-00006 | CGINS-CTDMOG-11654 | 50.3295 | -144.398 | 4145 | ||
| 7 Review | SKQ201920S | 09/27/2019 | CGMGP-03FLMB-00007 | CGINS-CTDMOG-12189 | 50.3755 | -144.514 | 4176 |
| 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 |
| 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
|
|
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 |