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.
remove dependancy to lidar for mono det3D inferencer
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
For mono detection the inferencer should not have dependancy to lidar2cam and lidar2img matrices. But in the current version it loads them as np.asarrays. So if one is using a dataset(public/custom) that does not have lidar sensor, they won't be able to use the inference module. Moreover the networks don't even use those two matrices, making it completely unnecessary to load them in the code.
Modification
added conditions to only load lidar transitions matrices if they are in the annotation data.
Checklist