skip to main content

Title: Admiralty Inlet Advanced Turbulence Measurements: June 2014

This data is from measurements at Admiralty Head, in Admiralty Inlet (Puget Sound) in June of 2014. The measurements were made using Inertial Motion Unit (IMU) equipped ADVs mounted on Tidal Turbulence Mooring's (TTMs). The TTM positions the ADV head above the seafloor to make mid-depth turbulence measurements. The inertial measurements from the IMU allows for removal of mooring motion in post processing. The mooring motion has been removed from the stream-wise and vertical velocity signals (u, w). The lateral (v) velocity has some 'persistent motion contamination' due to mooring sway. Each ttm was deployed with two ADVs. The 'top' ADV head was positioned 0.5m above the 'bottom' ADV head. The TTMs were placed in 58m of water. The position of the TTMs were: ttm01 : (48.1525, -122.6867) ttm01b : (48.15256666, -122.68678333) ttm02b : (48.152783333, -122.686316666) Deployments TTM01b and TTM02b occurred simultaneously and were spaced approximately 50m apart in the cross-stream direction. Units ----- - Velocity data (_u, urot, uacc) is in m/s. - Acceleration (Accel) data is in m/s^2. - Angular rate (AngRt) data is in rad/s. - The components of all vectors are in 'ENU' orientation. That is, the first index is True East, the second is Truemore » North, and the third is Up (vertical). - All other quantities are in the units defined in the Nortek Manual. Motion correction and rotation into the ENU earth reference frame was performed using the Python-based open source DOLfYN library (http://lkilcher.github.io/dolfyn/). Details on motion correction can be found there. Additional details on TTM measurements at this site can be found in the included Marine Energy Technology Symposium paper. « less
Authors:
Publication Date:
Report Number(s):
50
DOE Contract Number:
FY14 AOP 1321
Product Type:
Dataset
Research Org(s):
Marine and Hydrokinetic Data Repository (MHKDR); National Renewable Energy Laboratory
Collaborations:
National Renewable Energy Laboratory
Sponsoring Org:
USDOE Office of Energy Efficiency and Renewable Energy (EERE), Wind and Water Technologies Office (EE-4W)
Subject:
16 Tidal and Wave Power; MHK; Marine; Hydrokinetic; energy; power; Admiralty Inlet; Puget Sound; water velocity; Turbulence; Matlab; data; DOLfYN; Python; TTM; vector files; code; resource; effectiveness; safety
Related Identifiers:
OSTI Identifier:
1245825
  1. The DOE Marine and Hydrokinetic Data Repository was established to receive, manage and make available all marine and hydrokinetic-relevant data generated from projects funded by the DOE Water Power Programs. This includes data from DOE-funded projects associated with any portion of the marine and hydrokinetic project life-cycle (e.g. resource characterization, device development, demonstration), as well as data produced by DOE-funded research. The database includes wave, tidal, current, and ocean thermal energy, and contains information on the various energy conversion technologies, companies active in the field, and development of projects in the water.
