I notice some strange things with the number of frames and simulation time in the PostProcessor.
Example:
I am running a simulation for 100s with a step size of 0.01s, which should result in 10.001 frames, right?
First thing i noticed: the frames and simulation time are correct at the start of the simulation, but during the simulation there arises a gap, for example at 04001 frames i expect a simulation time of 40s, not the 39.6s shown in the picture.
Second thing i noticed: the simulation consist of more than 10.001 frames (10.392 in this situation), but after frame 10.001 there is no motion, which is logical. But then why the extra frames?
Is this some sort of bug that you guys already know?
I am running a simulation for 100s with a step size of 0.01s, which should result in 10.001 frames, right?
This is not true or it is true for simple models
For example contact in model will increase number of frames.
If you try simple model like sphere falling on plane with contact , you will have different number of frames, with SI2 and I3, also changing solver settings like Hmax or Error will results in different number of frames for same simulation time and time step.
Ok so you say contacts can add extra frames to an animation. But why are these extra frames not animated? Because, i assumed these extra frames would be in the animation and the animation would stop at 100s, but thats not the case. The animiation stops at 10.001 frames and than continues (without motion) for another 200+ frames.
After reading the article i understand it is a well known issue. Thank you for the link!
As Jozef pointed out, we generate extra output steps around contact events so that we can capture proper animation of the contact. However, there was a bug in the post processor's animation in Adams 2020 FP1, which I believe you are experiencing this in. To get around this issue, please check the "Include Contact" option in the animation dashboard.