Method | Data Stream | Content | Type | |
---|---|---|---|---|
recovered_host | metbk_a_dcl_instrument_recovered | Data Products | Report M2M Stats | Science |
recovered_host | metbk_hourly | Flux Data Products Calculated From Hourly Averages | Report M2M Stats | Science |
telemetered | metbk_a_dcl_instrument | Data Products | Report M2M Stats | Science |
telemetered | metbk_hourly | Flux Data Products Calculated From Hourly Averages | Report M2M Stats | Science |
Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
---|---|---|---|---|---|---|---|---|---|---|
1 Review | OC1503D | 04/09/2015 | 09/25/2015 | CGMCE-09OSSM-00001 | CGINS-METLGR-00007 | 46.8539 | -124.958 | 0 | 542 | |
2 Review | OC1510A | 10/15/2015 | 05/07/2016 | CGMCE-09OSSM-00002 | CGINS-METLGR-00012 | 46.8531 | -124.954 | 0 | 542 | |
3 Review | TN-342 | 05/12/2016 | 09/22/2016 | CGMCE-09OSSM-00003 | CGINS-METLGR-00009 | 46.8537 | -124.961 | 0 | 542 | |
4 Review | AT37-03 | 09/20/2016 | 04/14/2017 | CGMCE-09OSSM-00004 | CGINS-METLGR-00014 | 46.8508 | -124.972 | 0 | 542 | |
5 Review | SKQ201704S | 04/12/2017 | 10/06/2017 | CGMCE-09OSSM-00005 | CGINS-METLGR-00009 | 46.8529 | -124.959 | 0 | 542 | |
6 Review | SKQ201715S | 10/04/2017 | 03/30/2018 | CGMCE-09OSSM-00006 | CGINS-METLGR-00025 | 46.8478 | -124.984 | 0 | 542 | |
7 Review | SKQ201808S | 03/26/2018 | 09/19/2018 | CGMCE-09OSSM-00007 | CGINS-METLGR-00006 | 46.853 | -124.958 | 0 | 554 | |
8 Review | SR1813 | 09/19/2018 | 04/25/2019 | CGMCE-09OSSM-00008 | CGINS-METLGR-00025 | 46.849 | -124.978 | 0 | 542 | |
9 Review | SKQ201910S | 04/24/2019 | 10/13/2019 | CGMCE-09OSSM-00009 | CGINS-METLGR-00030 | 46.8527 | -124.954 | 0 | 542 | |
10 Review | SKQ201921S | 10/11/2019 | CGMCE-09OSSM-00010 | CGINS-METLGR-00009 | 46.865 | -124.948 | 0 | 542 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE09OSSM-SBD11-06-METBKA000 |
met_current_speed, met_relwind_speed, met_wind10m, shortwave_irradiance, and met_netsirr global ranges should be reviewed. See review notes for CP01CNSM-SBD11-06-METBKA000 for more details. By Lori Garzio, on 4/9/19 |
||
CE09OSSM-SBD11-06-METBKA000 |
metbk_hourly data will not be reviewed because of issues producing the data products have not been resolved - see Redmine tickets 13111, 13113, 13221. Data plots are available in the review images. By Lori Garzio, on 4/9/19 |
||
CE09OSSM-SBD11-06-METBKA000 |
These variables are missing global ranges for this instrument: stream metbk_hourly - met_buoyfls, met_buoyflx, met_frshflx, met_heatflx, met_latnflx, met_mommflx, met_rainflx, met_sensflx, met_netsirr_hourly. stream metbk_a_dcl_instrument and metbk_a_dcl_instrument_recovered: met_windavg_mag_corr_east, met_windavg_mag_corr_north, met_heatflx_minute, met_latnflx_minute, met_netlirr_minute, met_sensflx_minute. By Lori Garzio, on 4/9/19 |
||
CE09OSSM-SBD11-06-METBKA000 |
|||
CE09OSSM-SBD11-06-METBKA000 Deployment: 1 |
Downwelling Shortwave Irradiance (shortwave_irradiance) and Net Shortwave Irradiance (met_netsirr) minimum values jump to ~13-14 W m-2 shortly after deployment (should be around 0 W m-2). A similar issue was seen on GS01SUMO-SBD11-06-METBKA000 (see annotation ID 1522 and Redmine 12543). This should be investigated and annotated. By Lori Garzio, on 4/9/19 |
||
CE09OSSM-SBD11-06-METBKA000 Deployment: 1 |
Data gap (2015-04-11T16:56:44 to 2015-04-20T18:32:34) and missing data at the end of the deployment should be annotated. By Lori Garzio, on 4/9/19 |
||
CE09OSSM-SBD11-06-METBKA000 Deployment: 1 |
5/10/15, 12:00 AM | 9/5/15, 8:10 AM | |
CE09OSSM-SBD11-06-METBKA000 Deployment: 1 |
6/1/15, 12:00 AM | 9/5/15, 8:10 AM | |
CE09OSSM-SBD11-06-METBKA000 Deployment: 1 |
8/10/15, 12:00 AM | 9/5/15, 8:10 AM | |
CE09OSSM-SBD11-06-METBKA000 Deployment: 2 |
10/15/15, 11:06 PM | 5/7/16, 3:28 PM |
sea_surface_temperature values are -5, sea_surface_conductivity values are 0.0, and met_salsurf values are 0.0. It looks like other variables are using these data in their calculations, which is creating bad data products. This should be investigated and annotated. By Lori Garzio, on 4/9/19 |
CE09OSSM-SBD11-06-METBKA000 Deployment: 2 |
12/22/15, 12:00 AM | 5/7/16, 3:28 PM | |
CE09OSSM-SBD11-06-METBKA000 Deployment: 3 |
8/22/16, 12:00 AM | 9/22/16, 3:35 PM |
Suspect CT data. Annotation ID 936 should be updated to indicate that the sensor was replaced By Lori Garzio, on 4/9/19 |
CE09OSSM-SBD11-06-METBKA000 Deployment: 6 |
2/10/18, 12:00 AM | 3/30/18, 7:15 PM |
Suspect CT data - should be investigated and annotated. By Lori Garzio, on 4/9/19 |
CE09OSSM-SBD11-06-METBKA000 Deployment: 7 |
There are no recovered_host data available for download for deployment 7. These data should be available (according to the ingest csv) and if they are not available, the dataset should be annotated to indicate why. By Lori Garzio, on 4/9/19 |
||
CE09OSSM-SBD11-06-METBKA000 Deployment: 7 |
4/10/18, 12:00 AM | 5/1/18, 12:00 AM | |
CE09OSSM-SBD11-06-METBKA000 Deployment: 7 |
6/20/18, 12:00 AM | 9/19/18, 2:15 PM |
Suspect data starting in the middle of the deployment. Something happened in late June 2018 that caused the CT sensor stopped working temporarily. Issue should be investigated and annotated. A similar issue is seen in the data from CE02SHSM-SBD11-06-METBKA000, CE04OSSM-SBD11-06-METBKA000 and CE07SHSM-SBD11-06-METBKA000 from the same time period. By Lori Garzio, on 4/9/19 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE09OSSM-SBD11-06-METBKA000 |
12/22/15, 7:00 PM | 5/11/16, 8:00 PM |
Issue: The Relative Humidity measurement (RELHUMI) from the METBK data logger started reporting erroneous values on 2015-12-23. This instrument was damaged during a storm and replaced on May 12, 2016.
Id: 935
By: michaesm
|
CE09OSSM-SBD11-06-METBKA000 |
8/16/16, 8:00 PM | 10/3/16, 8:00 PM |
The METBK-CT data signal flatlined on 2016/08/17 15:48:20.780. Data from that date forward should be considered as suspect.
Id: 936
By: michaesm
|
CE09OSSM-SBD11-06-METBKA000 Method: telemetered Stream: metbk_a_dcl_instrument |
5/4/20, 6:34 PM |
The rain gauge sensor in the meteorological suite has failed, flat-lining at approximately -1.5 mm on 2020-05-04T22:34:00.
Id: 2205
By: wingardc
|
|
CE09OSSM Method: telemetered |
5/9/20, 8:40 PM | 5/10/20, 8:00 PM |
Due to a bug in the mooring telemetry system, data during this time range was not telemetered to shore. It was recorded on the mooring and instruments and will be available in the recovered data streams.
Id: 2182
By: wingardc
|