Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Time events are not handled in model exchange example (listed on the standard doc) #72

Closed
clagms opened this issue Sep 23, 2020 · 0 comments

Comments

@clagms
Copy link
Collaborator

clagms commented Sep 23, 2020

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants