Fix last_pose bug in nuscenes_converter.py #244
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for this amazing work! I got into a little trouble when reading can_bus data using
nuscenes_converter.py
.After I checked, I noticed that there was a small bug in this script.
as you can see , the
vel
,velocity
androtation_rate
are one frame laggingHowever , you will find that the raw data in
nuscenes/can_bus/scene-0003_pose.json
looks like this:the
pos
andorientation
come from the former, but the rest of them come from the latter.I assume that this won't be a big problem since those two frames are quite close.