-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix #580 + related test #581
Conversation
Thanks Thomas! I think I would move the logic of this to What do you think? |
Yes, makes more sense the way you say, on it. |
xgi/core/simplicialcomplex.py
Outdated
supfaces_ids = self._supfaces_id(self._edge[id]) | ||
for sup_id in supfaces_ids: | ||
self._remove_simplex_id(sup_id) | ||
self.remove_simplex_id(sup_id) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't this was wrong before so I wouldn't touch it, unless you think it's more efficient?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch, thx
Co-authored-by: Maxime Lucas <maximelucas@users.noreply.github.com>
Co-authored-by: Maxime Lucas <maximelucas@users.noreply.github.com>
* feat: function + test * style: formatted with black * fix: iteration over orders * fix: removed iteration across orders * test: added test for k=0, related to #581 * style: black * docs: added explanation + link to ref * docs: rephrased definition * moved function to `convert.simplex` + created file for test * added k_skeleton to api rst file * use `max_edge_order` function * created cut_to_order + modified k_skeleton + tests * added cut_to_order to api * style: black * minor change for consistency with other functions * modified recipe * changed formatting in the recipe
fixes #580