Skip to content

Enhance PB2NC to derive Mixed-Layer CAPE (MLCAPE). #1824

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

On 6/8/21, NOAA/EMC requested that the PB2NC tool be enhanced to derive additional variations of CAPE. They are most interested in mixed-layer CAPE (representing the average characteristics of the boundary layer). Mixed-layer is the "flavor" of CAPE that was recommended to be verified in our models, via the metrics workshop.

While PB2NC does currently derive CAPE, it is surface-based CAPE and its done by calling this Fortran sub-routine:
https://github.com/dtcenter/MET/blob/main_v10.0/met/src/tools/other/pb2nc/calcape.f
That routine was taken from the NOAA/EMC VSDB verification code, but no such code exists for mixed-layer CAPE. However, it is defined in UPP.

This task is to enhance PB2NC to derive the mixed-layer variation of CAPE. Consider some of the implementation options:

  • We could keep the scope limited and lift/adapt the code for deriving MLCAPE from the UPP source code. Should we keep that code in Fortran or re-write in C++?
  • We could expand the scope considerably and investigate a more direct interface to the UPP derivation routines. But this would add a new dependency on UPP.

An example of a UPP module to compute CAPE can be found at:

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the enhancement down into sub-issues.

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

needs to be done by 7/31/21 if possible

Funding Source

2792541

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required: not sure yet
  • Select scientist(s) or no scientist required: Perry S

Labels

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

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

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 Linked 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 and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions