LAST CHANGED : 2023/12/22 CRUISE NAME(S) : FKt230508 CRUISE DATES : 2023/05/08 to 2023/05/13 SHIP NAME : Falkor (too) PORTS : San Juan, Puerto Rico to Colon, Panama CHIEF SCIENTIST : Paul Duncan DATABASE NAME : a_ftoo DATA FILES : ftoo2023_127_79602.raw to ftoo2023_132_43200.raw STATUS : to do done ------ ----------- averaged [ X ] at sea loaded [ X ] 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 : os38 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/05/08 22:11:42 off 300 100 12 7 16 0.91 0.00 0001 2023/05/11 00:11:48 off 300 100 12 7 16 0.91 0.00 0001 2023/05/13 02:11:47 off 300 100 12 7 16 0.91 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: 0.91 additional rotation 0.7 final transducer angle is: 0.21 = 0.91 - 0.7 (2) scale factor original scale factor 1 additional scale factor (none) (3) ADCP (dx=starboard, dy=fwd) meters from GPS xducer_dx xducer_dy original: 0 0 correction 0 -10 final offset 0 -10 COMMENTS : I performed a dxdy calibration. A good estimate of heading correction and transducer offset is available from adjacent cruises. Data below the bottom was removed, as well as small bits of data at the the bottom of the sonars range was removed. Due to a strong scattering layer, some data was flagged as "below that bottom". Some of this data was able to be reclaimed. Editing and updating the dxdy correction improved the data during heading changes. PROCESSOR : Jamie Ash --- final processing parameters from dbinfo.txt ---------- #-------------------- ## (determined from "sonar"): model = os ## (determined from "sonar"): frequency = 38 ## (determined from "sonar"): instname = os38 ## (determined from "sonar"): pingtype = bb beamangle 30 cruisename FKt230508 datatype uhdas dbname a_ftoo ens_len 300 fixfile a_ftoo.gps frequency 38 hcorr_inst seapath instname os38 model os pingtype bb proc_engine python ref_method refsm refuv_smoothwin 3 refuv_source nav sonar os38bb txy_file a_ftoo.agt xducer_dx 0 xducer_dy -10 yearbase 2023 ================================================== POST PROCESSING STEPS: ================================================== ------------------------------------------------------------------------ ### 1. Check visual oddities ------------------------------------------------------------------------ # I ran this to look for gaps in the cruise track. plot_nav.py nav/a*.gps # The cruise track looks clean. # I ran this to look for gaps in the heading correction. figview.py # place holders do exists in the heading correction. # I'll need to run patch h_corr. ### Run this: (to interpolate for missing heading correction fixes) cd cal/rotate patch_hcorr.py cd ../.. # I ran this looking for missing heading correction values. dataviewer.py # There's a section where with high ship speeds where percent good is # very low, resulting in bad data quality. # I ran this to check watertrack calibration. # Same as other sonars on this ship, the ship speed goes on the fritz # and there is a substantial gap in the reference layer velocity. ------------------------------------------------------------------------ ### 2. ADCP calibration ------------------------------------------------------------------------ # Insufficient calibration information; # use adjacent cruises for calibration values. # I ran this to adjust the calibration. quick_adcp.py --steps2rerun rotate:apply_edit:navsteps:calib --xducer_dy -10 --auto quick_adcp.py --steps2rerun rotate:apply_edit:navsteps:calib --rotate_angle 0.7 --auto ------------------------------------------------------------------------ ### 3. Editing points ------------------------------------------------------------------------ # I ran this go through the dataset and edit out bad values. dataviewer.py -e # It appears that at high ship speeds, the os38 data has very poor # percent good. As much data as possible was left untouched. A # substantial amount of pruning was done. ------------------------------------------------------------------------ ### 4. Check edited, calibrated dataset against original dataset ------------------------------------------------------------------------ # Has this corrected the problems in the original? dataviewer.py -c . ../os38bb.orig # To compare this sonar with another sonar. dataviewer.py -c ../os38nb.cal . # Overall, the data is a bit noisy, and as much was kept in as possible. ------------------------------------------------------------------------ ### 5. Make plots and files ------------------------------------------------------------------------ # To carry over the section info from another sonar. mkdir webpy cp ../wh300/webpy/sectinfo.txt webpy/ quick_web.py --redo # I ran this to extract matlab files. quick_adcp.py --steps2rerun matfiles --auto # I ran this to extract a netCDF file. adcp_nc.py adcpdb contour/os38bb FKt230508 os38bb --ship_name "Falkor (too)" # I ran this to look at the headers. ncdump -h contour/os38bb.nc | egrep '(cruise_id|sonar|yearbase)' # complete