You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The expected behavior of the BouncingBallStairs model is as follows:
Essentially, each time there's a bounce, the model schedules a time event for about 0.1s later.
The model also shows that, when an timed event happens at the same time as a state event, it can happen that the state event is not longer handled. That is, if the ball collides with the floor (the importer detects a zero crossing), but the floor moves, then the ball will no longer collide with the floor.
The behavior obtained from #70 is the incorrect one:
The text was updated successfully, but these errors were encountered:
I provide a PR that shows this problem with a modified bounding ball model (called BouncingBallStairs): #70
I also fixed this issue in #71
The expected behavior of the BouncingBallStairs model is as follows:
![expected_behavior](https://user-images.githubusercontent.com/871103/94010495-4f984880-fda6-11ea-85b5-398e8437a822.png)
Essentially, each time there's a bounce, the model schedules a time event for about 0.1s later.
The model also shows that, when an timed event happens at the same time as a state event, it can happen that the state event is not longer handled. That is, if the ball collides with the floor (the importer detects a zero crossing), but the floor moves, then the ball will no longer collide with the floor.
The behavior obtained from #70 is the incorrect one:
![bad_behavior](https://user-images.githubusercontent.com/871103/94010995-fc72c580-fda6-11ea-8c52-d1a4be953110.png)
The text was updated successfully, but these errors were encountered: