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

Move the harmonic preprocessing to METcalcpy #165

Open
21 tasks
CPKalb opened this issue Mar 17, 2022 · 0 comments
Open
21 tasks

Move the harmonic preprocessing to METcalcpy #165

CPKalb opened this issue Mar 17, 2022 · 0 comments
Assignees
Labels
alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle priority: blocker Blocker requestor: METplus Team METplus Development Team requestor: NOAA/other NOAA Laboratory, not otherwise specified type: enhancement Improve something that it is currently doing

Comments

@CPKalb
Copy link
Contributor

CPKalb commented Mar 17, 2022

Describe the Enhancement

The harmonic pre-processing currently lives in METplus under the RMM use case. However, it should live in the pre-processing area of METcalcpy. It needs to be moved here and the import statements updated

Time Estimate

1 day

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

2793541

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 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.
@CPKalb CPKalb added priority: blocker Blocker type: enhancement Improve something that it is currently doing requestor: NOAA/other NOAA Laboratory, not otherwise specified alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED MORE DEFINITION Not yet actionable, additional definition required alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle requestor: METplus Team METplus Development Team labels Mar 17, 2022
@CPKalb CPKalb self-assigned this Mar 17, 2022
@CPKalb CPKalb removed alert: NEED ACCOUNT KEY Need to assign an account key to this issue alert: NEED MORE DEFINITION Not yet actionable, additional definition required labels Mar 17, 2022
@bikegeek bikegeek added this to the METcalcpy 2.1.0-beta2 milestone Mar 1, 2023
@JohnHalleyGotway JohnHalleyGotway modified the milestones: METcalcpy 2.1.0-beta2, METcalcpy 2.1.0 Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alert: NEED CYCLE ASSIGNMENT Need to assign to a release development cycle priority: blocker Blocker requestor: METplus Team METplus Development Team requestor: NOAA/other NOAA Laboratory, not otherwise specified type: enhancement Improve something that it is currently doing
Projects
No open projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants