-
Notifications
You must be signed in to change notification settings - Fork 40
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
Problem and questions about LineArrangement #39
Comments
Thanks for your interest in hgeometry, and sorry for the late reply.
a) build the arrangement of the supportinlines of the segments, and mark the edges that are part of the original input segments (note that this may blow up the space requirement, i.e. it produces an arrangement of O(n^2) size, whereas maybe the segments did not intersect at all, so could have been stored in O(n) space) b) To build the arrangement of segments you essentially need 2 things; to find the intersections and to build the planar subdivision (after "splitting" segments at intersections). Both these indiviual parts have been implemented. But they still need to be combined. |
I am currently trying to port some code I played with from Python that used CGAL bindings to Haskell and it looks like HGeometry has the algorithms I need, which are computing Line Arrangements and Convex Hulls.
Now this ends with an error "link: fromJust" when evaluating _unboundedIntersections in GHCI.
Am I doing something wrong or is this a bug? I would have expected to get an arrangement that in some way contains the 4 triangles inside the box.
What would be the easiest way to extract the polygons (as sequence of points) of the arrangement?
With the CGAL bindings I could use line segments for arrangements. It does not look to me that this is possible with HGeometry yet, is this correct? Should I just use constructArrangementInBox with a sufficiently tight box that excludes intersections outside of the regions that I care for, as a workaround for the lacking support for segments?
Thanks in advance!
The text was updated successfully, but these errors were encountered: