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.

Sign up for GitHub

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

Jump to bottom

Clean up leaky interface that requires discrete_time_problem to know about time freezing. #117

Open
apozharski opened this issue Aug 6, 2024 · 1 comment
Open

Clean up leaky interface that requires discrete_time_problem to know about time freezing. #117

apozharski opened this issue Aug 6, 2024 · 1 comment

Comments

@apozharski
Copy link
Member

Currently Stewart and Heaviside problems use Options.time_freezing to identify a physical time state. This makes the resulting implementation confusing. A possible solution to this is just adding a new option that specifies the existence of a physical time state.
@apozharski apozharski mentioned this issue Aug 6, 2024
Merged
@nurkanovic
Copy link
Member

I agree. And the default is of course that the clock state does not exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@apozharski @nurkanovic