Closed simtheverse closed 1 year ago
For some background, when the Product Development Group (PDG) designed the Execution Control part of the SpaceFOM standard, the scenario timeline was selected for freeze times since this timeline is common to both HLA time managed and non HLA time-managed federates.
The issue here is that the calculation of the simulation time from the scenario time did not take into account the time resolution used by Trick.
I configured the SpaceFOM example SIM_Roles_Test simulation to use 5 milliseconds for dynamics, lookahead & LCTS and I was able to reproduce the issue.
Please let me know if the updates I have checked in has fixed the issue for you and I will close the issue.
Hi @dandexter, The updates work very well and no issues observed! Thank you!
Hello,
I think this line is "disarming" planned pauses in my Other federate because of a suspected double/float math error: https://github.com/nasa/TrickHLA/blob/0580604b21dd210683286ab2b52e302ac5d16cd0/source/SpaceFOM/ExecutionControl.cpp#L2311 This happens often but not all the time and I can Freeze okay often as well.
When I initiate a freeze by pressing "Freeze" on the Trick Panel for the MPR federate, here is the console output from my Other federate:
Then when it gets around to: https://github.com/nasa/TrickHLA/blob/0580604b21dd210683286ab2b52e302ac5d16cd0/source/SpaceFOM/ExecutionControl.cpp#L2311, this boolean condition evaluates to True and goes back to execution mode when it should have paused.
Using print statements the Trick-sim-time and the simulation_freeze_time during that boolean condition is:
This is the print statement inserted above the line in question:
Is this a result of float/double comparison issues?
I am using trick at 06a1d2bf and trickhla at 0580604b, which I believe is master/latest at time of writing.