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

Write instructions for running on HPC #38

Open
20 tasks
georgemccabe opened this issue Jun 2, 2023 · 0 comments
Open
20 tasks

Write instructions for running on HPC #38

georgemccabe opened this issue Jun 2, 2023 · 0 comments
Assignees
Labels
alert: NEED MORE DEFINITION Not yet actionable, additional definition required component: documentation Documentation issues deliverable 1.1 Generate desired configurations type: task An actionable item of work
Milestone

Comments

@georgemccabe
Copy link
Contributor

georgemccabe commented Jun 2, 2023

Start by running on Cheyenne. Can refer to Melissa's notes found on issue #6. Eventual goal is to run on Derecho when it is available, which uses a different batch submission utility (PBS vs. Slurm).

Describe the Task

Provide a description of the task here.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 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

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

  • 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.
@georgemccabe georgemccabe added type: task An actionable item of work alert: NEED MORE DEFINITION Not yet actionable, additional definition required component: documentation Documentation issues deliverable 1.1 Generate desired configurations labels Jun 2, 2023
@georgemccabe georgemccabe added this to the I-WRF 0.1.0 milestone Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alert: NEED MORE DEFINITION Not yet actionable, additional definition required component: documentation Documentation issues deliverable 1.1 Generate desired configurations type: task An actionable item of work
Projects
None yet
Development

No branches or pull requests

2 participants