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 new version of LazySets #214

Merged
merged 1 commit into from
Jan 7, 2024
Merged

Support new version of LazySets #214

merged 1 commit into from
Jan 7, 2024

Conversation

schillic
Copy link
Contributor

@schillic schillic commented Jan 5, 2024

Closes #211.
Closes #213.

@mykelk mykelk merged commit 9802458 into sisl:master Jan 7, 2024
2 checks passed
@mykelk
Copy link
Member

mykelk commented Jan 7, 2024

Thanks! I merged because it looks like the tests were passing on this PR, but it looks like after the merge we have this:

image

@schillic
Copy link
Contributor Author

schillic commented Jan 7, 2024

To me this is not concerning. I believe this just means that some LP problem is numerically tricky. We have seen such warnings in LazySets for years, also in some of the unit tests. In principle we just pass on the constraints from the user to the LP solver, so it is less likely that there is something wrong on our end. The results are still correct since the tests pass.

@mykelk
Copy link
Member

mykelk commented Jan 7, 2024

Ah okay... I saw the two broken tests listed there. Shall we tag a 0.1.1 release then?

@schillic
Copy link
Contributor Author

schillic commented Jan 7, 2024

Ah, you meant those. They were broken before. I did not touch the tests.
I leave the tagging decision to you 👍

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.

Ai2h and VPolytope construction install issue
2 participants