-
Notifications
You must be signed in to change notification settings - Fork 87
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
Box
- Ball
intersection in 2D
#1165
Comments
We really need a FAQ for this. There are multiple issues closed about the same stack overflow. The pair Ball + Box is not implemented currently. What are you trying to achieve? |
Box
- Ball
intersection in 2D
If it's a known issue, would it be appropriate to add a warning in the documentation? I would like to generate a Cartesian grid of data points, and clip it using a ball. Ideally, the segments would be cut by the ball and turn the cartesian mesh into a "mostly cartesian" mesh, with some Quadrangles converted into other NGons by the intersection with the ball. Perhaps I'm approaching the problem completely wrong, I've only spent an afternoon with the package. |
That would be great, though I feel that people will continue opening issues on GitHub. The problem lies in the fact that we exploit the symmetry of the We tried to address this issue in the past, but the design became much more convoluted. We aborted the attempt. If you have a better suggestion that avoid code repetition, please feel free to submit a PR.
I think you can already achieve this if you convert the using Meshes
b = Ball((0, 0), 1)
# sample points on boundary
s = sample(boundary(b), HomogeneousSampling(10))
# approximate ball with polygon
p = PolyArea(collect(s)) The intersection between the Related discussion: #402 |
The documentation for
intersection
readsOne might then expect to be able to run
which results in a
StackOverflowError
.Perhaps "intersection" is not intended for this purpose?
The text was updated successfully, but these errors were encountered: