[Enhancement] faster but nondeterministic version of hard voxelization #904
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.
Small enhancement -- reimplement hard voxelization and make it faster at the cost of deterministic property
It is now an optional feature and is disabled by default. Set
deterministic=False
insideVoxelization
config to enable it. It only works for hard voxelization and has no effect when using dynamic voxelization.Performance comparison:
bs=6
bs=6
bs=2
bs=2
bs=4
bs=8
bs=4
Score comparison with MMDet3D Original (May Not Precise!!!!! I also made a lot of code revisions besides voxelization and I messed them up)
bs=12
bs=12
bs=8 fp16
L1-mAPH=63.94
L2-mAP=63.62
L2-mAPH=58.08
L1-mAPH=63.318
L2-mAP=62.619
L2-mAPH=57.573
bs=8
NDS=60.14
NDS=59.66