Skip to content

hybrid coordinate wrf  #1148

Open
Open

Description

@hkershaw-brown

hybrid coordinate:

"It is mandatory to use the terrain following coordinate
system (hybrid_opt=0)"?
#404 (comment)

.. Important ::
This tutorial was designed to be compatible with WRF Version 4 and later, and was
tested with WRFv4.5.2. It is mandatory to use the terrain following coordinate
system (hybrid_opt=0) and not the default sigma hybrid coordinates (hybrid_opt=1)
when using WRF-DART. Using the sigma hybrid coordinate can lead to adverse effects
when generating ensemble spread leading to poor forecast performance. For more
details see `DART Issue #650 <https://github.com/NCAR/DART/pull/650>`__.

! hybrid_opt 2 is a hybrid coordinate - terrain following at the
! surface, and straight pressure levels at the top.
integer, parameter :: VERT_HYBRID = 2

Apparently the "It is mandatory to use the terrain following coordinate
system" is only when using WRF CV3 perturbation to generate the boundary condition perturbed ensemble.

echo "ERROR: WRF-DART must use terrain following coordinates, hybrid_opt must be 0"

Needs to be explained in the docs.
Came in in d85b7a0
part of #1030

Originally posted by @hkershaw-brown in #741 (comment)

Activity

  1. braczka commented on Jul 13, 2026

    @braczka
    Contributor

    The statement in the documentation seems fairly clear, "Using the sigma hybrid coordinate can lead to adverse effects
    when generating ensemble spread leading to poor forecast performance." However, the link to the DART Issue needs to be updated from Issue #650 to #807, where I performed a detailed analysis on the negative impact of using hybrid-coordinates with pert_wrf_bc. I will issue a documentation fix for this.

  2. hkershaw-brown commented on Jul 13, 2026

    @hkershaw-brown
    CollaboratorAuthor

    My question is on this statement:
    "It is mandatory to use the terrain following coordinate system (hybrid_opt=0)"

    Is it mandatory to use the terrain following coordinate with WRF in DART in general, or just mandatory when following the WRF-DART tutorial?

  3. braczka commented on Jul 13, 2026

    @braczka
    Contributor

    It is mandatory when using the WRF-DART tutorial approach to perturb the boundary conditions -- which perturbs either the GFS or ECMWF state and applies it to the BC. If you have your own custom perturbed BC ensemble apriori (like Peter Jan) then you don't have to use this standard perturbation approach. The WRF-DART tutorial approach (for performing BC perts) is still how we recommend running WRF-DART in general -- the shell scripting used for the tutorial is identical to general WRF-DART. We only port in the severe storm information for the tutorial. In my experience the user having their own custom ensemble BC is not common.

  4. hkershaw-brown commented on Jul 13, 2026

    @hkershaw-brown
    CollaboratorAuthor

    Ok thanks, it would be good to have what is mandatory and when documented.
    Currently the bash version of the scripting models/wrf/shell_scripts/gen_retro_icbc.sh enforces "hybrid_opt must be 0"
    The models/wrf/shell_scripts_csh/gen_retro_icbc.csh does not seem to enforce this.
    The docs appear to say that hybrid_opt 0 must be used for WRF-DART, but really this is just for when using a generated perturbation bank.

  5. braczka commented on Jul 13, 2026

    @braczka
    Contributor

    I will provide a more detailed explanation in the tutorial docs, and also update the WRF model docs -- which are a bit out of sync with the WRF-DART tutorial

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    wrfWeather Research & Forecasting Modelwrf-chem

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions