Method | Data Stream | Content | Type | |
---|---|---|---|---|
recovered_host | nutnr_b_dcl_conc_instrument_recovered | Data Products | Report M2M Stats | Science |
recovered_host | nutnr_b_dcl_conc_metadata_recovered | Metadata | Report M2M | Engineering |
recovered_host | nutnr_b_dcl_dark_conc_instrument_recovered | Dark Sample Data Products | Report M2M Stats | Science |
recovered_inst | nutnr_b_dark_instrument_recovered | Dark Sample Data Products | Report M2M Stats | Science |
recovered_inst | nutnr_b_instrument_recovered | Data Products | Report M2M Stats | Science |
recovered_inst | nutnr_b_metadata_recovered | Metadata | Report M2M | Engineering |
telemetered | nutnr_b_dcl_conc_instrument | Data Products | Report M2M Stats | Science |
telemetered | nutnr_b_dcl_conc_metadata | Metadata | Report M2M | Engineering |
telemetered | nutnr_b_dcl_dark_conc_instrument | Dark Sample Data Products | Report M2M Stats | Science |
Deployment | Cruise | Start Date | Stop Date | Mooring Asset | Node Asset | Sensor Asset | Latitude | Longitude | Deployment Depth | Water Depth |
---|---|---|---|---|---|---|---|---|---|---|
1 Review | OC1404B | 04/17/2014 | 08/16/2014 | CGMCE-01ISSM-00001 | CGINS-NUTNRB-00243 | 44.6583 | -124.096 | 7 | 25 | |
2 Review | OC1410A | 10/10/2014 | 04/12/2015 | CGMCE-01ISSM-00002 | CGINS-NUTNRB-00254 | 44.6583 | -124.096 | 7 | 25 | |
3 Review | PS1506A | 06/03/2015 | 10/07/2015 | CGMCE-01ISSM-00003 | CGINS-NUTNRB-00264 | 44.6583 | -124.095 | 7 | 25 | |
4 Review | OC1510A | 10/08/2015 | 05/10/2016 | CGMCE-01ISSM-00004 | CGINS-NUTNRB-00286 | 44.6601 | -124.096 | 7 | 25 | |
5 Review | TN-342 | 05/18/2016 | 10/02/2016 | CGMCE-01ISSM-00005 | CGINS-NUTNRB-00263 | 44.6583 | -124.095 | 7 | 24 | |
6 Review | AT37-03 | 09/30/2016 | 04/17/2017 | CGMCE-01ISSM-00006 | CGINS-NUTNRB-00265 | 44.6598 | -124.095 | 7 | 25 | |
7 Review | SKQ201704S | 04/19/2017 | 10/12/2017 | CGMCE-01ISSM-00007 | CGINS-NUTNRB-00254 | 44.6563 | -124.095 | 7 | 25 | |
8 Review | SKQ201715S | 10/12/2017 | 04/01/2018 | CGMCE-01ISSM-00008 | CGINS-NUTNRB-01056 | 44.6597 | -124.095 | 7 | 25 | |
9 Review | SKQ201808S | 04/03/2018 | 09/30/2018 | CGMCE-01ISSM-00009 | CGINS-NUTNRB-01115 | 44.6568 | -124.096 | 7 | 25 | |
10 Review | SR1813 | 09/29/2018 | 04/27/2019 | CGMCE-01ISSM-00010 | CGINS-NUTNRB-01061 | 44.6598 | -124.095 | 7 | 25 | |
11 Review | SKQ201910S | 04/20/2019 | 10/22/2019 | CGMCE-01ISSM-00011 | CGINS-NUTNRB-01058 | 44.6568 | -124.095 | 7 | 25 | |
12 Review | SKQ201921S | 10/20/2019 | CGMCE-01ISSM-00012 | CGINS-NUTNRB-01164 | 44.6598 | -124.095 | 7 | 25 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE01ISSM-RID16-07-NUTNRB000 |
NUTNR timestamps between recovered_inst and recovered_host/telemetered data are offset, so comparisons between the two methods based on timestamp is invalid. In the attached figures, timestamp_offset1 is from the beginning of deployment 2 and timestamp_offset2 is at the end of deployment 2. The first column is recovered_host data and the second column is recovered_inst data. By Lori Garzio, on 5/28/19 |
||
CE01ISSM-RID16-07-NUTNRB000 |
Annotation ID 1408 should be updated when the new SUNA parser is available and data are ingested. By Lori Garzio, on 5/29/19 |
||
CE01ISSM-RID16-07-NUTNRB000 |
The .nc files for all deployments are missing pressure. By Lori Garzio, on 5/29/19 |
||
CE01ISSM-RID16-07-NUTNRB000 |
Data generally look suspect for all deployments of this instrument (the ISUS model) because of the prevalence of negative values. The dataset should be annotated if there is a known issue with this instrument to inform users if all or some data should be considered suspect. By Lori Garzio, on 5/30/19 |
||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 1 |
The recovered_inst data are not available for download from deployment 1. According to the ingest csv, the parser wasn't working. These data need to be ingested or annotated to indicate why the full recovered dataset isn't available. By Lori Garzio, on 5/29/19 |
||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 1 |
|||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 2 |
|||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 3 |
7/29/15, 12:00 AM | 8/25/15, 12:00 AM | |
CE01ISSM-RID16-07-NUTNRB000 Deployment: 4 |
|||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 4 |
11/8/15, 12:00 AM | 5/10/16, 3:22 PM |
The missing data at the end of deployment 4 should be annotated. By Lori Garzio, on 5/30/19 |
CE01ISSM-RID16-07-NUTNRB000 Deployment: 5 |
|||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 5 |
97% of the salinity_corrected_nitrate data are fill values (no CTD data available for the correction). By Lori Garzio, on 5/30/19 |
||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 6 |
|||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 7 |
|||
CE01ISSM-RID16-07-NUTNRB000 Deployment: 7 |
salinity_corrected_nitrate data are all fill values. According to the provenance.json file, ctdbp_seawater_temperature and practical_salinity are missing because the recovered_inst data from CE01ISSM-RID16-03-CTDBPC000 are missing for deployment 7. By Lori Garzio, on 5/30/19 |
Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE01ISSM |
4/17/14, 4:45 PM | 9/30/16, 8:00 PM |
All of the inshore surface moorings suffer from an issue called the 'top of the day problem.' A race condition exists in the CPM firmware when transferring daily log files harvested from the various sub-components in a buoy system (e.g. DCL16, CPM3, DCL35, etc) over the Iridium RUDICS connection. The primary CPM rsync's data files from the various sub-components to a central data directory. The first time a daily file is created/copied into that directory (usually shortly after midnight), a compressed copy of the file is created and that compressed file is queued up in a separate text file for transmission to shore. The transfer routine reads that text file and processes the files from that list in order from top to bottom. Once that compressed file is transferred to shore, no further updates for that file are sent to shore. Meanwhile, the CPM continues to rsync data from the different sub-components, updating the original daily log file. The net result is that data is accumulating in the daily log file for an instrument, but we may see only one record (or none) depending on when the rsync job occurred and the compressed file was created and staged for transfer to shore. This affects telemetered data only. Id: 868 By: michaesm |
CE01ISSM |
8/7/16, 8:00 PM | 10/3/16, 8:00 PM |
Correcting the iridium data telemetry issues, permitting full telemetry of data files, resulting in greater power consumption than anticipated. Result is power level of the battery pack has dropped below operational limits and subsystems can no longer power instruments. Shutting the mooring down, and placing in a low power maintenance mode.
Id: 869
By: michaesm
|
CE01ISSM |
12/11/16, 7:00 PM | 5/30/17, 8:00 PM |
On Monday, Mon Dec 12 15:30:00 2016, stopped receiving any data from CTDBP3. No indication as to possible cause.
Id: 870
By: michaesm
|
CE01ISSM |
2/5/17, 7:00 PM | 4/30/17, 8:00 PM |
The buoy and mfn battery voltages have been drawn down faster than expected. Have shutdown further power to DCL16, DCL17, CPM3, and DCL37 (DCL35 failed several weeks ago). This takes the following instruments offline: DCL17
Id: 871
By: michaesm
|
CE01ISSM-RID16-07-NUTNRB000 |
8/6/17, 7:00 AM |
The Satlantic ISUS instrument has been discontinued, and all OOI ISUS units have been converted to the Sea-Bird SUNA model. A new data parser is in development, and any resulting data gaps will be filled once the parser has been delivered and the data are processed. Id: 1408 By: lgarzio |
|
CE01ISSM-RID16 Method: telemetered |
1/11/20, 1:45 PM |
During a large storm event on 2020-01-11, the surface buoy and NSIF broke free and went adrift. The buoy and NSIF were recovered from the beach the following mooring. No further data will be collected from these systems for the remainder of this deployment.
Id: 1893
By: wingardc
|