3-D Single Point Velocity Meter

Reference Designator
CE01ISSM-MFD35-01-VEL3DD000
Review Status
Review Complete
Note
Seawater velocities are too high for all deployments.
Depth
25m
Class
VEL3D (3-D Single Point Velocity Meter)
Make / Model
Nortek / VECTOR

Dataset Reviews Last processed:

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 / Complete
2 telemetered 185 3 0 180 0 0 4,320 25 / 32 1 1 Complete
3 recovered_inst 127 126 0 0 0 0 4,330,080 25 / 31 Complete
4 recovered_inst 216 209 7 0 0 0 7,187,040 25 / 21 1 1 Complete
5 recovered_inst 138 138 0 0 0 0 4,740,480 24 / 30 1 1 Complete
6 recovered_inst 200 200 0 0 0 0 6,883,200 25 / 25 Complete
7 recovered_host 177 18 0 158 1 2 555,406 25 / 29 2 Complete
8 recovered_inst / Complete
9 recovered_inst / Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison
  2. fail: data found in another stream (gaps: [2] days: [4])

Data Coverage

Deployment: 123456789
2%
99%97%100%100%10%

Lat/Lon Differences (km)

Deployment: 123456789
2 0.00
3 0.080.00
4 0.200.220.00
5 0.080.000.220.00
6 0.180.170.090.170.00
7 0.240.220.430.220.390.00

System Annotations

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

CE01ISSM-MFD35
10/28/16, 8:00 PM 5/14/17, 8:00 PM

The file system on the SD card used by embedded Linux card comprising DCL35 became corrupted on Saturday, October 29, 2016. Affected instruments are: [ADCPT, PCO2W, PHSEN, PRESF, VEL3D]. All instruments are set to log internally. Will not receive telemetered data, but do not anticipate complete loss of data.

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

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

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:
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

CE01ISSM-MFD35
5/11/17, 8:00 PM 10/30/17, 8:00 PM

Lost communication with DCL35, on the MFN of CE01ISSM sometime after 2017/05/12 04:32:31.744. Reason unknown. Attempted to log into the system and establish both an ssh connection and a minicom session with no success. Minicom session showed zero activity, suggesting the system is completely offline. With the exception of the VEL3D, all instruments hosted by DCL35 are autonomous. No further data should be expected from: [ADCPT (recording internally), PRESF (recording internally), PC02W (recording internally), PHSEN (recording internally), VEL3D (status unknown)]

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

CE01ISSM-MFD35-01-VEL3DD000
Method: telemetered
4/2/18, 8:00 PM

No data from this instrument is being logged or telemetered to shore. It's possible that the serial port on either the VEL3D or DCL has failed and/or is incorrectly setup or the driver software on the DCL has somehow failed.

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

CE01ISSM-MFD35-01-VEL3DD000
4/19/19, 11:01 PM 10/22/19, 7:57 PM

Due to adverse datalogger/instrument sampling schedule interactions, the instrument battery packs were removed to render the instrument a "dumb" device (samples when powered on). An unintended consequence of this is the instrument sometimes loses the internal clock settings and sets to 1970-01-01 as the default date. The current Data Portal system excludes this data. Until such time as a work around is available, this data will not be available for this deployment.

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

CE01ISSM-MFD35
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. 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: 1895 By: wingardc
Flag: not_available Exclude: No

Review Notes

Metadata Start Date End Date Comment
CE01ISSM-MFD35-01-VEL3DD000

Seawater velocity ranges are too high for all deployments - eastward and northward velocities reach as high as 10 m s-1 and upward velocities reach 2.5 m s-1. Global ranges are -3 to 3 (eastward and northward) and -1 to 1 (upward). For comparison, seawater velocities measured by the VELPT on RID16 are an order of magnitude lower. This should be investigated.

By Lori Garzio, on 8/23/19

CE01ISSM-MFD35-01-VEL3DD000

And end date should be added to annotation ID 1455

By Lori Garzio, on 8/22/19

CE01ISSM-MFD35-01-VEL3DD000

There are no data available for download for deployments 1, 8 and 9. According to the ingest csvs, recovered_inst raw data files are available. These files should be ingested or the datasets should be annotated to explain why no data are available.

By Lori Garzio, on 8/22/19

CE01ISSM-MFD35-01-VEL3DD000
Deployment: 2

There are no recovered_inst data available for download for this deployment. According to the ingest csv, recovered_inst raw data files are available. These files should be ingested or the dataset should be annotated to explain why recovered_inst data aren't available.

By Lori Garzio, on 8/22/19

New Note