Hi, I had not noticed that Polyhedron created a Poset, and if so that 'makes > sense'. I had the same problem with both classes: it makes it very hard to > create a lot of Polyhedron objects, or many posets (and this, in turns, > makes it hard to write a routine that enumerates posets up to isomorphism) > :-/ >
Yes, this is really bad. At the time, I had to create loads of relatively small polyhedral cones and discard them but the computation was hitting the RAM limit way too fast. Is the related poset problem really difficult to fix? I believe that trying to have a workaround for polyhedron to avoid the usage of the face lattice is 1) a lot of work 2) not clear how fast it could be Of course, once the face lattice is computed many combinatorial data is stored there, so it's logic to use this data structure. So a workaround is not really ideal anyway. JP -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
