Skip to content

Enhance the ASCII2NC wrapper to support setting the -valid_beg and -valid_end command line options #2547

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

The issue dtcenter/MET#2654 and pull request dtcenter/MET#2846 updated the ASCII2NC tool to add support for -valid_beg and -valid_end command line options to support filtering the input point observations by their valid time. These command line options already exist in PB2NC, a similar point pre-processing tool.

This issue is to enhance the ASCII2NC wrapper to support the setting of these command line options in a way that is consistent with how they're supported for PB2NC.

Time Estimate

4 hours?

Sub-Issues

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

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

split between Dynamic drought veg (2785031) and the UAlbany (7750034) projects

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)

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.

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.
  • 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 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