No associated Collections found.
  1. This data is from measurements at Admiralty Head, in Admiralty Inlet (Puget Sound) in May of 2015. The measurements were made using Inertial Motion Unit (IMU) equipped ADVs mounted on a 'StableMoor' (Manufacturer: DeepWater Buoyancy) buoy and a Tidal Turbulence Mooring (TTM). These platforms positionmore » ADV heads above the seafloor to make mid-depth turbulence measurements. The inertial measurements from the IMU allows for removal of mooring motion in post processing. The mooring and buoy motion has been removed from the stream-wise and vertical velocity signals (u, w). The lateral (v) velocity has some 'persistent motion contamination' due to mooring sway. The TTM was deployed with one ADV, it's position was: 48 09.145', -122 41.209' The StableMoor was deployed twice, the first time it was deployed in 'wing-mode' with two ADVs ('Port' and 'Star') at: 48 09.166', -122 41.173' The second StableMoor deployment was in 'Nose' mode with one ADV at: 48 09.166', -122 41.174' Units ----- - Velocity data (_u, urot, uacc) is in m/s. - Acceleration (Accel) data is in m/s^2. - Angular rate (AngRt) data is in rad/s. - The components of all vectors are in 'ENU' orientation. That is, the first index is True East, the second is True North, and the third is Up (vertical). - All other quantities are in the units defined in the Nortek Manual. Motion correction and rotation into the ENU earth reference frame was performed using the Python-based open source DOLfYN library (http://lkilcher.github.io/dolfyn/). Details on motion correction can be found there. Additional details on TTM measurements at this site can be found in the included Marine Energy Technology Symposium paper. « less
  2. This data is from measurements at Admiralty Head, in admiralty inlet. The measurements were made using an IMU equipped ADV mounted on a mooring, the 'Tidal Turbulence Mooring' or 'TTM'. The inertial measurements from the IMU allows for removal of mooring motion in post processing.more » The mooring motion has been removed from the stream-wise and vertical velocity signals (u, w). The lateral (v) velocity may have some 'persistent motion contamination' due to mooring sway. The ADV was positioned 11m above the seafloor in 58m of water at 48.1515N, 122.6858W. Units ----- - Velocity data (_u, urot, uacc) is in m/s. - Acceleration (Accel) data is in m/s^2. - Angular rate (AngRt) data is in rad/s. - The components of all vectors are in 'ENU' orientation. That is, the first index is True East, the second is True North, and the third is Up (vertical). - All other quantities are in the units defined in the Nortek Manual. Motion correction and rotation into the ENU earth reference frame was performed using the Python-based open source DOLfYN library (http://lkilcher.github.io/dolfyn/). Details on motion correction can be found there. For additional details on this dataset see the included Marine Energy Technology Symposium paper. « less
  3. AASG Wells Data for the EGS Test Site Planning and Analysis Task Temperature measurement data obtained from boreholes for the Association of American State Geologists (AASG) geothermal data project. Typically bottomhole temperatures are recorded from log headers, and this information is provided through a boreholemore » temperature observation service for each state. Service includes header records, well logs, temperature measurements, and other information for each borehole. Information presented in Geothermal Prospector was derived from data aggregated from the borehole temperature observations for all states. For each observation, the given well location was recorded and the best available well identified (name), temperature and depth were chosen. The “Well Name Source,” “Temp. Type” and “Depth Type” attributes indicate the field used from the original service. This data was then cleaned and converted to consistent units. The accuracy of the observation’s location, name, temperature or depth was note assessed beyond that originally provided by the service. - AASG bottom hole temperature datasets were downloaded from repository.usgin.org between the dates of May 16th and May 24th, 2013. - Datasets were cleaned to remove “null” and non-real entries, and data converted into consistent units across all datasets - Methodology for selecting ”best” temperature and depth attributes from column headers in AASG BHT Data sets: • Temperature: • CorrectedTemperature – best • MeasuredTemperature – next best • Depth: • DepthOfMeasurement – best • TrueVerticalDepth – next best • DrillerTotalDepth – last option • Well Name/Identifier • APINo – best • WellName – next best • ObservationURI - last option. The column headers are as follows: • gid = internal unique ID • src_state = the state from which the well was downloaded (note: the low temperature wells in Idaho are coded as “ID_LowTemp”, while all other wells are simply the two character state abbreviation) • source_url = the url for the source WFS service or Excel file • temp_c = “best” temperature in Celsius • temp_type = indicates whether temp_c comes from the corrected or measured temperature header column in the source document • depth_m = “best” depth in meters • depth_type = indicates whether depth_m comes from the measured, true vertical, or driller total depth header column in the source document • well_name = “best” well name or ID • name_src = indicates whether well_name came from apino, wellname, or observationuri header column in the source document • lat_wgs84 = latitude in wgs84 • lon_wgs84 = longitude in wgs84 • state = state in which the point is located • county = county in which the point is located « less
  4. This document presents results from tests to demonstrate underwater mapping capabilities of an underwater vehicle in conditions typically found in marine renewable energy arrays. These tests were performed with a tethered Seabotix vLBV300 underwater vehicle. The vehicle is equipped with an inertial navigation system (INS)more » based on a Gladiator Landmark 40 IMU and Teledyne Explorer Doppler Velocity Log, as well as a Gemini 720i scanning sonar acquired from Tritech. The results presented include both indoor pool and offshore deployments. The indoor pool deployments were performed on October 7, 2016 and February 3, 2017 in Corvallis, OR. The offshore deployment was performed on April 20, 2016 off the coast of Newport, OR (44.678 degrees N, 124.109 degrees W). During the mission period, the sea state varied between 3 and 4, with an average significant wave height of 1.6 m. Data was recorded from both the INS and the sonar. « less
  5. Field measurements of mean flow and turbulence parameters at the Kvichak river prior to and after the deployment of ORPC's RivGen hydrokinetic turbine. Data description and turbine wake analysis are presented in the attached manuscript "Wake measurements from a hydrokinetic river turbine" by Guerra andmore » Thomson (recently submitted to Renewable Energy). There are three data sets: NoTurbine (prior to deployment), Not_Operational_Turbine (turbine underwater, but not operational), and Operational_Turbine. The data has been quality controlled and organized into a three-dimensional grid using a local coordinate system described in the paper. All data sets are in Matlab format (.mat). Variables available in the data sets are: qx: X coordinate matrix (m) qy: Y coordinate matrix (m) z : z coordinate vector (m) lat : grid cell latitude (degrees) lon: grid cell longitude (degrees) U : velocity magnitude (m/s) Ux: x velocity (m/s) Vy: y velocity (m/s) W: vertical velocity (m/s) Pseudo_beam.b_i: pseudo-along beam velocities (i = 1 to 4) (m/s) (structure with raw data within each grid cell) beam5.b5: 5th-beam velocity (m/s) (structure with raw data within each grid cell) tke: turbulent kinetic energy (m2/s2) epsilon: TKE dissipation rate (m2/s3) Reynolds stresses: uu, vv, ww, uw, vw (m2/s2) Variables from the Not Operational Turbine data set are identified with _T Variables from the Operational Turbine data set are identified with _TO « less