Meta-ticket: Set up polyhedra with both Vrep and Hrep #29199
Description
With #28880 at hand, it makes sense to set up polyhedra from both Vrepresentation and Hrepresentation, if the backend supports it.
This is faster an any case, if the backend supports precomputed data (currently only field, but polymake and normaliz potentially can do that as well). Otherwise it might be faster, as it chooses the shorter representation by default. E.g.
- setting up a hypercube is then done by inequalities instead of vertices,
- translating a hypercube should be done by inequalities not by vertices.
This ticket collects all those instances, where we will set up the polyhedron from both Vrep and Hrep:
- From the library:
- Polyhedral constructions:
- Obtain polar with both Vrep and Hrep (if backend supports it) #29569: polar,
- Obtain product with both Vrep and Hrep (if backend supports it) #29583: product,
- Set up join with both Vrepresentation and Hrepresentation #33653: join,
- Set up linear transformation with precomputed data if injective #29843: affine hull, linear transformation
- Dilation of polyhedron with both Vrep and Hrep (if backend supports it) #29200: dilation,
- Translation with both Vrep and Hrep #29324: translation,
- Set up prism with both Vrep and Hrep #32150: prism,
- Set up bipyramid with both Vrep and Hrep #32151: pyramid,
- Set up pyramid with both Vrep and Hrep #32152: bipyramid.
- PolyhedronFace.as_polyhedron: Provide double description to backends that support it #31801:
PolyhedronFace.as_polyhedron
Component: geometry
Issue created by migration from https://trac.sagemath.org/ticket/29199