WRF Reference Configurations
- DTC RC
- Community Contributed RC
WRF Reference Configurations
Path to Reference Configuration
After code is checked in to the WRF Repository it is eligible to become part of a Reference Configuration. Once suggestions for configurations have been obtained from the community at large, the DTC Advisory Board will establish a prioritized list of candidate configurations, which will then go to the DC Executive Committee for final approval.
In order to serve both the operational and research communities, the DTC has developed the concept of Reference Configurations (RCs). By conducting carefully controlled, rigorous testing, including the generation of verification statistics, RCs provide the operational community guidance for selecting configurations with potential value for operational implementation. RCs provide the research community with baselines against which the impacts of new techniques can be evaluated. Statistical results for a RC also aid researchers in selecting a configuration to use for their particular application.
A RC is defined as a particular collection of configuration files that are set at compile-time and run-time. Each RC is uniquely defined and detailed in a design document. RCs are extensively tested, documented, and the baseline data and statistical verification results are made available to the community.
DTC Reference Configurations
The DTC solicits feedback from operational centers and the research community on which configurations to establish and maintain as DTC RCs. (Please visit the DTC RC submission webpage to propose a candidate configuration.) Striking a balance between keeping a traceable history of results from year to year and testing new features and capabilities in NWP is critical in considering which configurations will be tested. Ultimately, the candidate configurations are selected based on their potential use and value added to the research and operational communities.
DTC RC testing is generally retrospective in nature and encompasses a large number of cases. The cases are selected to encapsulate a broad range of weather regimes. The exact periods and domains chosen vary based on the type of phenomenon the configuration is designed to forecast. Once a RC has been run for the specified set of cases, extensive verification statistics are computed and the results are distributed to the user community via the DTC RC webpage. In addition, all input and output datasets are archived for at least one year.
DTC RC testing is generally based on official releases of the WRF code with the inclusion of any bug fixes that have been posted prior to retrospective testing.
More information on the process of designating DTC RCs can be found in the RC Implementation Plan (pdf).
Community Contributed Reference Configurations
To take advantage of extensive data sets being produced by the WRF user community the DTC also collects and distributes information on Community Contributed Reference Configurations (CCRCs).
For a user defined configuration to become a CCRC, the contributing user will be required to fully disclose the details of the code and configuration. A sufficient quantity of cases that represent a broad range of weather regimes relevant to that particular application must be available from a consistent (unchanged) version and configuration of the code in order to qualify. The contributing user must also provide at least a minimal set of verification measures for the cases. Information on CCRCs is posted on the DTC CCRC webpage. In order to keep the results most relevant to the user community, results from old versions of the code will eventually be retired or may be updated by the contributor with results from a more current version of WRF. More information on requirements for submitting CCRCs can be found in the RC Implementation Plan (pdf).
WOLFF, Jamie — PH: 303.497.2812 | EMAIL: jwolffucar.edu