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

Do not project automatically for :projection_matrix option #547

Merged
merged 1 commit into from
Mar 16, 2019

Conversation

schillic
Copy link
Member

No description provided.

@schillic schillic requested a review from mforets March 16, 2019 13:14
Copy link
Member

@mforets mforets left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking to delete the call to project inside post altogether, do it in the upper level solve! instead.

But maybe this is just fine, since projection is algorithm-specific in general (for example depends on the way the flowpipe is represented: e.g. if it consists of concrete zonotopes => i may want to use linear_map for the projection, instead of LinearMap -> overapproximate). A workaround is then to call project from solve! but allow algorithms to extend the function project for their use case.

@schillic
Copy link
Member Author

I do not propose to keep it here. We can still outsource later. But in any case we want to remove that disjunct.

@schillic schillic merged commit fe9bd10 into master Mar 16, 2019
@schillic schillic deleted the schillic/projection_matrix branch March 16, 2019 15:18
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

Successfully merging this pull request may close these issues.

2 participants