Skip to content
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

Possible pathological case for lmfauto() #20

Open
max-mapper opened this issue Dec 6, 2023 · 3 comments
Open

Possible pathological case for lmfauto() #20

max-mapper opened this issue Dec 6, 2023 · 3 comments

Comments

@max-mapper
Copy link

max-mapper commented Dec 6, 2023

I was playing with lmfauto() and have a file where it takes about 45 minutes to complete find_trees on a 32 core machine, sharing in case it's useful, if not feel free to ignore.

library(lidR)
library(lidRplugins)
las = readLAS("L4_6624_1947.las")
ttops <- find_trees(las, lmfauto(hmin = 100))

https://drive.google.com/file/d/1ZgZHoOZ49uBkREvzDjruj3uWQagFsyLM/view?usp=sharing

@Jean-Romain Jean-Romain reopened this Dec 6, 2023
@Jean-Romain
Copy link
Owner

Jean-Romain commented Dec 6, 2023

Does regular lmf works as usual ?

@max-mapper
Copy link
Author

Yes

# finished in about 5 minutes
ttops <- find_trees(las, lmf(ws = 2))
Local maximum filter: [==================================================] 100% (4 threads)

# after 10 minutes...
> ttops <- find_trees(las, lmfauto())
Local maximum filter: [--------------------------------------------------] 1% (4 threads)s)

Maybe what is happening is a large ws is being selected?

@Jean-Romain
Copy link
Owner

I have a lot of stuff to deal with these days. I'll try to investigate within a week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants