-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
Improved input output for backend polymake #31864
Comments
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:4
I think it would be better to call |
comment:5
Good point. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
Is #31866 a dependency now? |
Changed branch from u/gh-kliem/polymake_input_output to u/gh-kliem/polymake_input_output2 |
Reviewer: Matthias Koeppe |
comment:10
This is a very nice improvement. |
comment:11
Thank you. Sometimes it is surprising what the bottle neck of a calculation is. |
Changed branch from u/gh-kliem/polymake_input_output2 to |
From #26368.
The interface to polymake seems to have a significant delay. For input, we can avoid it, as polymake accepts nested lists of integers, rationals, floats.
For output we can avoid it, as at least for matrices and vectors, we can just parse the representation string.
Before:
After:
Depends on #27745
CC: @mkoeppe
Component: geometry
Keywords: polymake, input, output
Author: Jonathan Kliem
Branch/Commit:
e6fef55
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/31864
The text was updated successfully, but these errors were encountered: