Closed bhyang closed 2 years ago
Thanks for reporting this. We will investigate it ASAP.
Ah! The bug here is that the named values are not working. In the pybind code there's a missing argument to the corresponding C++ function so instead of passing padding=0 you wind up passing a head_angle=0. Thank you for catching and reporting this! We've also added unit tests there so that this doesn't happen again.
We'll merge it shortly but the fix is here: https://github.com/facebookresearch/nocturne/pull/49
It is now merged and if you pull master this should be resolved. I'm closing this but feel free to re-open it if you find issues!
Operating system
Ubuntu 20.04
Bug description
Hi,
The description for the
visible_state
method inexamples/nocturne_functions.py
says that settingpadding=True
will add extra objects to the dict to hit the maximum number of objects for each type.So for the default scenario config (where max_visible_objects is 16) we'd expect
visible_dict['objects'].shape == (16,13)
.But if you set
padding=True
, you actually get(7,13)
. The original unpadded shape is(5,13)
.Additionally,
visible_dict['traffic_lights']
andvisible_dict['stop_signs']
have shapes(0,12)
and(0,3)
respectively whenpadding=True
even though the maxes are nonzero.The final shapes will also change depending on the vehicles and scenarios even when
padding=True
.If I'm misunderstanding the expected behavior, please let me know.
Thanks!
Steps to reproduce
Here's a short script that reproduces the issue (run the same as
examples/nocturne_functions.py
)Relevant log output
No response