Use a larger time step for MPAS forecast
Open
@jim-p-w is already working on this.
Since Mar 20, 2024.
- Dominant language
- Python
- Stars
- 25
- Forks
- 19
- Avg merge
- 1d 49m
- Merged PRs (30d)
- 2
Description
I believe we are still using 6dx for the forecast time step in our workflow and experiments.
I suggest we try 8dx, in the cycling and longer-range forecasts.
This will make experiment run faster and save a not small % of core hours.
Once we confirm this larger time step works well for you, we should set this as the default in the workflow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.