Closed jhpalmieri closed 5 years ago
Two additional things; everything else LGTM.
return tuple(self._vertex_to_index.keys())
is better as return tuple(self._vertex_to_index)
product
, is there some way we can avoid creating two simplicial complexes? I imagine it is slower to do it twice. Why not for the first case return the simplicial complex and for the second use the facets
?Replying to @tscrim:
Two additional things; everything else LGTM.
return tuple(self._vertex_to_index.keys())
is better asreturn tuple(self._vertex_to_index)
Sure, sounds good.
- In
product
, is there some way we can avoid creating two simplicial complexes? I imagine it is slower to do it twice. Why not for the first case return the simplicial complex and for the second use thefacets
?
Yes. I think when I first wrote this, I was going to use something produced by the __init__
method and so I was constructing the simplicial complex to avoid code duplication. That doesn't seem to be the case any more, so you're right, I can just use facets
in the second case.
Branch pushed to git repo; I updated commit sha1. New commits:
3da1d0f | trac 26966: following reviewer suggestions to simplify a little code. |
Thanks.
Reviewer: Jeroen Demeyer, Travis Scrimshaw
Great, thanks for reviewing!
Changed branch from u/jhpalmieri/sorting-simplicial-complexes to 3da1d0f
With Python 3, before #26931:
After #26931:
After this branch:
Component: python3
Author: John Palmieri
Branch/Commit:
3da1d0f
Reviewer: Jeroen Demeyer, Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/26966