Long running time of M3C2 on entire point cloud compared to CloudCompare

[chrise96]

With the help of this git issue I'm able to run M3C2 algorithm with (I think) the same params used in CloudCompare. However, the M3C2 algorithm takes roughly 100x times longer than the implementation of CloudCompare.

Cloudcompare M3C2: ~2 seconds py4dgeo M3C2: 271 seconds

I put all the files to recreate the experiment here.

Is the time difference caused by a param that I forgot to configure in the py4dgeo implementation? Here is the config file (default settings exported from CloudCompare): m3c2_params.txt