-
Notifications
You must be signed in to change notification settings - Fork 42
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
Paper/implementation mismatch? #31
Comments
Side note: I think that part can be simplified to something like the following pseudocode.
This matches Algorithm 5.2 (step 7) more closely. |
Hmm. This is indeed weird. I don't know why I wrote it like that 😂 Probably I came up with some wrong idea, tested it, figured out I was wrong, so corrected the code but in a stupid way, and also forgot to rewrite the paper. Thanks a lot for catching this!! I'll correct it right away. |
Thanks again, it's fixed now. |
(section 5.1.6, page 21)
If I understand this correctly, the condition of the left endpoint being excluded or x not being an integer is enough to say that the intersection in question is empty, and the parity doesn't need to be checked.
However, the algorithm implementation seems to disagree:
In fact, the comments explicitly state that checking parity is required. From quick testing it seems that the code is right here.
The text was updated successfully, but these errors were encountered: