skip to main content

Title: Turbine Depth Optimization Study, Admiralty Inlet, WA

The zipped file contains a directory of data and routines used in the NNMREC turbine depth optimization study (Kawase et al., 2011), and calculation results thereof. For further info, please contact Mitsuhiro Kawase at
; ;
Publication Date:
Report Number(s):
DOE Contract Number:
Product Type:
Research Org(s):
Marine and Hydrokinetic Data Repository (MHKDR); Univ. of Washington, Seattle, WA (United States)
University of Washington
Sponsoring Org:
USDOE Office of Energy Efficiency and Renewable Energy (EERE), Wind and Water Technologies Office (EE-4W)
16 Tidal and Wave Power; MHK; Admiralty Inlet; Water velocity; Turbine power output; Northwest National Marine Renewable Energy Center; NNMREC; depth optimization; turbine depth data; calculation results; capacity contour; optimize; depth; power density; matlab; average power; capacity factor; average speed; area; profile; power law; tide period; rated speed; rated power; barotropic; pressure; snohomish; sst; Sound and Sea Technology; hub height; turbine; data; routines; procedure; calculations; tidal; in-stream; Washington; WA; code; technical report
Related Identifiers:
OSTI Identifier:
  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. Attached are the .cas and .dat files along with the required User Defined Functions (UDFs) and look-up table of lift and drag coefficients for the Reynolds Averaged Navier-Stokes (RANS) simulation of three coaxially located lab-scaled DOE RM1 turbine implemented in ANSYS FLUENT CFD-package. The lab-scaledmore » DOE RM1 is a re-design geometry, based of the full scale DOE RM1 design, producing same power output as the full scale model, while operating at matched Tip Speed Ratio values at reachable laboratory Reynolds number (see attached paper). In this case study the flow field around and in the wake of the lab-scaled DOE RM1 turbines in a coaxial array is simulated using Blade Element Model (a.k.a Virtual Blade Model [VBM]) by solving RANS equations coupled with k-\omega turbulence closure model. It should be highlighted that in this simulation the actual geometry of the rotor blade is not modeled. The effect of turbine rotating blades are modeled using the Blade Element Theory. This simulation provides an accurate estimate for the performance of each device and structure of their turbulent far wake. The results of these simulations were validated against the developed in-house experimental data. Simulations for other turbine configurations are available upon request. « less
  2. 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
  3. Attached are the .cas and .dat files for the Reynolds Averaged Navier-Stokes (RANS) simulation of a single lab-scaled DOE RM1 turbine implemented in ANSYS FLUENT CFD-package. The lab-scaled DOE RM1 is a re-design geometry, based of the full scale DOE RM1 design, producing same powermore » output as the full scale model, while operating at matched Tip Speed Ratio values at reachable laboratory Reynolds number (see attached paper). In this case study taking advantage of the symmetry of lab-scaled DOE RM1 geometry, only half of the geometry is models using (Single) Rotating Reference Frame model [RRF]. In this model RANS equations, coupled with k-\omega turbulence closure model, are solved in the rotating reference frame. The actual geometry of the turbine blade is included and the turbulent boundary layer along the blade span is simulated using wall-function approach. The rotation of the blade is modeled by applying periodic boundary condition to sets of plane of symmetry. This case study simulates the performance and flow field in the near and far wake of the device at the desired operating conditions. The results of these simulations were validated against in-house experimental data. Please see the attached paper. « less
  4. This data package provides daily measurements of snow depth at 195 National Weather Service (NWS) first-order climatological stations in the United States. The data have been assembled and made available by the National Climatic Data Center (NCDC) in Asheville, North Carolina. The 195 stations encompassmore » 388 unique sampling locations in 48 of the 50 states; no observations from Delaware or Hawaii are included in the database. Station selection criteria emphasized the quality and length of station records while seeking to provide a network with good geographic coverage. Snow depth at the 388 locations was measured once per day on ground open to the sky. The daily snow depth is the total depth of the snow on the ground at measurement time. The time period covered by the database is 1893-1992; however, not all station records encompass the complete period. While a station record ideally should contain daily data for at least the seven winter months (January through April and October through December), not all stations have complete records. Each logical record in the snow depth database contains one station's daily data values for a period of one month, including data source, measurement, and quality flags. The snow depth data have undergone extensive manual and automated quality assurance checks by NCDC and the Carbon Dioxide Information Analysis Center (CDIAC). These reviews involved examining the data for completeness, reasonableness, and accuracy, and included comparison of some data records with records in NCDC's Summary of the Day First Order online database. Since the snow depth measurements have been taken at NWS first-order stations that have long periods of record, they should prove useful in monitoring climate change. « less
  5. 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 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