Nitrate

Reference Designator
CE06ISSM-RID16-07-NUTNRB000
Review Status
Review Complete
Note
Data generally look suspect for all deployments because of the prevalence of negative values - did not calculate final data ranges.
Depth
7m
Class
NUTNR (Nitrate)
Make / Model
Satlantic / ISUS

Dataset Reviews Last processed: 7/22/19, 1:27 PM

QC Check Info
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 186 185 0 0 0 0 72,994 1 7 / 1 1 2 Complete
2 recovered_inst 187 160 0 0 3 28 49,817 7 / 1 1 2 Complete
3 recovered_inst 207 19 0 187 0 0 7,493 1 7 / 1 1 2 Complete
4 recovered_inst 142 10 0 131 0 0 2,076 1 7 / 1 1 2 Complete
5 recovered_inst 201 44 0 156 0 0 18,569 1 7 / 1 1 2 Complete
6 recovered_inst 176 106 0 70 0 0 14,669 1 7 / 1 1 2 Complete
7 telemetered 175 73 0 101 0 0 13,876 1 7 / 1 1 2 Complete
8 recovered_inst / Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison
  2. missing: ['pressure']

Data Coverage

Deployment: 12345678
42%
99%86%9%7%22%60%

Lat/Lon Differences (km)

Deployment: 12345678
1 0.00
2 1.630.00
3 1.860.260.00
4 2.070.440.240.00
5 1.900.280.080.170.00
6 1.960.330.120.130.060.00
7 2.010.390.160.090.110.060.00

System Annotations

Metadata Start Date End Date Comment
CE06ISSM
10/7/14, 3: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: 897 By: michaesm

CE06ISSM-RID16-07-NUTNRB000
5/14/16, 8:00 PM 4/14/17, 8:00 PM

The NUTNR started to show signs of degraded performance, variable values spanning +- ranges, then completely failed.

Id: 906 By: michaesm
Flag: not_operational Exclude: No

CE06ISSM
7/26/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. 11 instruments offline.

Id: 898 By: michaesm
Flag: not_operational Exclude: No

CE06ISSM
12/31/16, 7:00 PM 4/22/17, 8:00 PM

The buoy main battery voltage is being drawn down faster than expected. Have shutdown further power to DCL17 and to the OPTAA on DCL16. This takes the following instruments offline:
DCL17
MOPAK
CTDBP (with attached FLORT)
VELPT
ACOMM
OPTAA
Have had to power off DCL17 and DCL16 and reduce call in frequency to 12 hours. Will still (at least should) receive data from MFN. Instruments affected are:
DCL17 (Buoy)
MOPAK
CTDBP3 (with FLORT)
VELPT1
UCSPP (aka ACOMM)
DCL16 (NSIF)
CTDBP1 (with DOSTA) (should internally log)
FLORT
PCO2W1 (should internally log)
PHSEN1 (should internally log)
OPTAA1
NUTNR (should internally log)
SPKIR
VELPT2 (should internally log)

Id: 899 By: michaesm

CE06ISSM
10/2/17, 8:00 PM 3/2/18, 3:44 AM

CAMDS not serviced by vendor in time for deployment

Id: 1236 By: michaesm
Flag: not_operational Exclude: No

CE06ISSM-RID16-07-NUTNRB000
12/17/17, 7:30 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: 1411 By: lgarzio

CE06ISSM-RID16-07-NUTNRB000
Method: telemetered
5/23/20, 8:00 PM 6/22/20, 2:45 PM

Reduced battery power on the mooring (unforeseen delay of mooring recovery well past the originally scheduled date) has resulted in the decision to reduce the operational schedule for this sensor for. Data, at a reduced sample rate, will be collected and telemetered to shore for as long as possible.

Id: 2199 By: wingardc

CE06ISSM-RID16-07-NUTNRB000
Method: telemetered
6/22/20, 2:45 PM

Reduced battery power on the mooring (unforeseen delay of mooring recovery well past the originally scheduled date) has resulted in the decision to power off this sensor for the remainder of the deployment.

Id: 2202 By: wingardc
Flag: not_operational Exclude: No

Review Notes

Metadata Start Date End Date Comment
CE06ISSM-RID16-07-NUTNRB000

There is no pressure variable in the .nc files. This should be a coordinate.

By Lori Garzio, on 7/23/19

CE06ISSM-RID16-07-NUTNRB000

Annotation ID 1411 should be updated when the parser is complete and the data from the new instruments is ingested.

By Lori Garzio, on 7/23/19

CE06ISSM-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 7/23/19

CE06ISSM-RID16-07-NUTNRB000
Deployment: 2
4/10/15, 4:30 AM 10/13/15, 11:45 PM

Suspect data - 80% of the values for nitrate_concentration are outside of global ranges

By Lori Garzio, on 7/23/19

CE06ISSM-RID16-07-NUTNRB000
Deployment: 3

Missing data for deployment 3 should be annotated.

By Lori Garzio, on 7/23/19

CE06ISSM-RID16-07-NUTNRB000
Deployment: 3
10/13/15, 10:54 PM 5/6/16, 3:00 PM

Suspect data - 92% of the values for salinity_corrected_nitrate are outside of global ranges

By Lori Garzio, on 7/23/19

CE06ISSM-RID16-07-NUTNRB000
Deployment: 4
5/6/16, 2:24 AM 9/24/16, 3:33 PM

Suspect data - see annotation ID 906 (the end date for this annotation spans multiple deployments and should be reviewed)

By Lori Garzio, on 7/23/19

CE06ISSM-RID16-07-NUTNRB000
Deployment: 5
11/1/16, 12:00 AM 4/15/17, 2:00 PM

highly variable nitrate_concentration values towards the end of the deployment, including negative values - possible biofouling?

By Lori Garzio, on 7/23/19

CE06ISSM-RID16-07-NUTNRB000
Deployment: 6
4/13/17, 7:53 PM 10/5/17, 1:53 PM

Suspect data - 43% and 16% of the values for salinity_corrected_nitrate and nitrate_concentration are outside of global ranges (mostly negative)

By Lori Garzio, on 7/23/19

CE06ISSM-RID16-07-NUTNRB000
Deployment: 7

Only telemetered data are available for this deployment. Recovered data need to be ingested - the ingest csv indicates that the data weren't ingested because a new parser needs to be developed, but this dataset should still be the old ISUS data and can be ingested with the original parsers.

By Lori Garzio, on 7/23/19

CE06ISSM-RID16-07-NUTNRB000
Deployment: 7
10/5/17, 11:35 PM 3/28/18, 5:54 PM

Suspect data - 19% and 16% of the values for salinity_corrected_nitrate and nitrate_concentration are outside of global ranges (mostly negative)

By Lori Garzio, on 7/23/19

New Note