-
Notifications
You must be signed in to change notification settings - Fork 156
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
the meaning of neighborhood_limits #224
Comments
You definitely can. The calibration function is here to simplify the parameter tuning by choosing an appropriate value depending on the point density. But you can set it yourself absolutely. |
Thanks for your reply! One more thing, could you explain why the calibration function needs the 90% of the neighborhoods remain untouched ? I don't understand. |
It does not "need" it. It is just a value you can decide for yourself. In my experiments, I noticed this was a good value as it already reduced the computations by a lot, while not losing any performance |
Thanks for your reply! |
Hello, HuguesTHOMAS.
Thanks for your amazing work! In every calibration function of all the sampler classes, you remarked that:
Neighbors calibration: Set the "neighborhood_limits" (the maximum number of neighbors allowed in convolutions)
so that 90% of the neighborhoods remain untouched. There is a limit for each layer.
I'dont understand why some parts of the neighborhood points should remain untouched. And I want to use the KPConv module in my experiment and try to build a simpler dataloader, I'm wandering that whether it necessary to add a calibration function to gain the batch_limit and neighborhood_limits or I could just set the batch_num and neighborhood_num fixed with fixing number of downsampled points.
The text was updated successfully, but these errors were encountered: