-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
Check containment for combinatorial faces #31822
Comments
comment:3
It works fine in the intended case. However, it should raise an error, when |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
The pyflakes plugin complains that
Did you mean |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
comment:11
Thanks. |
comment:12
Nees rebase. |
comment:13
is repeated in the doctest. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:15
Replying to @yuan-zhou:
Using the face as a bitset is much much faster than creating a list. Well there would be a faster method for the second case by comparing directly the array instead of the list, but I don't think this case is very important anyway. Here is some speed comparison:
Even the very difficult first case (
Fixed. |
comment:16
Replying to @kliem:
If speed is a concern, then I'd recommend to check Does a face know about the original combinatorial polyhedron |
comment:17
If The other case is not really intended and I just have something that will work. However, if you want, I can do something more efficient. |
comment:18
Replying to @kliem:
If it's not too complicated to implement, this sounds like a great solution! I don't have a direct use case of "f1 and f2 not in the same mode", so I feel good about the ticket even if you won't implement the additional speed-up. However, I'd like to include the |
Reviewer: Yuan Zhou |
comment:20
Replying to @yuan-zhou:
The check Here are the new timings:
|
comment:21
Btw, currently However, this might be the more honest timing, as it reflects more realistic the amount of time the first call needs. |
comment:22
Caching
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from u/gh-kliem/is_subface_for_combinatorial_face to u/mkoeppe/is_subface_for_combinatorial_face |
comment:25
I am guessing that this ticket "needs review" Last 10 new commits:
|
Changed reviewer from Yuan Zhou to Yuan Zhou, Matthias Koeppe |
comment:26
I have not followed the discussion on timing, but the code looks fine to me, and passes tests. |
comment:27
Thank you. |
Changed branch from u/mkoeppe/is_subface_for_combinatorial_face to |
We add a method
is_subface
to combinatorial faces.Depends on #31819
CC: @jplab @mkoeppe @yuan-zhou
Component: geometry
Keywords: combinatorial polyhedron, subface
Author: Jonathan Kliem
Branch/Commit:
ac5c327
Reviewer: Yuan Zhou, Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/31822
The text was updated successfully, but these errors were encountered: