-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Polyhedron(backend='number_field') #34479
Comments
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
Author: Matthias Koeppe, ... |
This comment has been minimized.
This comment has been minimized.
Dependencies: #34195 |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
My workaround is elif backend == 'polymake':
base_field = base_ring.fraction_field()
try:
- from sage.interfaces.polymake import polymake
+ from sage.interfaces.polymake import polymake, PolymakeElement
polymake_base_field = polymake(base_field)
+ assert isinstance(polymake_base_field, PolymakeElement) # to muffle pyflakes
except TypeError: |
comment:11
Thanks for catching this. This is actually from #34195 |
Changed branch from u/mkoeppe/polyhedron_backend__number_field__ to u/yzh/polyhedron_backend__number_field__ |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed author from Matthias Koeppe, ... to Matthias Koeppe, Yuan Zhou |
comment:15
Probably |
comment:16
Also this new parameter should probably not be called That we use a number field for the computation is specific to the new subclass |
Changed branch from u/yzh/polyhedron_backend__number_field__ to u/mkoeppe/polyhedron_backend__number_field__ |
New commits:
|
comment:19
How about renaming it to
|
comment:20
Sounds good. I notice that Replying to Matthias Köppe:
|
comment:21
Replying to Yuan Zhou:
Sounds good |
comment:22
Replying to Yuan Zhou:
Probably a good idea to rename it too |
Changed branch from u/mkoeppe/polyhedron_backend__number_field__ to u/yzh/polyhedron_backend__number_field__ |
comment:24
Renamed. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from u/yzh/polyhedron_backend__number_field__ to u/mkoeppe/polyhedron_backend__number_field__ |
comment:27
This works well New commits:
|
Reviewer: ..., 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:31
I would be happy to mark it as a positive review once the patchbot comes back green. If anyone has any objections before that, please do so. |
Changed reviewer from ..., Matthias Koeppe to Matthias Koeppe, Travis Scrimshaw |
comment:33
All green, Lint failures unrelated. |
Changed branch from u/mkoeppe/polyhedron_backend__number_field__ to |
(from #33752)
We lift the conversion code that sends symbolic and AA elements to a suitable embedded number field and back from the backend
normaliz
and create a new backendnumber_field
, which just runs backendfield
on the converted number field elements.This results in rather general (but slow) polyhedral code for algebraic data in pure Python.
Depends on #34195
CC: @yuan-zhou @kliem @jplab @videlec @tscrim
Component: geometry
Author: Matthias Koeppe, Yuan Zhou
Branch/Commit:
c729884
Reviewer: Matthias Koeppe, Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/34479
The text was updated successfully, but these errors were encountered: