LAST CHANGED : 2023/12/22 CRUISE NAME(S) : FKt230602 CRUISE DATES : 2023/06/02 to 2023/06/21 SHIP NAME : Falkor (too) PORTS : Puntarenas, Costa Rica to Puntarenas, Costa Rica CHIEF SCIENTIST : Beth Orcutt DATABASE NAME : a_ftoo DATA FILES : ftoo2023_152_09253.raw to ftoo2023_171_43200.raw STATUS : to do done ------ ----------- averaged [ X ] at sea loaded [ X ] at sea NOTE: heading correction instrument exists NOTE: time-dependent heading corrections applied IN the ensembles (see cal/rotate/ens_hcorr.ang) check heading correction [ X ] calibration [ X ] edited [ X ] re-check heading correction [ X ] check editing [ X ] figures [ X ] INSTRUMENT : ec150 ACQUISITION : PROGRAM : uhdas PROCESSING: : python LOGGING : PARAMETERS : BT : bottom track mode (on or off) SI : sampling interval or averaging period for ensemble (sec) NB : number of bins BL : bin length (m) TD : transducer depth (m) BK : blanking length (m) HO : heading offset applied by DAS (deg) HB : heading bias (deg) CRPH : compensation for roll-pitch-heading, 1:on, 0:off) yy/mm/dd hh:mm:ss BT SI NB BL TD BK HO HB CRPH 2023/06/19 19:26:01 off 300 43 8 7 9 45.00 0.00 0001 HEADING : PRIMARY : heading from gyro1 CORRECTION : heading correction from seapath NOTE: time-dependent heading corrections applied IN the ensembles (see cal/rotate/ens_hcorr.ang) POSITIONS : gps positions from posmv_gps CALIBRATION : (check original processing parameters) (1) transducer alignment original transducer alignment: 45 additional rotation -0.1 final transducer angle is: (45) - (-0.1) = 45.1 (2) scale factor original scale factor 1 additional scale factor (1.003) final scale factor 1.003 (3) ADCP (dx=starboard, dy=fwd) meters from GPS original: xducer_dx=0 xducer_dy=0 correction 0 0 final offset 0 0 final = original + corrections COMMENTS : no gaps in heading correction some periods with bad seapath positions top bin usually bad and edited out calibrations averaged over 9 cruises, not just this one PROCESSOR : Steven Howell --- final processing parameters from dbinfo.txt ---------- # # written 2023/06/19 19:26:09 # this file contains CODAS quick_adcp.py info #name, value pairs #-------------------- ## (determined from "sonar"): model = ec ## (determined from "sonar"): frequency = 150 ## (determined from "sonar"): instname = ec150 ## (determined from "sonar"): pingtype = fm beamangle 30 cruisename FKt230602 datatype uhdas dbname a_ftoo ens_len 300 fixfile a_ftoo.gps frequency 150 hcorr_inst seapath instname ec150 model ec pingtype fm proc_engine python ref_method refsm refuv_smoothwin 3 refuv_source nav sonar ec150fm txy_file a_ftoo.gps xducer_dx 0 xducer_dy 0 yearbase 2023 ================================================== POST PROCESSING STEPS: ================================================== -------------------------- ### 1. Check visual oddities -------------------------- ### Run this: (to look for gaps in the cruise track) plot_nav.py nav/a*.gps # There is not much data here. Just 1.7 or so days of the cruise, from dday 169.8 to 171.5. # There is a small gap in the nav data around dday 170.9 ### Run this: (to look for gaps in the heading correction, examine the character of ### the watertrack and bottom track calibration, etc figview.py # Looks okay. No missing heading corrections; the rest of the plots are well behaved. ### Run this: (looking for missing heading correction values or missing positions) dataviewer.py # Some obvious spurious data below sensor effective range and the top bin or two # are biased, but otherwise straightforward. ### Run this: (to check watertrack calibration after patching hcorr) catwt.py ### Run this: (to check dxdy statistics calibration after patching hcorr) catxy.py --------------------- ### 2. ADCP calibration --------------------- # Note about calibrations: There were insufficient watertrack points to derive decent # calibrations. Instead, I concatenated all of the EC150 a_ftoo_7.cal files for 9 cruises, # FKt230303 to FKt230918, then ran Wtplot_script.py to calculate heading and amplitude # corrections for all of the cruises, all at once. This assumes that those values were # constant for the entire period, which seems like a pretty safe bet. However, this # is impractical to do after editing, so there could be some inaccuracy that could be # corrected by redoing all of the concatenation and calculation after editing all of # the cruises. That is _not_ being done here! # The result of the watertrack calibrations for the set of cruises was: ADCP watertrack calibration ## Time range 90.07 to 262.53 Calculation done at Tue Nov 7 15:14:28 2023 delta-u min = -100.00, max = 100.00 delta-v min = -100.00, max = 100.00 clip_amp = 0.04, clip_ph = 3.0 clip_dt = 60, clip_var = 0.050 Number of edited points: 92 out of 106 amp = 1.0024 + -0.0000 (t - 191.5) phase = -0.10 + -0.0008 (t - 191.5) **watertrack** ----------- Number of edited points: 92 out of 106 median mean std amplitude 1.0030 1.0024 0.0075 phase -0.1180 -0.0982 0.4592 ----------- # So, for all of the cruises, we'll use amplitude correction factor 1.003 and # phase -0.1 --- ### Run this: quick_adcp.py --steps2rerun rotate:navsteps:calib --rotate_amplitude 1.003 --rotate_angle -0.1 --auto ### Run this: (look at the watertrack calibration again) catwt.py **watertrack** ----------- Number of edited points: 6 out of 6 median mean std amplitude 1.0045 1.0058 0.0066 phase 0.0960 -0.0105 0.4933 ----------- # But remember that this calculation is pretty meaningless ### Run this: (look at the offset again) catxy.py **transducer-gps offset** ----------- guessing ADCP (dx=starboard, dy=fwd) meters from GPS positions from a_ftoo.gps calculation done at 2023/12/19 00:15:01 xducer_dx = -0.613063 xducer_dy = 1.527872 signal = 124.652219 ----------- # Again, pretty much meaningless, but even if it weren't it's only a # little off, so corrections wouldn't be done anyway. ------------------- ### 3. Editing points ------------------- ### Run this: (to go through the dataset and edit out bad values) dataviewer.py -e # Deleted much of the top bin data and some deep isolated datapoints. The calibrations should still be good after editing. -------------------------------------------------- ### 4. Re-check heading correction and other figures -------------------------------------------------- ### Run this: (Is there anything strange with any of the figures?) figview.py -------------------------------------------------------------- ### 5. Check edited, calibrated dataset against original dataset -------------------------------------------------------------- ### Run this: (Has this corrected the problems in the original?) dataviewer.py -c . ../ec150fm.orig ### Run this to compare this sonar with another sonar (after both are finished) cannot compare with anything due to a dataviewer.py bug ### Final cleanup: Because this is a new instrument, we did not realize ### the original depths were too deep by one bin. A specialized program ### was used to correct this ("depth_change_ec"). A log of this change ### is appended to the end of this file. ------------------------- ### 6. Make plots and files ------------------------- ### Run this: quick_web.py --interactive ### Run this to extract matlab files quick_adcp.py --steps2rerun matfiles --auto ### Run this to extract a netCDF file adcp_nc.py adcpdb contour/ec150fm FKt230602 ec150fm --ship_name "Falkor (too)" ### Run this to look at the headers ncdump -h contour/ec150fm.nc | egrep '(cruise_id|sonar|yearbase)' ######################################### FKt230602_ec150fm_depth_change.log ../FKt230602/ec150fm/adcpdb/a_ftoo 169.80973 block = 0 ,bin = 7.9, blank = 8.7 170.88894 block = 1 ,bin = 7.9, blank = 8.7 ../FKt230602/ec150fm/adcpdb/a_ftoo 169.80973 block = 0 ,bin = 7.9, blank = 0.7 170.88894 block = 1 ,bin = 7.9, blank = 0.7