FeatureRequest: Debug output for long running jobs

Follow

michael.cieslik

• July 22, 2020 17:10

I have experienced very good performance of the software, when beginning with work. The more information the user and algorithm inputs into the scene, the faster the calculations should get.

 

In my case the opposite is the case. The more connection points the model gets, and the more iterations I run through - to fine tune the model and give hints to features -, the slower the calculations get.

I get more and more the feeling the algorithm gets stuck in a local loop, and I would like to see, what the program is doing for hours. And then give you hints, how to optimize the calculations that scale with the number of inputs and iterations.

 

0

• 

  Erik Kubiňan CR

  • July 23, 2020 06:33

  In this case, the behaviour actually is normal. By adding control points you're letting the software reconsider it's decisions and "think more" about certain places in the point cloud. If you wish to optimise the process and make it shorter, you should change the settings to easier values. 

  0

  Comment actions Permalink

Please sign in to leave a comment.