Cyclic boundary condition not working for restart when intial time ne 0
Nobody has claimed this yet.
- Dominant language
- GLSL
- Stars
- 68
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
submitted 11/09/2010 into trac ticket system
Phil found when trying to add a cyclic boundary condition to his restart that it crashed if he defined his cycle time relative to time 0, i.e., times were entered as 0 30, 60, etc. If he defined his cycle to start at the restart time 17800, with 30 day increments, the boundary did not re-cycle every 30 days as desired. My guess is that the first cycle time became too big because the start time was a large number of days. See Phil for more info.
Contributor guide
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.
Research direction
Start by locating the cyclic boundary-condition and restart-handling code; no file or test is identified in the issue. Reproduce the reported cases with cycle times relative to 0 and to restart time 17800, then verify that the boundary recycles every 30 days without a crash.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100