Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

the performance of your released occupancy model tpv04_occupancy #39

Open
SISTMrL opened this issue May 13, 2023 · 2 comments
Open

the performance of your released occupancy model tpv04_occupancy #39

SISTMrL opened this issue May 13, 2023 · 2 comments

Comments

@SISTMrL
Copy link

SISTMrL commented May 13, 2023

image
hello, i run the inference of tpv04_occupancy with command, the gpu i used is v100

python eval.py --py-config config/tpv04_occupancy.py --ckpts ckpt/tpv04_occupancy_v2.pth

the performance on nuscenes is shown in the picture.

the performance is not matched with paper released and could you please explain the evaluation metrics of miou vox/pts, i'm confused about it.

@huang-yh
Copy link
Collaborator

We use different supervision signals for lidar segmentation and occupancy prediction, and thus yielding different model weights for these two tasks. For lidar segmentation, lovasz softmax loss supervises point predictions and crossentropy loss supervises voxel predictions. While for occupancy prediction, both of them supervise voxel predictions.

@huang-yh
Copy link
Collaborator

As for pts miou and vox miou, they are not two metrics, but two different ways to derive predictions for point queries.
Pts miou interpolates voxel features to explicitly generate point features before feeding them to the decoder, while in vox miou, we simply assign the query point the prediction for the voxel which it belongs to.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants