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.

Sign up for GitHub

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

Jump to bottom

Tracking should not always trigger at the end of the simulation #7

Open
haraldkl opened this issue Mar 22, 2024 · 0 comments · May be fixed by #8
Open

Tracking should not always trigger at the end of the simulation #7

haraldkl opened this issue Mar 22, 2024 · 0 comments · May be fixed by #8
Assignees
@haraldkl

Comments

@haraldkl
Copy link
Member

In some cases it may not be desirable to trigger the tracking output at the end of the simulation. For example in APESmate settings, the end of the simulation time for each solver happens to be at every step of the overall execution.
@haraldkl haraldkl self-assigned this Mar 22, 2024
@haraldkl haraldkl linked a pull request Mar 23, 2024 that will close this issue
Draft
@haraldkl haraldkl linked a pull request Mar 23, 2024 that will close this issue
Trigger tracking not at program end or termination #8
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@haraldkl haraldkl

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Trigger tracking not at program end or termination apes-suite/tem-source
1 participant
@haraldkl