-
Notifications
You must be signed in to change notification settings - Fork 80
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
Inputs into PolarNet #12
Comments
|
Thanks for your clarifications, @edwardzhou130! Why do you choose to input so many variations of spatial representation ( |
Hi @polars05 , Thanks for asking and very insightful questions. Also, you can replace |
Hi @YangZhang4065, it was a very interesting paper, and hence my curiosity / questions 😄 To clarify that my understanding of Is so, why not convert the points and grid to polar coordinates first, and then use the residual distances in the polar space instead? |
@polars05, sorry for the confusion caused by the name. I used the same name PolarSeg/dataloader/dataset.py Lines 239 to 247 in 73488e8
|
Thanks for clarifying my confusion! And residual distances refer to the l1, l2, l3, etc. in my above diagram? |
PolarNet seems to take in a 9-dimensional feature vector as an input; could you clarify what these 9 features are?
Based on
spherical_dataset
in./dataloader/dataset.py
, my guesses are --return_xyz
: (3 features)[**not too sure what this is**]
xyz_pol
: (3 features) original x, y and z coordinates converted to radius, angle and z, size[num_points, grid_size_r, grid_size_theta, grid_size_z]
xy
: (2 features) original x and y coordinates, size[num_points, 3]
sig
: (1 feature) reflectance, size[num_points, 1]
Are my guesses correct / wrong? Thanks!
The text was updated successfully, but these errors were encountered: