Skip to content

Make the specification of a binary threshold in Wavelet-Stat optional. #1746

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

This issue arose via the JTTI project meeting. For this project, we need the ability to run Wavelet-Stat without applying a categorical threshold to convert the data to a binary image instead. This task is to make the thresholding step optional and deal with any consequences of that change.

Be sure to:
(1) Make the Wavelet-Stat thresholding step optional in the config file
(2) Consider the scientific impact of this change. For example, this may make MSE no longer summable across scales.
(3) Consider the impacts to the PostScript and NetCDF output from Wavelet-Stat.
(4) Add new unit tests to exercise this functionality.
(5) Update the scientific and technical documentation in the MET User's Guide.

Recommend coordinating with May Wong to test the changes.

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

List relevant project deadlines here or state NONE.

Funding Source

164951 - NOAA JTTI FV3SAR

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required: John HG
  • Select scientist(s) or no scientist required: Eric G

Labels

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

Projects and Milestone

  • Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
  • Select milestone to next major version milestone 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), Project(s), Milestone, and Linked issues
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Labels

required: FOR OFFICIAL RELEASERequired to be completed in the official release for the assigned milestonetype: enhancementImprove something that it is currently doing

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions