.. _phase1:
.. raw:: html
.. role:: red
.. raw:: html
.. role:: blue
Phase 1: the baseline
================================
**Phase 1 is now completed, please refer to later phases! Slides that show phase 1 results can be downloaded `here `_ **
In Phase 1, the benchmark team releases LIMITED inflow observations at AWAKEN for 24 August 2023 (and the day before, if needed to start the simulations) and NREL’s open-source wind turbine model to the benchmark participants.
The participants leverage the limited inputs and their own best practices to simulate the wakes from the King Plains and Armadillo Flats wind plants.
The benchmark team then compares the simulated results with the observed values.
Please read the instructions below in detail.
Phase 1 is now completed. It officially started on 28 May 2024. Participants submitted results for Phase 1 (as specified below) by 1 September 2024.
Model inputs and recommendations
---------------------------------
The following inputs and recommendations are provided to the benchmark participants:
- Recommended topographical data set
- USGS 1⁄3 arc-sec Digital Elevation Model (DEM) can be downloaded from the USGS National Map Downloader (https://apps.nationalmap.gov/downloader/#/). You will want to select the Elevation Product, and the 1/3 datasets will be selected by default. Then, use the map to zoom into your area of interest and use the search products button. You can then see what products are available in the area covered by your current map extent. To download a product, click the download link to the right of it. We note that for mesoscale models coarser data sets can be used, such as the WRF default 30-sec data set. Below, we provide a suggested step-by-step process on how to use the USGS data in WRF:
- Download the .tif file from the website linked above
- In QGIS, Layer -> Add Layer -> Add Raster Layer; select the .tif file
- Using the GIS4WRF plugin, GIS4WRF -> Datasets -> Process -> Convert active layer to WPS binary -> Is this layer's data categorical? (NO) -> Save data
- Copy binaries and index files to a new directory, for instance, “topo_srtm_3s”
- Move “topo_srtm_3s” to the directory that stores WRF static datasets, which is usually WPS_GEOG
- Create the new terrain class “topo_srtn_1_3s” in GEOGRID.TBL
- Select as an option in the WRF namelist.wps
geog_data_res = 'topo_srtm_1_3s'
NOTE: William Radünz kindly shared the 'USGS_13_n37w098_20181130.tif' file, which includes the terrain data for the AWAKEN site, at `this `_ link. The folder also contains the data already pre-processed for WRF users in the 'topo_srtm_1_3s’ folder.
- Recommended land use data set
- National Land Cover Dataset 1 arc-sec 2019, about 30 m spatial resolution, can be downloaded from https://www.sciencebase.gov/catalog/item/604a4fb1d34eb120311b0039. Below, we provide a suggested step-by-step process on how to use this data in WRF:
- Download the nlcd_2019_land_cover_l48_20210604.zip file from the link above and extract data
- Import nlcd_2019_land_cover_l48_20210604.img into QGIS (Layer->Add-Layer->Raster->Source)
- Using the GIS4WRF plugin: Plugins->GIS4WRF->Datasets->Process->Convert active layer to WPS binary, and save it inside a folder named ‘nlcd2019_ll_1s’, for instance
- Move WPS binaries to the directory that stores WRF static datasets, which is usually WPS_GEOG
- The GEOGRID.TBL dictionary must create a new object (for example, with the name “nlcd20_1s”) that selects and points to the NLCD 2019 data; later on, this option should be selected in the namelist.wps
- The LANDUSE.TBL and VEGPARM.TBL dictionaries must create a new object (for example, with the name “NLCD20”) that contains a table that relates the land use categories with surface characteristics, such as roughness
- The WRF namelist.wps should contain
geog_data_res = 'nlcd20_1s'
- The WRF namelist.input should contain
num_soil_layers = 4,
num_land_cat = 20
- Recommended roughness length values
- We do not impose a fixed roughness length value to the benchmark participants. Instead, this should be considered as a calibration parameter to match the observed atmospheric conditions. In general, the AWAKEN region is characterized by pastures, crops, and scattered trees, so that roughness length values between 0.03-0.2 m seem appropriate. We also note that in WRF the roughness will be calculated by the land surface model used, and then adopted in the selected surface layer scheme.
- King Plain and Armadillo Flats turbine locations and dimensions
- Can be downloaded `here `_. Note: the USGS wind turbine data base information about these two wind farms are NOT accurate.
- Wind turbine model
- The turbines in the King Plains and Armadillo Flats wind farms are of four different models, as detailed in :doc:`field_site`. For each of the four turbine types, we provide an open-source turbine model, including Cp and Ct curves, RPM table, pitch table, lift and drag table. The open-source model and documentation on how to use it can be found `here `_. NEW: WRF-specific files that include information on the four turbine types can now be found `here `_.
- Observed inflow wind speed, wind direction, and turbulence. Data also include the day before (23 August 2023) the selected case study if needed.
- 10-minute average and 1-second retrievals of horizontal wind speed, wind direction, vertical wind speed (and, for the 1-s data, two horizontal wind components) are provided from the profiling lidar at site A1. Data are provided every 20 m from 40 m to 240 m a.g.l.
- 10-minute average retrievals of TI and TKE are provided from the scanning lidar at site A1. Data are provided at 110 m a.g.l.
- data are available in netCDF format `here `_.
- `this `_ python script can be used as an example to access and explore these data sets.
- Observed inflow temperature. Data also include the day before (23 August 2023) the selected case study if needed.
- 30-minute average temperature profiles at the surface from the ASSIST-II at site B.
- data are available in netCDF format `here `_.
- `this `_ python script can be used as an example to access and explore this data set.
- Observed inflow Obukhov length. Data also include the day before (23 August 2023) the selected case study if needed.
- 30-minute average time series at 4 m a.g.l. from sonic anemometers at site A1.
- data are available in netCDF format `here `_.
- `this `_ python script can be used as an example to access and explore this data set.
More details about the observations can be found in the :ref:`Measurements` page. Note: for all average files, the time stamps indicate the middle of the averaging period (e.g., if a file that has 30-minute average data has a :45 time stamp, it means that data from :30 to :00 have been averaged).
We note that any parameters not listed above are left to the decisions of each participant.
Phase 1 submission
---------------------------------
Benchmark participants are required to submit the following FOUR files by 1 September 2024:
- ONE .txt file with model setup information:
- domain extension
- 3D grid resolution
- temporal resolution (and specify if results are being submitted as averages or instantaneous values)
- other model setup choices (e.g., PBL scheme in WRF)
- any assumed constants used to run the model (e.g., roughness)
- how your model calculates TI and TKE (if it does -- see more details below)
- If you use any observations not directly provided as part of the benchmark (i.e., listed on this page), please make note of it in this file, and specify what you used and to do what.
- ONE .netCDF file with modeled atmospheric inflow. The .netCDF file template to be filled with simulated data can be found `here `_. Do NOT change the variable names and heights in the file. Please interpolate your simulated data to match the heights listed below whenever reasonable (e.g., if your simulated domain extends to 2 km a.g.l., DO NOT guess/extrapolate any values above that). Please DO change the temporal dimension in the template to match that of your model output. If your model output is available at really high frequency, such that the file to submit would become too big, please do NOT calculate averages, and just submit instantaneous data at whatever time resolution you feel comfortable submitting results at. Please only submit TI and TKE if your model directly outputs them. If that is the case, please specify in the .txt file above how they are calculated (averaging time, center of the window, etc.). If your model does NOT directly calculate TI and TKE, please do NOT provide them in the submitted file, and we will calculate them ourselves whenever possible to ensure consistency. NaNs should be used where simulated data are not available. You can find the coordinates of the AWAKEN sites in the :ref:`Measurements` page.
- Time series of u, v, w, wind speed, wind direction, TI, TKE, Obukhov length at sites A1, A2, and A5 at 4 m a.g.l..
- Time series of u, v, w, wind speed, wind direction, TI, TKE at sites A1, A2, B, and E36 every 10 m from 40 m through 4000 m a.g.l..
- Time series of temperature at sites B and E36 at the following heights: [0, 10, 21, 33, 46, 61, 77, 95, 114, 136, 159, 185, 214, 245, 280, 318, 359, 405, 456, 512, 573, 640, 714, 795, 885, 983, 1092, 1211, 1342, 1486, 1645, 1819, 2011, 2223, 2455, 2710, 2991, 3300, 3640, 4014] m a.g.l..
- ONE .netCDF file with modeled turbine response. The .netCDF file to be filled with simulated data can be found `here `_. Do NOT change the variable names and heights in the file. The same considerations as above apply for the time resolution of the results to submit. NaNs should be used where simulated data are not available.
- Time series of hub-height (80 m, 88.5 m, or 90 m a.g.l., see heights for various turbines in the spreadsheet linked above) wind speed at the locations (see coordinates in spreadsheet linked above) of all the Armadillo Flats and King Plains turbines. Note: these simulated values will be compared with those from the turbine SCADA, whose values are reported AFTER a nacelle transfer function is applied.
- Time series of power produced by each of the Armadillo Flats and King Plains turbines.
- ONE .netCDF file with modeled wake. The .netCDF file to be filled with simulated data can be found `here `_. Do NOT change the variable names and heights in the file. The same considerations as above apply for the time resolution of the results to submit. NaNs should be used where simulated data are not available. You can see the coordinates of the AWAKEN sites in the :ref:`Measurements` page.
- Time series of u, v, w, wind speed, wind direction, TI, TKE at sites C1a, H, and Golf Course every 10 m from 40 m through 4000 m a.g.l..
- Time series of u, v, w, wind speed, wind direction, TI, TKE, Obukhov length at sites C1a, G, and H at 4 m a.g.l..
- Time series of temperature at sites H, C1a, G, and Golf Course at the following heights: [0, 10, 21, 33, 46, 61, 77, 95, 114, 136, 159, 185, 214, 245, 280, 318, 359, 405, 456, 512, 573, 640, 714, 795, 885, 983, 1092, 1211, 1342, 1486, 1645, 1819, 2011, 2223, 2455, 2710, 2991, 3300, 3640, 4014] m a.g.l..
- Evolution of wind speed and wind direction across eight horizontal planes north of the E06 King Plains turbine. Height a.g.l. (m) of the eight horizontal planes: 27, 59, 90.5, 122, 154, 217.5, 281, 344.5. Note that the data shall be compiled using a coordinate system centered on the E06 turbine, with x being north-south, y east-west, z vertical. In the template, for each horizontal plane, the x dimension varies from 0 (i.e., the turbine) to ~ +4 km (i.e., north of the turbine) at every 127 m (i.e., 1 rotor diameter); the y dimension varies from -2.54 km (i.e., west of the turbine) to +2.54 km (i.e., east of the turbine) at every 127 m (i.e., 1 rotor diameter).
Notes:
- in the above, v is the wind component along the North-South direction (positive going from South to North), u is the wind component along the East-West direction (positive going from West to East), w is the vertical component (positive going up).
- more in general, units for all variables are detailed in the Glossary page here on the website.
- we are also now providing python scripts that can be used to create templates with a different time resolution from the one provided by us. These scripts are really easy to use (they only require modifying ONE number as detailed in the scripts). The scripts are available in the same Box folders linked above.
Each participant should submit the FOUR files (one .txt file, three .netCDF files) in the Box folder communicated to each participant at the beginning of the benchmark. For any question about the result submission, please email nicola.bodini@nrel.gov.