NCAR / NCAR/wrfcloud

Change WPS and/or WRF settings so that initial conditions have hydrometeors

Open
#77 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component: NWP components priority: medium type: enhancement
Dominant language
Python
Stars
18
Forks
6
PR merge metrics
No merged PRs in 30d

Description

The current settings of WPS/WRF are such that the initial state of the model (initial wrfout files) has no hydrometeors. This greatly affects the initial forecast moisture fields, and results in unrealistic precipitation forecasts for the first several hours of the simulation (long spin-up time). This seems especially bad for a tropical setting.

Describe the Enhancement

Modify the WPS or WRF settings (or both) in order to include hydrometeors in the initial conditions.

This may be as simple as modifying the VTABLE, per this wrfhelp forum post: https://forum.mmm.ucar.edu/threads/resolved-using-hydrometeor-mixing-ratios-in-gfs-metgrid-error-in-ext_pkg_write_field.8644/

There is literature that indicates this significantly reduces spin-up time (improves short-term forecasts): https://ui.adsabs.harvard.edu/abs/2020AGUFMA183.0007L/abstract

Time Estimate

1 day

Sub-Issues

Consider breaking the enhancement down into sub-issues.

  • Add a checkbox for each sub-issue here.
Relevant Deadlines

NONE

Define the Metadata

Assignee
  • Select no engineer required
  • Select scientist(s) required
Labels
  • Select component(s)
  • Select priority
Projects and Milestone
  • Select Project
  • Select Milestone as the next official version or Backlog of Development Ideas

Enhancement 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 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), Project, and Development issue
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the repository's WPS and WRF configuration and any VTABLE used to generate the initial wrfout files. Reproduce the current initialization, inspect the hydrometeor fields, and compare the result after changing the settings. Done means the initial conditions include hydrometeors and the first forecast hours show reduced moisture spin-up.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.