Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Some what lacking documentation with regard "read-out" of critical termination condition . #233

Closed
THB0705 opened this issue Jun 6, 2023 · 2 comments

Comments

@THB0705
Copy link

THB0705 commented Jun 6, 2023

Hi,

As requested, here I write today. The issue I'm reporting only pertains to the docs and not the functioning of TudatPy itself. When implementing hybrid termination settings, I believe there should be example code or an explanation as to how one can determine on which of the termination conditions a propagation terminated (without having to inspect the state or dependent variable history). If not an explanation under the function hybrid_termination , perhaps a link to the class PropagationTerminationDetails with an explanation or example listed there.

If you have any questions please let me know.

With kind regards,

Teun

@larshinueber larshinueber transferred this issue from tudat-team/tudat-multidoc Feb 13, 2025
@larshinueber
Copy link
Member

Hi Teun,
There was a note added to the hybird_termination condition, which links to the PropagationTerminationDetailsFromHybridCondition.was_condition_met_when_stopping attribute. The attribute has a small code example how to read out the conditions that were met. The same code snippet is used in the post-processing of the Reentry example to show which of the conditions terminated the propagation.
Hope that clarifies it!

@DominicDirkx
Copy link
Member

Awesome, thanks Lars!

@github-project-automation github-project-automation bot moved this from tudat-multidoc to Closed in Tudat general development board Feb 28, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
Status: Closed
Development

No branches or pull requests

3 participants