CTD

Reference Designator
CE02SHSP-SP001-08-CTDPFJ000
Review Status
Review Complete
Note
Depth
0 to 80m
Class
CTDPF (CTD Profiler)
Make / Model
Sea-Bird / FastCAT 49 CTD

Dataset Reviews Last processed: 6/28/19, 2:16 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_cspp 16 15 0 0 3 3 237,356 80 / 73 1 1 Complete
3 recovered_cspp 41 41 0 0 0 0 905,913 80 / 73 1 1 Complete
4 recovered_cspp 88 44 0 0 13 47 652,748 80 / 73 1 1 Complete
5 recovered_cspp 32 18 0 9 3 6 335,389 80 / 73 1 1 Complete
6 recovered_cspp 5 4 0 1 0 0 112,219 80 / 78 1 1 Complete
7 recovered_cspp 105 55 0 40 3 11 537,577 80 / 78 1 1 Complete
8 recovered_cspp 27 22 0 3 1 2 170,670 80 / 78 1 1 Complete
9 recovered_cspp 20 20 0 0 0 0 175,748 80 / 78 1 1 Complete
10 recovered_cspp 71 7 0 64 0 0 86,504 80 / 76 1 1 Complete
Data Ranges Review Images

Test Notes

  1. no other streams for comparison

Data Coverage

Deployment: 1345678910
94%100%50%56%80%52%81%100%10%

Lat/Lon Differences (km)

Deployment: 1345678910
1 0.00
3 0.880.00
4 0.080.960.00
5 0.230.950.190.00
6 0.360.560.420.400.00
7 0.470.680.490.370.250.00
8 0.260.800.330.480.410.620.00
9 0.660.790.670.510.450.210.830.00
10 0.00

System Annotations

Metadata Start Date End Date Comment
CE02SHSP
3/8/17, 7:00 PM 4/17/17, 8:00 PM

The main batteries on CE02SHSP-00005 drained unexpectedly. CSPPs are deployed at 33.4 V. Voltage drops roughly linearly with each profile. Batteries were at 31 V at the beginning of this week. Yesterday (2017-03-09), it reported via acoustic modem that it was in a LOW POWER state, which it does automatically at 28 V to protect the main batteries. In the past, similar drains have been due to faulty connections between the main batteries and the profilers at the battery adapter plates. This has been the CSPP's main failure behavior.

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

CE02SHSP
4/24/17, 8:00 PM 10/4/17, 8:00 PM

CE02SHSP-00006 reported that it had surfaced unexpectedly April 25 at 5:10 pm local time. Within a few hours it was determined that it was still tethered to its anchor. It's beacon wasn't reporting either. The profiler and its anchor were recovered the following day. Data were sent to the profiler vendor. By April 28 we confirmed there was a firmware bug that had never been seen before. While moving between two positions, the control canister thought the profiler was 20 cm below its destination, but the profiler's winch thought the profiler was 20 cm above its destination, so the profiler was winched up to the surface, instead of retreating 20 cm to its parking depth. The bug will be corrected in the next firmware release. It also turns out that the beacon was programmed improperly, so it had run out of batteries. We switched to a new beacon model this year and confirmed with the vendor which settings to use.

Id: 883 By: michaesm

CE02SHSP
5/29/18, 8:00 PM 8/1/18, 4:30 PM

Profiler was profiling twice per day, but it has not surfaced as planned since May 30 ~1am PDT. It is deployed too far from CE02SHSM for us to have good acoustic communications (1150m vs. the planned 150-400m), so we cannot debug it remotely. It will need to be recovered, but it is not at the surface or adrift, so it does not need immediate recovery.

Id: 1458 By: michaesm

Review Notes

Metadata Start Date End Date Comment
CE02SHSP-SP001

During deployments 3 - 5, there are several pressure (dbar) data points that are outliers (much deeper than the max deployment depth of 80m).

By Lori Garzio, on 7/1/19

CE02SHSP-SP001-08-CTDPFJ000

Some conductivity, density, and salinity data near the surface are unreasonable for all deployments.

By Lori Garzio, on 7/1/19

CE02SHSP-SP001-08-CTDPFJ000
Deployment: 3
10/1/16, 12:00 AM 10/2/16, 4:52 PM

Suspect density and salinity > 50 dbar.

By Lori Garzio, on 7/1/19

CE02SHSP-SP001-08-CTDPFJ000
Deployment: 4

The 13 gaps totaling 47 days should be annotated.

By Lori Garzio, on 7/1/19

CE02SHSP-SP001-08-CTDPFJ000
Deployment: 4
10/11/16, 12:00 AM 10/15/16, 12:00 AM

Suspect density data towards the beginning of the deployment (density is lower at depth).

By Lori Garzio, on 7/1/19

New Note