Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Use Case: PointStat AMDAR PBLH with python embedding #2198

Closed
17 of 24 tasks
jason-english opened this issue Jun 5, 2023 · 0 comments · Fixed by #2206
Closed
17 of 24 tasks

New Use Case: PointStat AMDAR PBLH with python embedding #2198

jason-english opened this issue Jun 5, 2023 · 0 comments · Fixed by #2206
Assignees
Labels
type: new use case Add a new use case
Milestone

Comments

@jason-english
Copy link
Contributor

jason-english commented Jun 5, 2023

Replace italics below with details for this issue.

Describe the New Use Case

Using python embedding, compute PBLH from AMDAR aircraft data using the "Theta-increase" method (Nielsen-Gammon et al., 2008, J. App. Met. Clim.), which creates an altitude ascending array for each flight, computes a potential temperature base value, and finds the first altitude that exceeds a specified increase in potential temperature. The geographic region(s)/airport(s) of interest is specified, and the lat/lon domain to determined by processing a static mask (which is created for each region/airport via gen_vx_mask). The airport(s), pt_delta (theta-increase), and sounding can all be specified in the configuration script.

Use Case Name and Category

PointStat_fcstHRRR_obsAMDAR_PBLH
Category: model_applications/pbl

Input Data

AMDAR hourly netcdf file: 221822000q.cdf (7.1 MB)
HRRR grib2 file: hrrr_pblh_2218208000012 (5.1 MB)

Acceptance Testing

Use gen_vx_mask to create a circular static mask around the airport(s) of interest, and then point-stat with python embedding to generate .stat files of PBL Height.

Time Estimate

Approximately 3 months (including PBLH algorithm development)

Sub-Issues

  • Add a checkbox for each sub-issue here.

Relevant Deadlines

To be implemented as part of the June 2023 MET/METplus release.

Funding Source

GSL Task II funds

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

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

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

New Use Case 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.
  • Add any new Python packages to the METplus Components Python Requirements table.
  • 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 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 your changes. Merge branch into develop.
  • Create a second pull request to merge develop into develop-ref, following the same steps for the first pull request.
  • Delete your fork or branch.
  • Close this issue.
@jason-english jason-english added alert: NEED MORE DEFINITION Not yet actionable, additional definition required alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle type: new use case Add a new use case and removed alert: NEED MORE DEFINITION Not yet actionable, additional definition required alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle labels Jun 5, 2023
@jason-english jason-english linked a pull request Jun 8, 2023 that will close this issue
14 tasks
@DanielAdriaansen DanielAdriaansen added this to the METplus-5.1.0 milestone Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: new use case Add a new use case
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants