NCAR / NCAR/wrfcloud

Move non-production settings of YAML config file into "debug" collection

Open
#82 0 comments 0 reactions 1 assignee View on GitHub

@mkavulich is already working on this.

Since Oct 4, 2022.

alert: NEED MORE DEFINITION type: enhancement
Dominant language
Python
Stars
18
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Describe the Enhancement

Certain settings in the config file for a WRF run are related to manual debug runs only, e.g. local_data and exists in the run collection. These should be split out into their own debug collection.

Time Estimate

2 hours

Sub-Issues
Relevant Deadlines

2022-10-07

Define the Metadata

Assignee
  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required
Labels
  • Select component(s)
  • Select priority
Projects and Milestone
  • Select Project
  • Select Milestone as the next official version or Backlog of Development Ideas

Enhancement Checklist

  • 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 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, and Development issue
    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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.