Skip to content

Use Case: Renewable Energy Forecasting #97

@jaredalee

Description

@jaredalee

Describe the Use Case

This I-WRF demo will involve configuring the WRF container to run a single WRF-Solar simulation for ~48 h duration with 15-min output over a high-resolution domain over New York State (NYS). This simulation length will span both intra-day and day-ahead time horizons, which are relevant for electric utility operations. The verifying observations will come from the NYS Mesonet, which has graciously agreed to allow us to post 48 h of NYSM observations publicly with this I-WRF use case demo. The METplus container will use point-stat to verify surface variables (including global horizontal irradiance, 2-m temperature, and 10-m wind speed) at the 127 standard network stations and hub-height variables (100-m wind speed, 100-m temperature) at the 17 profiler network stations. Visualization scripts will plot maps of WRF output, maps of errors across the network of stations, as well as time series of the bulk errors.

Use Case Name and Category

Renewable Energy Forecasting. In the Users Guide, this will replace 6.3. Regional Climate Simulations. The NCAR and Cornell PIs have collectively agreed to this change.

Input Data

  • 48 h of forecasts from the High-Resolution Rapid Refresh (HRRR) model, which can be freely downloaded from AWS, to serve as the initial and lateral boundary conditions (ICs/LBCs) for WRF (nothing to be stored locally)
  • Surface observations from NYS Mesonet's 127 standard network stations (GHI, 2-m T, 10-m WS, SLP, precip) (minimal file size)
  • Hub-height observations from NYS Mesonet's 17 profiler network stations (100-m WS, 100-m T) (minimal file size)

Acceptance Testing

Describe tests required for new functionality.
As use case develops, provide a run time here
Initially build, test, and document instructions for this use case demo on NSF NCAR HPC. Then do the same on Jetstream2 and Red Cloud.

Time Estimate

3–4 weeks total for all the sub-issues (to be listed below as they get created).

Sub-Issues

Relevant Deadlines

1 May 2026

Funding Source

NSF I-WRF project (PRJ003917)

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Select component(s)
  • Select priority
  • Select requestor(s)
  • Select privacy

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

New Use Case Checklist

  • Complete the issue definition above, including the Time Estimate and Funding source.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept your changes. Merge branch into develop.
  • Create a second pull request to merge develop into develop-ref, following the same steps for the first pull request.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

No fields configured for Feature.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions