-
Notifications
You must be signed in to change notification settings - Fork 26
Open
Labels
MET: Configurationalert: NEED ACCOUNT KEYNeed to assign an account key to this issueNeed to assign an account key to this issuecomponent: documentationDocumentation issueDocumentation issuepriority: mediumMedium PriorityMedium Priorityrequestor: METplus TeamMETplus Development TeamMETplus Development Teamtype: taskAn actionable item of workAn actionable item of work
Milestone
Description
Describe the Task
In editing the Grid-Stat configuration section, it was noted that the same content listed in two spots:
- The Grid-Stat config section describes nbrhd, fourier, gradient, and distance_map
- The Config File overview ALSO describes those
We only want this information in one place in the User's Guide. Move the information in “Settings Specific to Individual Tools” section of the Config File Overview to the chapters for the specific tool.
Also, consider adding subsection headers until the Practical Information sections to reflect the same formatting as @jvigh added in this PR for the tc-diag tool.
Time Estimate
1 to 3 days of work
Sub-Issues
Consider breaking the task down into sub-issues.
- Add a checkbox for each sub-issue here.
Relevant Deadlines
September 30, 2021 (beta3)
Funding Source
TBD once work has begun
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.
Task 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.
Metadata
Metadata
Assignees
Labels
MET: Configurationalert: NEED ACCOUNT KEYNeed to assign an account key to this issueNeed to assign an account key to this issuecomponent: documentationDocumentation issueDocumentation issuepriority: mediumMedium PriorityMedium Priorityrequestor: METplus TeamMETplus Development TeamMETplus Development Teamtype: taskAn actionable item of workAn actionable item of work