CTD (30 m)
- Reference Designator
- GP03FLMA-RIM01-02-CTDMOG040
- Review Status
- Review Complete
- Note
- Deployment 2 recovered_inst data should be made available for download from uFrame. Deployment 5 data gap should be filled.
- Depth
- 30m
- Class
- CTDMO (CTD Mooring (Inductive))
- Make / Model
- Sea-Bird / SBE 37IM
Dataset Reviews Last processed: 11/28/18, 5:20 PM
| 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 | 28 / 15 | Complete | ||||||
| 2 | telemetered | 353 | 157 | 0 | 195 | 0 | 0 | 914 | 14,400 | 28 / 12 | 1 | 1 | Complete | ||||
| 3 | recovered_inst | 389 | 389 | 0 | 0 | 0 | 0 | 37,234 | 900 | 48 / 33 | Complete | ||||||
| 4 | recovered_inst | 383 | 383 | 0 | 0 | 0 | 0 | 36,728 | 900 | / 42 | Complete | ||||||
| 5 | recovered_inst | 380 | 373 | 0 | 0 | 1 | 8 | 35,581 | 900 | / 40 | 2 | Complete |
Test Notes
- no other streams for comparison
- fail: data found in another stream (gaps: [1] days: [9])
Data Coverage
| Deployment: | 1 | 2 | 3 | 4 | 5 |
|---|---|---|---|---|---|
| 100% | 100% | 100% | 98% | ||
| 44% |
Lat/Lon Differences (km)
| 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 |
Example Composite Data Plot
System Annotations Show
| 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-RIM01-02-CTDMOG040 |
6/17/14, 2:00 AM | 6/4/15, 8:00 PM |
Deployment 2: Upon recovery, a shield that guards the sensor and holds the anti-fouling was missing. Id: 582 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 |
Review Notes
| 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-CTDMOG040 Deployment: 2 |
6/17/14, 6:00 AM | 6/5/15, 12:00 AM |
recovered_inst data are not available for download from uFrame. There is an entry in the ingest csv indicating that the raw data file is available. This should be investigated and the recovered_inst data should be made available for download (or the system should have an annotation indicating why the recovered_inst data are not available). By Lori Garzio, on 1/4/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 |
|
GP03FLMA-RIM01-02-CTDMOG040 Deployment: 5 |
10/28/17, 5:15 AM | 11/5/17, 1:00 PM |
There is a data gap in the recovered_inst data stream from 2017-10-28T05:15:01 to 2017-11-05T13:00:01, however these data are available in the recovered_host data stream. The recovered_inst data should be filled in. See Redmine ticket 13752. By Lori Garzio, on 1/4/19  |