Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Some problems about val #61

Closed
wuwangzhuanwan opened this issue Dec 1, 2022 · 3 comments
Closed

Some problems about val #61

wuwangzhuanwan opened this issue Dec 1, 2022 · 3 comments

Comments

@wuwangzhuanwan
Copy link

hello, I find some problems about 'val', I found that there was a problem with the code in line 144 'val_dataset.pipeline = cfg.data.train.pipeline', and it needs to be changed to this val_dataset.pipeline = cfg.data.train.dataset.pipeline. right?

@filaPro
Copy link
Contributor

filaPro commented Dec 2, 2022

Looks you are right, in case of RepeatDataset wrapper. It is kind of mmdetection3d bug, as we don't modify this file.

@wuwangzhuanwan
Copy link
Author

If I want to train 10 classes of detection on the nuscenes dataset, do I just need to change the following two things?
(1)Comment this line: gt_labels_3d[gt_labels_3d > 0] = -1 in mmdet3d/datasets/nuscenes_monocular_dataset.py
(2)Modify this line:num_classes=1==>num_classes=10 in configs/imvoxelnet/imvoxelnet_nuscenes.py
Am I right? O(∩_∩)O

@filaPro
Copy link
Contributor

filaPro commented Dec 8, 2022

Basically yes, but the performance will be very low. For better performance you may follow Anchor3DHead parameters for NuScenes including sizes, scales and rotations. And for 3 scales here you also need to save 3 2d feature maps from 3 levels of the neck. We use only 1 scale (and 1 output of the neck) if I remember correctly.

@filaPro filaPro closed this as completed Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants