Skip to content
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

Where do the values in arch_cfg.yaml file come from, especially fov_up, fov_down, img_means, img_stds? #97

Closed
finnSartoris opened this issue Dec 13, 2021 · 4 comments

Comments

@finnSartoris
Copy link

Where do the values fov_up=3, fov_down=-25 and img_means and img_stds in arch_cfg.yaml file come from?
Since I currently have a model applied to the SemanticKitti dataset that uses these values and now want to apply it to another dataset, I am trying to figure out if I can reuse these values.
Are these values only dependent on the scanner that is used? So if a scanner of the same type (here: Velodyne HDL64) was used, are the above values also the same or what do these values depend on?
Thanks a lot!

@jbehley
Copy link
Member

jbehley commented Dec 13, 2021

The fov_up and fov_down are sensor-specific and are the field of view of the Velodyne HDL-64E. The img_mean and img_stds are computed from the range images. As noted in #43, these values are computed on the training data. However, it's somehow lost how these values are exactly are computed.

And I guess this question is more related to lidar-bonnetal?

@finnSartoris
Copy link
Author

Thanks for the quick reply, helps me a lot! Yes that's right, this issue is more related to lidar-bonnetal.
Does signal mean the remission of a point or what does the value for signal in img_means and img_std stand for?

@jbehley jbehley transferred this issue from PRBonn/semantic-kitti-api Dec 14, 2021
@jbehley
Copy link
Member

jbehley commented Dec 14, 2021

signal is the remission of the sensor.

@jbehley jbehley closed this as completed Dec 14, 2021
@jbehley jbehley reopened this Dec 14, 2021
@finnSartoris
Copy link
Author

Great. Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants