-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
A lot of polytope constructors are broken #18213
Comments
This comment has been minimized.
This comment has been minimized.
Author: Vincent Delecroix |
comment:3
I have a big commit to push in few minutes... |
New commits:
|
Branch: u/vdelecroix/18123 |
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:5
Depends on #18211? |
Dependencies: #18211 |
comment:6
Replying to @nathanncohen:
Yes New commits:
|
Changed branch from u/vdelecroix/18123 to u/vdelecroix/18213 |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:11
The |
comment:12
Replying to @jdemeyer:
Right. The problem of embedding should be done elsewhere (my version embedds in |
comment:13
Replying to @videlec:
Here is one reason. The generator name of
The answer |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:35
|
comment:36
Replying to @nathanncohen:
Yes! This is very sad... But you have to be careful about what it means. There is the combinatorial automorphism group and the isometry group. I have no idea how to implement the latter efficiently. |
comment:37
Most probably the ugliest thing I ever saw
|
comment:38
HMmmmmmmm... I don't exactly know what the isometry group is, but let's try anyway: what about defining a complete graph on your points, in which each edge has a color associated to its length. Wouldn't the automorphism group of that be what you want? |
comment:39
Okayyyyyyyyyyyyyy. End of the review. Nothing else to add Very good job. This code needed to be cleaned, and it is much better now. But please, next time: smaller patches. You waste your reviewers' health Nathann |
comment:40
Replying to @nathanncohen:
That is a valid definition. But the standard one is the set of orthogonal matrices that preserve the polyhedron. And it would be nice for |
comment:42
Patchbot should be happy after that. |
comment:43
Some broken doctests in the patchbot's report. Also, can you be sure that the Nathann |
comment:44
Hmmmmmm.. I can't seem to find on google an implementation of an isometry group function anywhere |
comment:45
Hi Vincent and Nathann Just a quick comment, as I'm not sure how useful this will be for general polyhedra: There is a method for lattice polytopes: Cheers, |
comment:48
Replying to @nathanncohen:
I don't know... Patchbot did not complain about this. |
comment:50
Okayyyyyyy. Then Nathann |
Reviewer: Nathann Cohen |
Changed branch from u/vdelecroix/18213 to |
A lot of polytopes constructors in
sage.geometry.polyhedron.library
. For examplegreat_rhombicuboctahedron
is defined overQQ
but it should be defined overQQ[sqrt(2)]
! There are in two places rough approximation of sqrt(2) in the codeInstead, we should use the
base_ring
argument (with appropriate defaults) and usebase_ring(2).sqrt()
instead.Polytopes
:Polytopes.orthonormal_1
,Polytopes.project_1
will be renamed respectivelyzero_sum_projection
andproject_points
Polytopes._pfunc
is just removedWhile we're at it, remove the deprecations from #11634.
During the process I discovered two annoying bugs:
Moreover, we can get a great speed up with the following because many polytopes have now coordinates in a quadratic number fields:
_mpfr_
method on quadratic number field elementsDepends on #18211
CC: @nathanncohen
Component: geometry
Author: Vincent Delecroix
Branch/Commit:
a58da00
Reviewer: Nathann Cohen
Issue created by migration from https://trac.sagemath.org/ticket/18213
The text was updated successfully, but these errors were encountered: