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 | 3,943 | 7,200 | 30 / | 1 | Complete | |||||
2 | recovered_inst | 352 | 352 | 0 | 0 | 0 | 0 | 4,211 | 7,200 | 31 / | 2 | 1 | Complete | ||||
3 | recovered_inst | 392 | 391 | 0 | 0 | 0 | 0 | 4,688 | 7,200 | 47 / | 1 | Complete | |||||
4 | recovered_inst | / | Complete | ||||||||||||||
5 | recovered_inst | 377 | 370 | 6 | 0 | 0 | 0 | 4,437 | 7,200 | / | 1 | Complete |
Deployment: | 1 | 2 | 3 | 4 | 5 |
---|---|---|---|---|---|
100% | 100% | 100% | 98% |
Deployment: | 1 | 2 | 3 | 4 | 5 |
---|---|---|---|---|---|
1 | 0.00 | ||||
2 | 0.22 | 0.00 | |||
3 | 0.26 | 0.11 | 0.00 | ||
5 | 9.59 | 9.80 | 9.86 | 0.00 |
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-RIS01-04-PHSENF000 |
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-24 and 2017-12-07 or after 2017-12-31. 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. Recovered instrument data are available for the entire deployment.
Id: 2178
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 |
GP03FLMB-RIS01-04-PHSENF000 Method: telemetered |
7/24/18, 7:01 PM | 9/27/19, 7:55 PM |
Deployment 6: There will be no telemetered data from this instrument due to issues between the instrument and controller. The instrument is logging internally and data should be available at recovery. Id: 1498 By: cdobson |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
GP03FLMB-RIS01-04-PHSENF000 |
pressure coordinate are missing in the data files By Leila Belabbassi, on 5/30/19 |
||
GP03FLMB-RIS01-04-PHSENF000 |
7/24/13, 12:00 AM | 6/18/14, 12:00 AM |
suspect data By Leila Belabbassi, on 5/30/19 |
GP03FLMB-RIS01-04-PHSENF000 |
9/25/15, 12:00 AM | 10/25/15, 12:00 AM |
suspect data By Leila Belabbassi, on 5/30/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-04-PHSENF000 |
7/14/16, 12:00 AM | 8/5/18, 12:00 AM |
suspect data By Leila Belabbassi, on 5/30/19 |
GP03FLMB-RIS01-04-PHSENF000 Deployment: 4 |
recovered data are missing in the system By Leila Belabbassi, on 5/30/19 |
||
GP03FLMB-RIS01-04-PHSENF000 Deployment: 4 |
7/4/16, 12:00 AM | 7/1/17, 12:00 AM |
Deployment 4 - instrument not telemetering data. Issue under investigation. UPDATE 11/15/2016: Either this instrument is having issues, or the entire secondary controller is malfunction. There are multiple low battery warnings that appear to originate from the SSIOC. The issue is under investigation.
By Lori Garzio,
on 8/1/16
|
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 |