You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
We note some inconsistency in the data collection, and we are wondering if you could help us out.
In
map_utils.py
, thehero_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 outputwindow_xxx_surface
, which is 5 pixels per meter. This is shown by the following line.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.
The text was updated successfully, but these errors were encountered: