-
Notifications
You must be signed in to change notification settings - Fork 132
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
Grids for 2D data #127
Comments
Hi @LouisSerrano ! Coordinates we feed to interpolation in wisp are in For 2D data - what's your intended use for acceleration structures? They're indeed optimized with 3D coordinates in mind, but one idea is to always pass |
Well, actually I am trying to find a way to obtain through an INR local embedding features of a physical field. I am not per se looking for faster but smarter architectures, and I was interested in trying an idea with the grids available in kaolin-wisp. Usually I work with SIREN or classical INRs that take as inputs global coordinates, and they struggle to fit multi scale signals (which is my case). Therefore I think local embeddings may help to better capture the nature of the signal. |
Hi, I would like to use the acceleration structures of kaolin-wisp for 2D data (180 000 points per sample). What do I need to change in the pipeline to make it work ? Everything seems to be designed (especially the grid classes) for 3D point clouds, but I am not sure.
Also in what range should be the coordinates so that the grid interpolation makes sense ?
The text was updated successfully, but these errors were encountered: