Skip to content

Enhance MET library code to support additional vertical level types in WRF files #2818

@georgemccabe

Description

@georgemccabe

@mrinalbiswas provided WRF Chem sample files that contain some vertical levels dimensions that are not currently supported by MET but could easily be added.

Describe the Enhancement

Add support for reading WRF files that use the following vertical dimensions:

  • bio_emissions_dimension_stag
  • klevs_for_dvel
  • soil_layers_stag
  • seed_dim_stag

Sample data is available in derecho:/glade/derecho/scratch/biswas/forMETplus

Time Estimate

<2 hours

Sub-Issues

Consider breaking the enhancement down into sub-issues.
None needed.

Relevant Deadlines

12.1.0

Funding Source

I-WRF (7790013)

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required - recommend @mrinalbiswas test these changes

Labels

  • Review default alert labels
  • Select component(s)
  • Select priority
  • Select requestor(s)

Milestone and Projects

  • Select Milestone as the next official version or Backlog of Development Ideas
  • For the next official version, select the MET-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

Enhancement Checklist

See the METplus Workflow for details.

  • 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 issue
    Select: Milestone as the next official version
    Select: MET-X.Y.Z Development project for development toward the next official release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions