3D bounding box support for tracking benchmark #43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reimplements tracking parser so that all object data is returned, including 3D bounding box information, as a namedtuple. Updated _load_calib so that only calibration data which is available for tracking is returned. Removed references to cam0 and cam1 (grayscale) since these are not provided as part of the tracking benchmark.
Fixes utiasSTARS#31 due to the lack of leading ':' in tracking calibration files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi there, I've been using pykitti for working with the tracking dataset and have made some modifications to allow it to load the full set of tracklet object information (3D bounding boxes etc.). I'm also hoping to add support for the object benchmark. Would this be of interest? Apologies if this is already being addressed by PR #28, happy to contribute to that instead if it is still active.