-
-
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
Set up permutahedron with both Vrep and Hrep (if backend supports it) #29325
Comments
Commit: |
Branch: public/29325 |
comment:2
Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date. |
Changed branch from public/29325 to public/29325-reb2 |
Reviewer: Jean-Philippe Labbé |
comment:4
These timings are interesting. Perhaps it would be good to add them to the documentation of the function? Since the backend |
Changed branch from public/29325-reb2 to public/29325-reb3 |
comment:6
Failing doctests, see patchbot:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
As for the bad exit it appears that memory consumption is highly unstable during doctesting. I guess I just mark it as not tested. The examples are more for documentation than for testing. New commits:
|
comment:10
"not tested" seems like the right choice for this. |
comment:11
Needs rebase |
Changed branch from public/29325-reb3 to public/29325-reb4 |
comment:14
these doctests that seem to depend on an unspecified order of enumeration... is there not a better way of testing this, for example by sorting...? |
comment:15
There is only a few doctests that can be fixed by sorting. The face iterator really behaves different with different order and the indices are all shuffled. |
comment:16
And the first ones cannot be fixed by this either. Looks like |
Changed reviewer from Jean-Philippe Labbé to Jean-Philippe Labbé, Matthias Koeppe |
comment:18
Ok then |
comment:19
Thank you. |
Changed branch from public/29325-reb4 to |
We set up the permutahedron with both Vrepresenation and Hrepresentation, if the backend supports it.
If the backend supports precomputed data (currently
field
) this is much faster. Otherwise, this is a bit faster, as the Hrepresentation seems to be the better choice.Before this ticket:
With this ticket:
Note that
field
is much slower thanppl
before this ticket and the timings are therefore omitted.As the order of Vrepresentation and Hrepresentation changes, a lot of tests need to be fixed.
CC: @jplab @LaisRast
Component: geometry
Keywords: polytopes, precomputed data, permutahedron
Author: Jonathan Kliem
Branch/Commit:
577e736
Reviewer: Jean-Philippe Labbé, Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/29325
The text was updated successfully, but these errors were encountered: