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

monitor condition number of Polytope #3

Open
johnyf opened this issue Apr 9, 2014 · 1 comment
Open

monitor condition number of Polytope #3

johnyf opened this issue Apr 9, 2014 · 1 comment

Comments

@johnyf
Copy link
Member

johnyf commented Apr 9, 2014

To make the user aware of how bad ill-conditioning is in their problem, a quick search leads, e.g., to this paper.

@slivingston
Copy link
Member

Can you make this issue more specific? E.g., are there specific motivating examples that new features should address? E.g., as a feature, would this be a package-wide flag that is fixed at time of importing polytope that would cause functions to fail in the midst of a computation if intermediate values are deemed to be badly ill-conditioned?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants