LiDAR segmentation for later classification || issues with dialogue box parameters

Dear All :)
are there any users here who, like me, appreciate good segmentation?
To be honest, the tool for this in GM has been giving me a headache for a long time. I don't find it intuitive, the results often don't correlate with my expectations, some of the values to be set have no meaning whatsoever.
I had tried to establish a new training tool in GM and based it on the capabilities of CloudCompare, but the subsequent implementation in GM25 was not successful and unfortunately not an improvement. It is really depressing for me to have this experience, because GM is a great piece of software in itself.
Can anyone give me any tips to improve the use of the segmentation tool? Of course I know the knowledgebase and I have already spent well over 100 hours with trial and error, but every “success” seems to be a fluke.
The example in the screenshot shows a cut through a ground surface and the “floating points” should be excluded, as well as tree trunks. However, trenches should remain as ground. It's quite simple: just follow the thick line. The values are just an example. I tried a lot of different ones already.
Thanks
Alex
Categories
- 12.9K All Categories
- 5.7K Features Discussion
- 346 Downloading Imagery
- 1.3K Elevation Data
- 385 Georeferencing Imagery Discussion
- 643 GM Script Language
- 54 User Scripts
- 115 GPS Features
- 419 Projection Questions
- 829 Raster Data
- 1.4K Vector Data
- 6.6K Support
- 179 Announcement and News
- 926 Bug Report
- 561 SDK
- 1.2K Suggestion Box
- 3.7K Technical Support
- 574 Other Discussion
- 132 GIS Data Sources
- 27 Global Mapper Showcase
- 241 How I use Global Mapper
- 108 Global Mapper Forum Website