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

Support irregular time-step in Runge-Kutta integration #60

Open
frothga opened this issue Mar 15, 2018 · 0 comments
Open

Support irregular time-step in Runge-Kutta integration #60

frothga opened this issue Mar 15, 2018 · 0 comments
Labels

Comments

@frothga
Copy link
Collaborator

frothga commented Mar 15, 2018

A part which is queued to execute at a given interval may also receive (say) spike events which cause it to integrate the time between its last regular cycle and the time of the event. This means that when the next cycle time comes up, not all the parts necessarily have the same starting time for integration. When this occurs, then amount of integration time should be part-specific.

This is simple to implement with Euler integration, because it only considers last and current time. However, Runge-Kutta considers multiple time point between last and current. A possible solution is to pass current time and a value in [0,1] to indicate proportion of period.

@frothga frothga added the bug label Mar 15, 2018
@frothga frothga changed the title Internal & C: Handle different integration periods in the same time-step Support irregular time-step in Runge-Kutta integration Mar 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant