-
-
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
Setting up a Polyhedron from both Vrep and Hrep - for backend='polymake' #26368
Comments
Dependencies: #28880 |
comment:2
#27745 has implemented this. |
comment:3
While #27745 has illustrated how to implement this, it does not implement a method This method is utilized when changing backends or when doing fully characterized constructions. |
comment:4
Good point. |
Branch: public/26368 |
Last 10 new commits:
|
Commit: |
comment:6
Before doing this, we should really optimize sage to polymake input/output, this is really awful:
Polymake vector to sage vector should be much much better. |
comment:7
Is it possible to see with a profiler where the time is spent? |
comment:8
Did this. Not much can be done about input. However output can really be accelerated. Everything is slow: Iterating, item fetching etc. However, just taking the representation and string operations seems to work well. I have a branch I can push in an hour or so. |
comment:9
Is it easy to see how much time is spent on the polymake side (in Perl and compiled polymake code) vs. on the Python side? |
comment:10
That is the ticket as is. I'm not exactly sure, why the method The input is slow as well, which does not suprise me, when forcing verbose things look like this:
Polymake also accepts input files etc. in interactive mode. So maybe we could utilize this. |
comment:11
I'm puzzled about this line:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Author: Jonathan Kliem |
comment:18
This seems to work well, thanks! |
Reviewer: Matthias Koeppe |
comment:19
Thank you. There is a problem with |
comment:20
Could you open a new ticket for this please? |
comment:21
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:23
Replying to @vbraun:
Merging in the updates from #27745 should resolve this (or raise a proper deprecation warning or something). In any case. |
comment:25
I think it's just that here
the |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:27
Replying to @mkoeppe:
Right. I wonder, when I will stop making this mistake ... |
Changed branch from public/26368 to |
Follow-up from #22701, where this was implemented for 'field'.
Before (with #31864):
After:
Also you can now change backends to polymake quickly:
Depends on #27745
Depends on #31864
CC: @jplab @simon-king-jena @kliem @videlec
Component: geometry
Author: Jonathan Kliem
Branch/Commit:
82020ef
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/26368
The text was updated successfully, but these errors were encountered: