-
Notifications
You must be signed in to change notification settings - Fork 28
-
Notifications
You must be signed in to change notification settings - Fork 28
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
revamp/replace pointsinside #353
Comments
Just to note that the example above |
Could also add a method for contains_points.ashape3d<-function(obj, points, ...) {
alphashape3d::inashape3d(obj, points=xyzmatrix(points), ...)
} |
contains_points.mesh3d <- function(obj, points, ...) {
xyz=xyzmatrix(points)
inbb=contains_points(boundingbox(obj), xyz, ...)
iosurf=pointsinside(xyz[inbb,,drop=F], surf = obj, ...)
res=inbb
res[inbb]=iosurf
res
} |
Initial work on https://github.com/jefferis/nat/tree/feature/improve-pointsinside (see ac15aa9) |
@fmlove this issue will be of interest |
jefferis
added a commit
that referenced
this issue
May 21, 2018
* a good start at #353 * feature/improve-pointsinside: Document new pointsinside behaviour Initial work accelerating/hardening pointsinside
closed by 3362ad8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Still having problems with
pointsinside
.pns.lh includes a lot of stuff outside the LH for some reason – only things that are distant though.
One option, given below would be to use a bounding box check to speed up computation as well as rejecting distant points.
The text was updated successfully, but these errors were encountered: