Changes between Version 14 and Version 17 of Ticket #31799


Ignore:
Timestamp:
05/26/21 06:34:22 (8 months ago)
Author:
mkoeppe
Comment:

New commits:

05fef94src/sage/geometry/polyhedron/constructor.py: Add more constructors
624ec2bMerge #26366
789eadaCombinatorialPolyhedron.as_polyhedron: New

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31799

    • Property Commit changed from to 789eadafc5807c003ccf7f8b0611b68760da2d3a
    • Property Dependencies changed from #31823 to #31823, #26366
    • Property Branch changed from to u/mkoeppe/from_combinatorialpolyhedron_and_h_representation_to_polyhedron__with_double_description_
  • Ticket #31799 – Description

    v14 v17  
    1 Given an (abstract) `CombinatorialPolyhedron` such that **at least one** of H-representation and V-representation are labeled geometrically, we should be able to efficiently build a polyhedron -- or raise an error if the data are inconsistent.
     1Given an (abstract) `CombinatorialPolyhedron` such that **at least one** of H-representation and V-representation are labeled geometrically, the new method `CombinatorialPolyhedron.as_polyhedron` constructs a geometric polyhedron.
     2
     3If `check=True` (default), it checks that the result is OK.
     4
     5We should be able to efficiently build a polyhedron, avoiding to run the double description method when setting up the polyhedron, for the backends that accept double description input:
     6 - if both representations are geometric, just pass them to the polyhedron constructor (#26366)
     7 - if only one representation is geometric, reconstruct the other one from the incidences by equation solving.
    28
    39Ideally, an optional argument `allow_degeneration` would allow that the given representation data actually gives a degeneration of the given combinatorial polyhedron.