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

Workaround for analyzing properties in appropriate dimension #524

Closed
wants to merge 3 commits into from

Conversation

schillic
Copy link
Member

@schillic schillic commented Mar 7, 2019

This is a workaround until #521 gets in.

The branch is based on #523.

@mforets
Copy link
Member

mforets commented Mar 7, 2019

For the record i have tried it and this idea works; the workaround is to provide the property in the reduced dimension (for example if n=48 and :vars => [25] then a linear constraint property is defined in one spatial dimension.

While in #525 we keep the property in high dimensions and call LazySets project method to do the "concrete projection". Note that if the concrete projection happens to not be implemented then it will throw an error. Hence, only halfspace and hpolyhedron sets are supported in the properties, at the moment.

@mforets mforets closed this Mar 7, 2019
@schillic schillic deleted the schillic/521 branch March 7, 2019 19:28
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