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 | KN-224 | 12/14/2014 | 12/29/2014 | CGMCP-03ISSM-00001 | CGINS-METLGR-00013 | 40.3619 | -70.878 | 0 | 94 | |
2 Review | AT-27 | 05/09/2015 | 10/21/2015 | CGMCP-03ISSM-00002 | CGINS-METLGR-00013 | 40.3595 | -70.8853 | 0 | 97 | |
3 Review | AT-31 | 10/21/2015 | 05/14/2016 | CGMCP-03ISSM-00003 | CGINS-METLGR-00023 | 40.3647 | -70.8884 | 0 | 96 | |
4 Review | AR-04 | 05/28/2016 | 10/15/2016 | CGMCP-03ISSM-00004 | CGINS-METLGR-00008 | 40.3595 | -70.885 | 0 | 95 | |
5 Review | AR-08 | 10/11/2016 | 06/15/2017 | CGMCP-03ISSM-00005 | CGINS-METLGR-00012 | 40.3619 | -70.8783 | 0 | 92 | |
6 Review | AR-18 | 06/15/2017 | 11/01/2017 | CGMCP-03ISSM-00006 | CGINS-METLGR-00033 | 40.3671 | -70.8816 | 0 | 93 | |
7 Review | AR-24 | 11/01/2017 | 03/28/2018 | CGMCP-03ISSM-00007 | CGINS-METLGR-00012 | 40.359 | -70.8855 | 0 | 93 | |
8 Review | AR-28 | 03/25/2018 | 10/26/2018 | CGMCP-03ISSM-00008 | CGINS-METLGR-00033 | 40.3672 | -70.8821 | 0 | 94 | |
9 Review | AR-31 | 10/29/2018 | 04/06/2019 | CGMCP-03ISSM-00009 | CGINS-METLGR-00012 | 40.3673 | -70.8811 | 0 | 92 | |
10 Review | AR-34 | 04/07/2019 | 10/01/2019 | CGMCP-03ISSM-00010 | CGINS-METLGR-00033 | 40.3672 | -70.8815 | 0 | 93 | |
11 Review | AR-39 | 09/26/2019 | CGMCP-03ISSM-00011 | CGINS-METLGR-00012 | 40.3594 | -70.8851 | 0 | 93 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CP03ISSM-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/5/19 |
||
CP03ISSM-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/5/19 |
||
CP03ISSM-SBD11-06-METBKA000 |
eastward_velocity and northward_velocity (from the collocated VELPT) don't have any units or description in the recovered_host-metbk_a_dcl_instrument_recovered METBK .nc file for deployments 2, 3 and 6. By Lori Garzio, on 4/5/19 |
||
CP03ISSM-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/5/19 |
||
CP03ISSM-SBD11-06-METBKA000 |
for all deployment met_netlirr data in the metbk_hourly stream have no valid data. Data in files are either nans, fill values, or outside global ranges [200.0, 500.0]. By Leila Belabbassi, on 2/27/19 |
||
CP03ISSM-SBD11-06-METBKA000 Deployment: 2 |
|||
CP03ISSM-SBD11-06-METBKA000 Deployment: 2 |
|||
CP03ISSM-SBD11-06-METBKA000 Deployment: 2 |
data gap not annotated in the system: By Leila Belabbassi, on 2/27/19 |
||
CP03ISSM-SBD11-06-METBKA000 Deployment: 2 |
9/18/15, 6:07 PM | 9/29/15, 10:05 AM |
Data gap should be annotated. By Lori Garzio, on 4/5/19 |
CP03ISSM-SBD11-06-METBKA000 Deployment: 3 |
Downwelling Shortwave Irradiance (shortwave_irradiance) and Net Shortwave Irradiance (met_netsirr) minimum night time values jump from ~0 W m-2 to ~13-14 W m-2 in Dec 2015 and remain there through the rest of the deployment. The same 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/5/19 |
||
CP03ISSM-SBD11-06-METBKA000 Deployment: 6 |
|||
CP03ISSM-SBD11-06-METBKA000 Deployment: 6 |
8/10/17, 12:00 AM | 9/1/17, 12:00 AM | |
CP03ISSM-SBD11-06-METBKA000 Deployment: 6 |
9/22/17, 12:00 AM | 11/1/17, 2:17 PM | |
CP03ISSM-SBD11-06-METBKA000 Deployment: 7 |
|||
CP03ISSM-SBD11-06-METBKA000 Deployment: 7 |
|||
CP03ISSM-SBD11-06-METBKA000 Deployment: 7 |
surface current direction data do not match when comparing recoverd and telemetered data. By Leila Belabbassi, on 2/28/19 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CP03ISSM-SBD11-06-METBKA000 Method: recovered_host |
12/14/14, 1:52 PM | 12/29/14, 7:00 PM |
No recovered data available because the Instrument was lost.
Id: 438
By: leila
|
CP03ISSM-SBD11-06-METBKA000 Stream: metbk_a_dcl_instrument |
4/29/18, 11:42 AM | 5/30/18, 1:09 PM |
Sensor reporting bad data (more information to be determined).
Id: 1383
By: leila
|
CP03ISSM-SBD11 Method: telemetered |
6/18/18, 2:05 AM | 10/28/18, 11:43 PM |
Instruments were temporarily disabled due to power constraints. The instruments could be revived to send data via telemetry when sufficient power is available. Note: Instruments may continue to collect data on internal battery power.
Id: 1563
By: leila
|
CP03ISSM-SBD11-06-METBKA000 |
6/29/19, 8:00 AM |
Deployment 10: Wind sensor failed on 6/29/2019 and any telemetered data after this date is not valid. Id: 1627 By: cdobson |
|
CP03ISSM |
1/7/20, 7:00 PM |
Deployment 11: UPDATED 2020-04-27: As of 2020-03-12 telemetered data for most instruments are being sent home via Iridium. A gap in telemetered data is expected between 2020-01-08 and 2020-03-12 and will not be backfilled but these data will be available upon recovery.* As of 2020-01-08 both fleet broadband telemetry pathways have failed and data can no longer be telemetered to shore from this mooring. Instruments will continue to log data which will be available upon recovery.
Id: 1889
By: cdobson
|