Phase 2: model improvement with inflow observations

Slides that show phase 1 results can be downloaded here.

In phase 2, The team releases ALL the inflow observations and SOME SCADA to the benchmark participants. The participants leverage the additional inputs and what learnt in Phase 1 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 2 officially starts on 12 November 2024, when results from Phase 1 are released. Participants are expected to submit results for Phase 2 (as specified below) by 15 January 2025.

UPDATES from phase 1

  • A reminder that USGS has wrong information for Armadillo Flats.

  • We recently realized that we had some errors in the spreadsheet for the turbine locations/coordinates:

    • King Plains was NOT affected

    • The coordinates of the Armadillo Flats turbine were all correct, but the wrong turbine type was sometime associated

    • The turbines in the northern portion of Armadillo Flats (i.e., closer to King Plains) were not affected

    • All phase 1 submissions were equally affected

    • We are not allowed to share any Armadillo Flats validation anyways

    • We have now updated the new file online

    • EVERYONE PLEASE DOWNLOAD THE NEW SPREADSHEET FILE here!

Model inputs and recommendations

The following inputs and recommendations are provided to the benchmark participants, on top of what already released in Phase 1 (please read that list, too):

  • SCADA (limited)

    • Normal operation: the following King Plains turbines were shut down the whole time on 24 August 2023: WIT_USKPL_SS001_WT011, WIT_USKPL_SS001_WT029, and WIT_USKPL_SS001_WT079. These four turbines were removed from the updated turbine location spreadsheet here

    • Curtailment: we provide a 1-min time series, for each King Plains turbine, with a binary flag to indicate derated/curtailed operation. 1 = derated, 0 = normal.

    • Yaw misalignment: we provide a 1-min time series, for each King Plains turbine, of the yaw misalignment.

    • Power production: we provide a 1-min average time series of power produced by selected King Plains turbines in the southmost row of turbines in the wind farm (WIT_USKPL_SS001_WT063, WIT_USKPL_SS001_WT064, WIT_USKPL_SS001_WT065, WIT_USKPL_SS001_WT066, WIT_USKPL_SS001_WT067, WIT_USKPL_SS001_WT068, WIT_USKPL_SS001_WT069, WIT_USKPL_SS001_WT070, and WIT_USKPL_SS001_WT071).

    • Data are available in netCDF format here.

  • Observed inflow wind speed, wind direction, and turbulence profiles

    • 10-minute average retrievals of horizontal wind speed, wind direction, three wind speed components, TI, and TKE are provided from the scanning lidars at sites A1 and A2. Data are provided every 10 m from 110 m to 4000 m a.g.l.

    • 4-s instantaneous retrievals of horizontal wind speed, wind direction, and the three wind components are provided from the scanning lidars at sites A1 and A2. Data are provided every 10 m from 110 m to 4000 m a.g.l.

    • 10-minute average retrievals of horizontal wind speed, wind direction, vertical wind speed are provided from the scanning lidar at site E36. Data are provided every 28 m from 98 m to over 10,000 m a.g.l.

    • 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 B. Data are provided every 20 m from 40 m to 300 m a.g.l.

    • 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.

    • 2-minute average retrievals of horizontal wind speed, wind direction, vertical wind speed are provided from the profiling lidar at site A2. Data are provided every 20 m from 40 m to 220 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 profiles

    • 30-minute average temperature profiles from the surface up to over 15 km (at varying vertical resolution) from the ASSIST-II at site B.

    • 10-minute average temperature profiles from the surface up to over 15 km (at varying vertical resolution) from the ASSIST-II at site E36. Data are not available after 14 UTC.

    • 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 near-surface properties (wind speed, wind direction, u, v, w wind components, sonic temperature, sensible heat flux, friction velocity, TKE, Obukhov length)

    • 30-minute average time series at 4 m a.g.l. from sonic anemometers at sites A1, A2, and A5.

    • data are available in netCDF format here.

    • this python script can be used as an example to access and explore these data sets.

More details about the observations can be found in the Measurements page.

We note the following: - participants are encouraged to make their own decisions about which inflow data set(s) to use to force their simulations. The results about the ‘best’ inflow data sets to use will be part of the overall results of the benchmark. - any parameters not listed above are left to the decisions of the single participants.

Phase 2 submission

Benchmark participants are required to submit the following FOUR files by 15 December 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.

    • NEW: what forcing data (e.g., reanalysis) you used to force your simulation, if any.

    • NEW: your WRF namelists (for WRF-based models only).

  • 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 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 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.