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

Add namelist.wps from the container to Github #58

Open
21 tasks
jaredalee opened this issue Jul 5, 2024 · 1 comment
Open
21 tasks

Add namelist.wps from the container to Github #58

jaredalee opened this issue Jul 5, 2024 · 1 comment
Assignees
Labels
component: documentation Documentation issues component: WRF WRF model issues type: task An actionable item of work
Milestone

Comments

@jaredalee
Copy link
Contributor

jaredalee commented Jul 5, 2024

Describe the Task

Add the WPS namelist (namelist.wps) file that is currently being used in the WRF container under development, to the use_cases/Hurricane_Matthew/WRF folder in the Github repo. This file should already have the container-relative file locations specified for geog_data_path, opt_geogrid_tbl_path, prefix, fname, and opt_metgrid_tbl_path. Then this namelist can be downloaded from the repository unmodified to support running the Hurricane Matthew test case. Once it has been uploaded to the repo, then Sec. 4.1.1.1 of the readthedocs should be updated accordingly to point directly to this file.

Time Estimate

Less than 1 hour.

Sub-Issues

  • Upload namelist.wps to use_cases/Hurricane_Matthew/WRF. (Bennett)
  • Update documentation in Sec. 4.1.1.1 to link to this namelist.wps. (Jared)

Relevant Deadlines

12 Jul 2024

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

  • 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

Task 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 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 Development 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.
@jaredalee jaredalee added type: task An actionable item of work component: WRF WRF model issues component: documentation Documentation issues labels Jul 5, 2024
@jaredalee jaredalee added this to the I-WRF 0.1.0 milestone Jul 5, 2024
@jaredalee
Copy link
Contributor Author

jaredalee commented Jul 5, 2024

@Trumbore, I initially assigned this to @rcplane, but it's also something you could take care of quickly. By uploading your modified namelist.wps to use_cases/Hurricane_Matthew/WRF in the repo, then you could adjust the run script to simply download namelist.wps from the repository, rather than modifying it locally. Similarly, the WRF namelist (namelist.input), which I just updated and committed per our meeting this morning, can be directly downloaded from the repo instead of doing any local modification of the file. That would make for a cleaner run script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: documentation Documentation issues component: WRF WRF model issues type: task An actionable item of work
Projects
None yet
Development

No branches or pull requests

2 participants