Termination with hybrid condition, where only one is exact, makes code crash for non-exact condition

[MiguelAvillez]

I have tried using an hybrid termination condition, where one of the conditions is based on a dependent variable, and the other is based on CPU time. I have only required one of the conditions to be satisfied to stop the propagation.

Both termination conditions work fine if the condition based on the dependent variable is not exact. If it is exact, everything also works fine if the end of the propagation is triggered by the condition based on the exact value of the dependent variable. However, if the end of the propagation is triggered by the CPU time the code crashes with Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Example of code triggering the issue is attached.

test_tudat_bundle.py.zip

[DominicDirkx]

I've made a small modification to the code, so that the iteration to an exact condition is only triggered if any of the conditions that are exceeded require an exact condition termination. I've checked your script, I was able to reproduce the issue, and it is now corrected.

I'll leave this issue open, as this case should be added to the unit tests:

• [ ] Add unit test for termination of CPU time (not exact) or dependent variable (exact), for either one being the limiting case