Abstract:
This data was collected during the CARTHE Surfzone Coastal Oil Pathways Experiment (SCOPE) experiment at Destin Inlet in December 2013. The data was underway ADCP data collected from the bow of the University of Miami's RV Calliope. The ADCP, an RDI 1200 kHz Workhorse, was mounted ~0.3 m below the MWL in a down-looking mode. Sampling interval and bin size are deployment-dependent. GPS data from the boat-mounted GPS is also included. The ADCP data was collected with Bottom Tracking Mode On, but without direct link to GPS. The ADCP is equipped with a pitch, roll, and magnetic compass (magnetic declination was accounted for in the configuration). The ADCP data was acquired in real-time with WinRiver software, the machine that housed the acquisition was synced to an NTP server. The machine clock was used to program the software acquisition. The data set contains 4 zip folders: 1) SPECGPS.zip contains the available gps information [time, longitude, latitude], the SPECgps.txt file within this folder contains a continuous record of all of the available gps information for the Calliope from SCOPE, raw data as well as matlab routines necessary to exporting the gps raw data to matlab-readable format is also provided; 2-4) adcp_configX.zip contain matlab-readable data from the Calliope's shipboard ADCP, each individual *.dat file is named by the transect time stamp and information provided within the ASCII file, for example a *_velocity.dat file contains Earth referenced velocity information (see the *_readme.dat files).
Suggested Citation:
Brian Haus, David Ortiz-Suslow, Nathan Laxague. 2016. Surfzone Coastal Oil Pathways Experiment (SCOPE) experiment, ADCP data collected from RV Calliope, Destin Inlet, Florida, December 2013. Distributed by: GRIIDC, Harte Research Institute, Texas A&M University–Corpus Christi. doi:10.7266/N7XW4GSC
Data Parameters and Units:
* All times are in UTC * All velocities are in m/s * All directions/headings are in degrees CW from True North * All vectors are oriented downstream (direction going towards) The files are named using the time stamp YYYYMMDD_HHMMSS_*.dat which refers to the time of the first profile in the run. For each run, there are tables called ANCILLARY, ANCHEADER, SYSTEM, ECHOAMP, VELOCITY, and a README. ANCHEADER provides description and units for each column of the ANCILLARY table. Here is that information in "rows": YY [years since 2000] MMM [months] DD [day] HH [hours] MM [minutes] SS [seconds] DS [decimal hundredths of seconds] ADCP Pitch [degrees] ADCP Roll [degrees] ADCP Heading [degrees from True North] Temperature [deg. C, measured at transducer head] Depth [m below surface, measured at transducer head] Orientation [logical, 0 means downward facing] BTE [m/s, Bottom Track Eastward Velocity] BTN [m/s, Bottom Track Northward Velocity] BTV [m/s, Bottom Track Northward Velocity] BTErr [m/s, Bottom Track Error Velocity] BTS [m/s, Bottom Track Speed] BTC [degrees from True North, Bottom Track Course ] BT Depth 1 [m, Bottom Track Depth from Beam 1] BT Depth 2 [m, Bottom Track Depth from Beam 2] BT Depth 3 [m, Bottom Track Depth from Beam 3] BT Depth 4 [m, Bottom Track Depth from Beam 4] SYSTEM contains basic ADCP system info in row format: ADCP-Type Profile Interval [s] Distance to Middle Bin [m] Bin Width [m] Number of Bins [integer] ECHOAMP contains an N x 4*(Number of Bins) table of echo amplitude, the signal strength return to the ADCP from the initially sent acoustic wave. N is the number of individual profiles. "4" is the number of individual transducers on the ADCP. "Number of Bins" is the number of individual bins in the ADCP profile. The unit for all values in this table is "counts", high counts means strong signal return, low counts means weak signal return. The columns of ECHOAMP are organized as follows (if number of bins = 95): [1,2,3,........,93,94,95,1,2,3,4,.....,95,....] The first set of 1-95 is beam 1, the second sequence is beam 2, and so on to beam 4. VELOCITY contains a table of N x 6*(Number of Bins) table of velocity data. "6" refers to the 6 velocity components included in the table, these are in order: Eastward Velocity, Northward Velocity, Vertical Velocity, Error Velocity, Magnitude, and Direction. The columns of VELOCITY are organized as follows (if number of bins = 95): [1,2,3,........,93,94,95,1,2,3,4,.....,95,....] The first set of 1-95 is the Eastward Velocity data, the second sequence is the Northward Velocity Data, and so on to the Direction. The Magnitude is the horizontal current speed (i.e. using Eastward and Northward) and Direction is the direction of that magnitude in degrees the current is going. The zip folder with the ADCP data contains external GPS data from 3 independent units sampled at 1 Hz. The 3 units data has been combined into a single table and duplicate data points have been removed. The data file is: SPECgps.txt It contains 3 columns. The description and units are provided here in "rows": Time [UTC, serial matlab time format referenced to Matlab's internal time = 0] Longitude [decimal degrees, this is a signed value, negative means west] Latitude [decimal degrees, this is a signed value, positive means north]
Methods:
The ADCP data is in a raw format (no external data removal or flagging algorithms have been applied), but the velocities have been screened with RDI internal/automatic methods and have been referenced to the bottom track velocity. For information about RDI processing see the Workhorse technical manual. * 3 separate configuration settings were used during the experiment. This will effect the profile interval and the number of bins. The only way to tell the difference is by checking *_SYSTEM.dat files. All other outputs (e.g. units, parameters outputted, etc.) are unaffected by this. ANCILLARY is a table which provides various data useful for ADCP processing. To get ADCP data on a spatial grid, the external GPS data (included) must be interpolated onto the ADCP time record. The GPS samples at 1 Hz. The ADCP always sampled at less than 1 Hz. There may be select instances when there is ADCP data available without the corresponding GPS information, no supplemental data is available for these periods, however these are most likely cases of instrument testing or when there was not coordinated sampling/observations being made as part of the aims of the SCOPE project. All files are named by the date and time of their first profile. Location, duration, and sampling scheme is completely deployment-dependent.
View Metadata