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 | 71 | 69 | 0 | 1 | 0 | 0 | 3,730,926 | 1 | 200 / 196 | Complete | ||||||
2 | recovered_host | 35 | 28 | 0 | 5 | 0 | 0 | 1,116,293 | 1 | 200 / 177 | Complete | ||||||
3 | recovered_host | 15 | 14 | 0 | 0 | 0 | 0 | 483,042 | 1 | 200 / 205 | Complete | ||||||
4 | recovered_host | 32 | 29 | 2 | 0 | 0 | 0 | 1,536,288 | 1 | 200 / 194 | 1 | Complete | |||||
5 | recovered_host | 50 | 48 | 0 | 2 | 0 | 0 | 3,352,550 | 1 | 200 / 194 | 2 | 2 | Complete |
Deployment: | 1 | 2 | 3 | 4 | 5 |
---|---|---|---|---|---|
97% | 80% | 93% | 91% | 96% |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CP05MOAS-GL335 |
11/10/15, 4:00 AM | 11/17/15, 9:34 AM |
Deployment 2: Glider experienced a leak in the bellophram and needed to be recovered early. No data expected after 2015-11-10T09:00:00.
Id: 638
By: cdobson
|
CP05MOAS-GL335 |
4/17/16, 8:00 PM | 4/18/16, 7:23 PM |
Deployment 3: Glider was accidentally recovered early by a fishing vessel on 2016-04-18; no data are expected after this date.
Id: 2034
By: cdobson
|
CP05MOAS-GL335 |
3/3/17, 10:00 PM | 3/6/17, 5:45 PM |
Deployment 5: Glider was struck by a vessel on the surface and needed to be recovered. No data are expected after 2017-03-04T03:00:00.
Id: 639
By: cdobson
|
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CP05MOAS |
Bad altimeter pings are apparent in many deployments of the coastal gliders. A few example plots are attached - m_water_depth plotted as semi-transparent bathymetry. By Lori Garzio, on 5/10/19 |
||
CP05MOAS |
Glider optodes typically exhibit a sensor lag of 20-25 seconds. Example attached of several segments with consecutive down and up casts for CP05MOAS-GL335-04-DOSTAM000 on 10/26/2015 showing a typical measurement time lag. Profiles should be analyzed for individual time lags and data should be adjusted. OOI doesn't necessarily need to make the adjustment but users should be aware of the issue. By Lori Garzio, on 5/15/19 |
||
CP05MOAS-GL335-05-PARADM000 |
sci_bsipar_par is the unscaled L0 PAR data product. The global ranges for this parameter are the same as for the scaled L1 PAR data product [0.0, 2500.0]. The global range for sci_bsipar_par should be reviewed. By Lori Garzio, on 5/15/19 |
||
CP05MOAS-GL335 Deployment: 1 |
|||
CP05MOAS-GL335-05-PARADM000 Deployment: 1 |
|||
CP05MOAS-GL335-05-PARADM000 Deployment: 2 |
|||
CP05MOAS-GL335 Deployment: 3 |
Short deployment (15 days) should be annotated. By Lori Garzio, on 5/15/19 |
||
CP05MOAS-GL335-05-PARADM000 Deployment: 3 |
|||
CP05MOAS-GL335 Deployment: 4 |
|||
CP05MOAS-GL335-05-PARADM000 Deployment: 4 |
|||
CP05MOAS-GL335-05-PARADM000 Deployment: 5 |
parad_m_par data for deployment 5 is a record of NaNs. According to the provenance.json file, the calibration factor 'CC_bsipar_par_scaling' is missing. By Lori Garzio, on 5/15/19 |