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

Potential Bug in BEV maps generation #31

Open
monghimng opened this issue Sep 12, 2020 · 0 comments
Open

Potential Bug in BEV maps generation #31

monghimng opened this issue Sep 12, 2020 · 0 comments

Comments

@monghimng
Copy link

We note some inconsistency in the data collection, and we are wondering if you could help us out.

In map_utils.py, the hero_xxx_surface are constructed bigger than the output size so that rotation would not cause loss of pixels. The resolution is constructed the same as the output window_xxx_surface, which is 5 pixels per meter. This is shown by the following line.

scaled_original_size = self.original_surface_size * (1.0 / 0.9)
self.hero_map_surface = pygame.Surface((scaled_original_size, scaled_original_size)).convert()

However, we notice during rotation,

rotated_map_surface = rz(self.hero_map_surface, angle, 0.9).convert()

There is a 0.9 shrinking. Wouldn't this cause the output to no longer have 5 pixels per meter resolution.

Thanks.

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

1 participant