Region Growing can be quite long as it implies neighbor queries on
pretty much all data points: if the cluster_epsilon parameter is very
large, then these neighbor queries can take a very long time. But 5 days
still seem like a crazy runtime to me: are you sure you are compiling in
Release mode? CGAL can be very slow without the compiler optimizations.
Also, I would make some trials on a small subset first (and check if the
output is what you expect) to avoid wasting hours or computation.
Note that in the most recent version of CGAL (4.12 beta), a callback
mechanism was introduced in Region Growing so that the user can know the
advancement of the algorithm while it's running:
> Hi all,
> I am running Region_growing to detect only plane on a 3.7 Million point
> I just call using .detect() so it uses the default parameters.
> The detection function has been running for 5 days on single CPU and never
> (I dunno how to make it utilize my CPU resource as it does not have
> concurrent flag)
> Are there any possibilities that the .detect() function comes to a dead
> Or it is just taking very long time to end?
> Would that be parameters problem? like min_points?
> Any ways to make the algo run faster?
> Thank you very much.
> Sent from: http://cgal-discuss.949826.n4.nabble.com/ >