Per vendor feedback, the first 1-2 min of each OPTAA instrument sampling period should be considered suspect. Signal drift can occur as the instrument warms up, flushes with seawater, and the filter wheel spins up. Users are encouraged to delete the first minute of data, at a minimum, from each measurement burst and then calculate a median average of the remaining data from the burst before working further with the OPTAA data.

Id: 2095 By: wingardc

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

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
Flag: not_operational Exclude: No

Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

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

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
Flag: not_operational Exclude: No

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:
DCL16
CTDBP + DOSTA (probably internally recording)
FLORTNUTNR (probably internally recording)
PHSEN (probably internally recording)
PCO2W (probably internally recording)
OPTAA
SPKIR
VELPT (probably internally recording)

DCL17
MOPAK
CTDBP + FLORT
VELPT (probably internally recording)
ACOMM
DCL35
ADCPT (probably internally recording)
PCO2W (probably internally recording)
PHSEN (probably internally recording)
PRESF (probably internally recording)
VEL3D (probably internally recording)
DCL37
CTDBP + DOSTA (probably internally recording)
OPTAA
ZPLSC (probably internally recording)

Id: 871 By: michaesm
Flag: not_available Exclude: No

The OPTAA data indicate that the sensor may be fouled. Counts for Channel A Raw Signal have sprodically been dropping to zero.

Id: 1867 By: politank
Flag: suspect Exclude: No

During a large storm event on 2020-01-11, the surface buoy and NSIF broke free and went adrift. As a result, telemetry from the data loggers and instrumentation on the seafloor platform has ceased. We expect the system to continue autonomous operations and hope to download data from the data loggers and instruments after the seafloor platform is recoverd in the spring of 2020.

Id: 1896 By: wingardc
Flag: not_available Exclude: No