I do a lot of Segment->Process->Merge operations, which I expect everyone does.
I've found that as I progress, more noticeably with larger clouds (100M+), the response of CC while drawing segmentation contours and performing the actual segmentation decreases. For example, creating a 20 vertex segmentation area in a 30M point cloud is instantaneous and performing the segmentation takes about 3 seconds at the beginning of a session. A few hours later I might have to wait 10 seconds to even see the results from clicking a segmentation point and I can make lunch while waiting for the segmentation to happen.
Of course I can always save my work to disk and restart CC but I may have 20 clouds segmented out of the original by that time.
On a related note, occasionally the toolbar doesn't come back after a segmentation completes and is waiting for you to click the check or the X. Clicking on the title bar of the CC window brings it back.
Decreasing Segmentation Performance
Re: Decreasing Segmentation Performance
Hi,
What version are you using? Because there was an issue with the 2.6.1 (due to Qt 5 --> we downgraded to Qt 4 for the next version). And there was another glitch when a GL shader is activated (e.g. EDL).
Can you try with the latest beta version maybe? (2.6.3.beta)
What version are you using? Because there was an issue with the 2.6.1 (due to Qt 5 --> we downgraded to Qt 4 for the next version). And there was another glitch when a GL shader is activated (e.g. EDL).
Can you try with the latest beta version maybe? (2.6.3.beta)
Daniel, CloudCompare admin
Re: Decreasing Segmentation Performance
Sorry, but the problem remains in the Beta too.
Re: Decreasing Segmentation Performance
Luca just found the problem.
The github code repository is fixed. And I'll update the beta version as soon as possible (probably at the very beginning of 2016!).
The github code repository is fixed. And I'll update the beta version as soon as possible (probably at the very beginning of 2016!).
Daniel, CloudCompare admin
Re: Decreasing Segmentation Performance
That's excellent!
Was it a memory leak? I've found if I push my luck too far, CC just crashes, which seems to point to a leak.
Was it a memory leak? I've found if I push my luck too far, CC just crashes, which seems to point to a leak.
Re: Decreasing Segmentation Performance
Nope the issue that each routine was called as many times as you had started the segmentation tool.
And regarding the crash it may be due to another bug I recently created (when trying to fix another one ;). We will have to wait for the new beta to settle things.
And regarding the crash it may be due to another bug I recently created (when trying to fix another one ;). We will have to wait for the new beta to settle things.
Daniel, CloudCompare admin
Re: Decreasing Segmentation Performance
The newest beta fixes these problems completely.
Thanks!
Thanks!