Data Trawler - Event Details

Please login if you have access to particular applications.

Event details

Voyage: IN2020_V10       [details]
When: 2020-11-17 23:45:08 UTC

- entered into Elog/Everlog as 2020-11-17 23:45:08
Log: PLAOS_in2020_v10
Equipment: Start
Position: Latitude: -43.89367 Longitude: 147.9185

- entered into Elog as 43 53.62 S, 147 55.11 E
Station Number:3
Vertical Starboard Strobe Working?:No
Vertical Starboard Camera Working?:Yes
Vertical Port Strobe Working?:Yes
Vertical Port Camera Working?:No
Oblique Strobe Working?:Yes
Oblique Camera Working?:Yes
Vertical Video Light Working?:Yes
Vertical Video Working?:Yes
Acoustics Frequencies (kHz):38, 70, 120, 200
Acoustics Mode:CW
Acoustics Calibration:38.1 mm WC @ 4.25 m
Optics Calibration:10 cm long 3 tags at 1, 2, and 3 m
Logging range (m):100
Deployment Depth (m):1050
Planning Comments:CW deep-water deployment to check all data stream
Operation Comments:This is the first proper deployment to check data streams including acoustics and optics. Unfortunately, the acoustics is not working as expected. Inconsistent ping rate across the channels. Tube 2 configured with 70 and 200 kHz is not pinging fast enough and slows down the ping rate considerably when all channels are recording data. Lost sample warning for 70 kHz and it is not working properly making the data unusable. Theoretically, we should achieve a ping rate of 7.5 pps for 100 m recording range. Because Tube 2 was not pinging fast we could only achieve a ping rate of 2.5 pps with inconsistency. For some reason this ping rate is not holding consistently and causing target tracking difficulty. Did some further ping rate test on deck. The issue seems to be with Tube 2 and when it is configured with Tube 1 the ping rate becomes slow and inconsistent for Tube 1 as well. Tube 1 in standalone mode seems to provide a ping rate of 6.1 pps (the best we can achieve given the processing overheads).
NCMI Information and Data Centre  »  Applications  »  Data Trawler