[Discussion] Task Trigger Criteria
@wrtobin is already working on this.
Since May 23, 2023.
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
Currently all events trigger based on simulation time in some fashion.
Extracting the event trigger from the event and allowing a larger degree of input specification for what triggers an event could provide significant utility.
e.g.
we could trigger an task on a failure of the linear solver or nonlinear solver to converge which dumps matrix / residual information,
or we could monitor a specific geometric or material property and only trigger time history collection when a certain threshold is passed.
I'm sure there are numerous other possible use cases.
This could also add unwanted complexity to problem specification, or make debugging runtime failures a bit more complicated, etc.
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.
Assessment
This issue has not been assessed yet.