-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
backend_polymake for Polyhedron #22683
Comments
comment:2
As preparation, I have implemented the Last 10 new commits:
|
Commit: |
Dependencies: #22658 |
Author: Matthias Koeppe |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
Two things I see:
Otherwise LGTM modulo the dependency. |
Reviewer: Travis Scrimshaw |
comment:10
Thank you. |
comment:11
Thanks for reviewing! |
comment:12
Not a problem; happy to help. |
comment:13
I suspect this will pass tests on the bots with stand-alone sage. It gives me trouble in sage-on-gentoo while building the documentation, I am not sure how other distros deal with the doc building. I have the following failure related to this ticket
which itself comes from #22630. Volker is currently testing the ticket so don't touch it now. If it is accepted as is, could we have a follow up to import |
comment:14
|
comment:15
Replying to @tscrim:
This, here, ticket. I am signaling because I need to keep track of these things but I don't want to stop normal progress. Any issue I have, could be dealt with in a follow up ticket. Volker's already merged this ticket in his testing branch and if all goes well we shouldn't prevent the closing of this ticket because of sage-on-gentoo [OK, I would stop it if I thought you did something terrible]. |
comment:16
Follow-up ticket at #22740. |
comment:17
Documentation doesn't build |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:19
I've merged in #22740, which was intended to be a follow-up ticket, hoping that this will fix the doc build problems. |
comment:20
I would have been somewhat surprised if the doc did build on Volker's testing branch given comment:13. Changes LGTM. |
comment:21
Well, I would have thought you build your branch and the documentation. So, to me it was probably a problem on my side. |
comment:22
I didn't test it in conjunction with #22630 and didn't notice the conflict. |
Changed branch from u/mkoeppe/backend_polymake_for_polyhedron to |
Building upon #22658 (Support interface coercion
polymake(X)
forPolyhedron
), we provide a backend inbackend_polymake.py
that does allPolyhedron
computations using polymake (in particular, the initial computation of the double description).For quadratic field extensions of the rationals, this backend should be faster than the generic implementation in Python (unless the pexpect overhead dominates).
Depends on #22658
CC: @simon-king-jena @jplab @videlec @tscrim @yuan-zhou
Component: geometry
Author: Matthias Koeppe
Branch/Commit:
6d1774b
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/22683
The text was updated successfully, but these errors were encountered: