3-Wavelength Fluorometer

Reference Designator
Review Status
Review Complete
FLORT (3-Wavelength Fluorometer)
Make / Model
WET Labs / ECO Triplet-w

Dataset Reviews Last processed: 6/7/19, 4:59 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
2 recovered_host flort_sample 185 184 0 0 0 0 4,389 2 / Complete
4 recovered_host flort_sample 216 1 0 214 0 0 2 3,599 2 / 1 1 Complete
6 recovered_host flort_sample 200 93 0 75 13 36 1,783 2 / Complete
7 recovered_host flort_sample 177 164 0 0 1 14 3,343 2 / Complete
8 recovered_host flort_sample 172 92 0 80 0 0 2,167 2 / Complete
9 recovered_host flort_sample 181 181 0 0 0 0 2,167 2 / Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison

Data Coverage

Deployment: 246789
flort_sample 99%0%46%93%53%100%

Lat/Lon Differences (km)

Deployment: 246789
2 0.00
4 0.200.00
7 0.240.430.390.00
9 0.170.370.340.100.330.00

Example Composite Data Plot

System Annotations

Metadata Start Date End Date Comment
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

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

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

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

VELPT (probably internally recording)
ADCPT (probably internally recording)
PCO2W (probably internally recording)
PHSEN (probably internally recording)
PRESF (probably internally recording)
VEL3D (probably internally recording)
CTDBP + DOSTA (probably internally recording)
ZPLSC (probably internally recording)

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

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

Review Notes

Metadata Start Date End Date Comment

The variable pressure_depth (dbar) is an array of all fill values for every deployment. This should contain valid pressure data.

By Lori Garzio, on 6/26/19

Deployment: 2
12/28/14, 12:00 AM 4/12/15, 12:30 AM

Approximately 40% of the data for all variables are negative values for this deployment. Excluding from final data ranges

By Lori Garzio, on 6/26/19

Deployment: 4
10/8/15, 12:00 AM 10/9/15, 12:00 AM

There are 2 data points available for this deployment of this instrument. The dataset should be annotated if there was an issue.

By Lori Garzio, on 6/26/19

Deployment: 7
4/19/17, 4:18 AM 10/12/17, 9:50 PM

Values are negative for this deployment. This should be investigated and fixed or annotated.

By Lori Garzio, on 6/26/19

Deployment: 8
1/11/18, 12:00 AM 4/1/18, 12:00 AM

Missing data at the end of deployment 8 should be annotated.

By Lori Garzio, on 6/26/19

New Note