The blocking and weather regime code currently require input that has the same number of days for each year. So, if someone is verifying DJF for 10 years, each year would need to have 90 days of data (leap years omitted). The driver script in METplus will fill missing data, but the user must enter start and end dates to include 90 days of each year (20001201 - 20200228 would work, whereas 20001201 - 20200101 would not). The code came to us this way, but it should be made more flexible. Making it more flexible will allow to remove some variables needed in the blocking and weather regime use cases
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
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required
Labels
[ ] Review default alert labels
[ ] Select component(s)
[ ] Select priority
[ ] Select requestor(s)
Milestone and Projects
[ ] Select Milestone as a METcalcpy-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
[ ] For a METcalcpy-X.Y.Z version, select the METcalcpy-X.Y.Z Development project
Define Related Issue(s)
Consider the impact to the other METplus components.
[ ] 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 issue
Select: Milestone as the next official version
Select: METcalcpy-X.Y.Z Development project for development toward the next official release
[ ] Iterate until the reviewer(s) accept and merge your changes.
Describe the Enhancement
The blocking and weather regime code currently require input that has the same number of days for each year. So, if someone is verifying DJF for 10 years, each year would need to have 90 days of data (leap years omitted). The driver script in METplus will fill missing data, but the user must enter start and end dates to include 90 days of each year (20001201 - 20200228 would work, whereas 20001201 - 20200101 would not). The code came to us this way, but it should be made more flexible. Making it more flexible will allow to remove some variables needed in the blocking and weather regime use cases
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.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Milestone and Projects
Define Related Issue(s)
Consider the impact to the other METplus components.
Enhancement Checklist
See the METplus Workflow for details.
feature_<Issue Number>_<Description>feature <Issue Number> <Description>