Changes between Initial Version and Version 1 of Ticket #27063, comment 11


Ignore:
Timestamp:
09/01/19 10:23:49 (2 years ago)
Author:
jipilab
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #27063, comment 11

    initial v1  
    1111On the long run, `CombinatorialPolyhedron` will contain the bulk of codes that strictly makes use of combinatorial data and `Polyhedron_base` things that use the geometry.
    1212
    13 Further, concerning the present ticket, I believe it would make sense to make it a meta-ticket tracking each method and have 1 ticket per method.
     13Further, concerning the present ticket, I believe it would make sense to make it a preparation ticket. Then each method would have 1 ticket. This way the changes will be more manageable.
    1414
    1515Another open question: currently how is the relation between a `Polyhedron` object and a `CombinatorialPolyhedron` object? I guess that as of now, since the double description is computed by default, it is worth maybe creating the combinatorial counter part as an attribute and make it accessible via a method say named `.combinatorial_polyhedron`. This might make it easier to then transfer the computations to the combinatorial type.