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_169_64800.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/02 02:39:11 off 300 42 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/02 02:39:21 # 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 = cw 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 cw proc_engine python ref_method refsm refuv_smoothwin 3 refuv_source nav sonar ec150cw 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 # Big gap between dday 158 and 166. Smaller gap dday 167.15 to 167.35. ### Run this: (to look for gaps in the heading correction, examine the character of <...> the watertrack and bottom track calibration, etc figview.py # No missing heading corrections. ### Run this: (looking for missing heading correction values or missing positions) dataviewer.py ### Run this: (to check watertrack calibration after patching hcorr) catwt.py ### Run this: (to check watertrack calibration after patching hcorr) catbt.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: (look at the remaining offsets required) catxy.py **transducer-gps offset** ----------- guessing ADCP (dx=starboard, dy=fwd) meters from GPS positions from a_ftoo.gps calculation done at 2023/06/19 19:15:03 xducer_dx = -0.438361 xducer_dy = 3.273214 signal = 813.522906 ----------- # But note the weak signal. Unfortunately, it is not easy to concatenate the xy # calculation in the same way as the watertrack, so cruises are not gathered together. # Estimates of d[xy] vary considerably between cruises, again with very weak signal. # Best estimate may be xducer_dx=0, xducer_dy=4, but these values are small enough # and uncertain enough that no calibration will be applied. # Note that we cannot practically reprocess the data; bugs in the acquisition scheme # would require considerable code rewriting to fix. Therefore, we cannot reprocess to # apply a revised xducer_d[xy] for improved uvship calculations. --- ### 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 ### Run this: (look at the offset again) catxy.py # But remember that the correction is not based on just this cruise **watertrack** ----------- Number of edited points: 23 out of 24 median mean std amplitude 0.9990 1.0014 0.0075 phase 0.0210 0.0188 0.3912 ----------- ------------------- ### 3. Editing points ------------------- ### Run this: (to go through the dataset and edit out bad values) dataviewer.py -e # Odd set of 4 profiles around 152.37. Looks like the sort of thing uvship # would fix, but not turning, and percent good is not showing anything odd. # Eliminated. # Also deleted some deep data from a scattering layer that showed suspiciously # strong currents around 152.8. # Bad profiles around 153.12. Apparently caused by bad seapath positions. # Could be fixed, but a lot of effort to save a little data. # Bad profiles around 155.43. # Top bin usually looks bad in u and/or v. Much of it removed. ### Run this: (to recompute the calibration residuals) quick_adcp.py --steps2rerun navsteps:calib --auto 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 . ../ec150cw.orig ### Run this to compare this sonar with another sonar (after both are finished) dataviewer.py -c ../ANOTHER_SONAR . # Since the ec150cw and ec150fm were run at different times, no direct comparison # is possible. There were also RDI OS38 and WH300 instruments operating, and # it makes sense to compare the ec150 with the WH300 and the OS38bb dataviewer.py -c ../../wh300 . dataviewer.py -c . ../../os38bb . # The whole dataset has lots of vertical structure, with thin layers # of water moving different directions. That means the different # vertical resolution of the two sonars yields lots of intense # horizontal stripes that do not really indicate a disagreement. Use the comparison to determine if anything else needs to be done. plot_reflayer.py --plotfp --zrange=30:80 ../../wh300 ./ zrange is 30:80 parts is ['30', '80'] ======> NOTE ABOUT CALIBRATIONS <======= If there was a reason to apply a calibration to ec150cw for it to better match wh300, these are APPROXIMATE values to use. Use these as if they came from cal/watertrk or cal/botmtrk. scale factor:f 0.998 to ec150cw rotation angle: -0.01deg to ec150cw ================ # Actually, that's not bad! plot_reflayer.py --plotfp --zrange=30:200 ../../os38bb ./ zrange is 30:200 parts is ['30', '200'] ======> NOTE ABOUT CALIBRATIONS <======= If there was a reason to apply a calibration to ec150cw for it to better match os38bb, these are APPROXIMATE values to use. Use these as if they came from cal/watertrk or cal/botmtrk. scale factor:f 0.995 to ec150cw rotation angle: -0.05deg to ec150cw ================ # Not quite as nice, but acceptable. ### 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/ec150cw FKt230602 ec150cw --ship_name "Falkor (too)" ### Run this to look at the headers ncdump -h contour/ec150cw.nc | egrep '(cruise_id|sonar|yearbase)' ######################################### FKt230602_ec150cw_depth_change.log ../FKt230602/ec150cw/adcpdb/a_ftoo 152.11054 block = 0 ,bin = 8.1, blank = 8.6 153.15222 block = 1 ,bin = 8.1, blank = 8.6 154.19388 block = 2 ,bin = 8.1, blank = 8.6 155.23554 block = 3 ,bin = 8.1, blank = 8.6 156.27723 block = 4 ,bin = 8.1, blank = 8.6 157.31887 block = 5 ,bin = 8.1, blank = 8.6 158.36057 block = 6 ,bin = 8.1, blank = 8.6 166.07909 block = 7 ,bin = 8.1, blank = 8.6 167.12076 block = 8 ,bin = 8.1, blank = 8.6 167.38178 block = 9 ,bin = 8.1, blank = 8.6 168.42344 block = 10 ,bin = 8.1, blank = 8.6 169.46515 block = 11 ,bin = 8.1, blank = 8.6 ../FKt230602/ec150cw/adcpdb/a_ftoo 152.11054 block = 0 ,bin = 8.1, blank = 0.6 153.15222 block = 1 ,bin = 8.1, blank = 0.6 154.19388 block = 2 ,bin = 8.1, blank = 0.6 155.23554 block = 3 ,bin = 8.1, blank = 0.6 156.27723 block = 4 ,bin = 8.1, blank = 0.6 157.31887 block = 5 ,bin = 8.1, blank = 0.6 158.36057 block = 6 ,bin = 8.1, blank = 0.6 166.07909 block = 7 ,bin = 8.1, blank = 0.6 167.12076 block = 8 ,bin = 8.1, blank = 0.6 167.38178 block = 9 ,bin = 8.1, blank = 0.6 168.42344 block = 10 ,bin = 8.1, blank = 0.6 169.46515 block = 11 ,bin = 8.1, blank = 0.6