-
Notifications
You must be signed in to change notification settings - Fork 11
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
Regarding GraphBEV, my results are off by 20 points compared to the paper's reported results. #4
Comments
I doubt the noise problem. Next you can train and test bevfusion |
是GlobalAlign的问题吗?bevfusion_graph_deformable.yaml和bevfusion_graph.yaml仅仅在Fuser有区别,分别是GlobalAlign和bevfusion的Confuser。GraphBEV的GlobalAlign.py里面我看到你定义了一个calculate_loss,但是并没有用来计算deformed_feature和mm_bev的loss,流程似乎也和文章里的有点出入,是还没有更新代码吗? |
I haven't updated the latest code yet.
…---Original---
From: ***@***.***>
Date: Wed, Aug 7, 2024 10:38 AM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [adept-thu/RoboFusion] Regarding GraphBEV, my results are off by20 points compared to the paper's reported results. (Issue #4)
是GlobalAlign的问题吗?bevfusion_graph_deformable.yaml和bevfusion_graph.yaml仅仅在Fuser有区别,分别是GlobalAlign和bevfusion的Confuser。GraphBEV的GlobalAlign.py里面我看到你定义了一个calculate_loss,但是并没有用来计算deformed_feature和mm_bev的loss,流程似乎也和文章里的有点出入,是还没有更新代码吗?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
So I just use the bevfusion_graph.yaml or bevfusion.yaml and it will be OK? |
You can try bevfusion_graph first, test clean and noisy setting. |
Yes, if you have any questions, I will reply in time. |
OK, I'll try. Thanks you very much. |
Hello, the mAP and NDS of training bevfusion_graph on the clean set for 10 epochs are 62.97 and 66.4, respectively, whereas in the paper, they are reported as 69.7 and 72.4. |
Please add a pre-trained model,bevfuaion. |
Please train openpcdet's bevfusion to ensure that the config is correct and see what the indicators are. |
Take a look at the clean and noise metrics change for bevfusion.yaml, then add bevfusion_graph.yaml to see the clean and noise changes. Remember to add pre-training bevfusion. |
Oh, I forget to train the lidar-branch pretrain model, do you mean it? |
Do you have a training log over there for GraphBEV |
Did you succeed? |
I'm working on it. |
If your results are correct, can you send your checkpoints? |
https://pan.baidu.com/s/1vibPImyEsM4wKy5OlpozJg?pwd=m1pi |
Are there logs trained on all datasets? |
can you send your checkpoints? |
|
Is bevfusion_graph OK? |
I just verify the bevfusion and it's OK, because I have met problems in bevfusion_graph_deformable. It seems that the bevfusion_graph_deformable haven't been fully upgraded. You can try the bevfusion_graph and make sure you add the LiDAR-branch pretrain model. |
I have try the bevfusion_graph earlier but the results are few points lower than the paper, because I forget to add the LiDAR-branch pretrained model. If you add it on, I think it will be OK. |
Do you have logs and checkpoints for training on the full Nuscenes dataset |
used the entire dataset to train 10 epochs with bevfusion_graph.yaml and added pre-training weights for the Lidar branch, but evaluated the result as MAP: 64.7 NDS: 69.49,the reported results in the GraphBEV paper are mAP and NDS of 70.1 and 72.9, |
Hi, can I have a look at the bevfusion log? I repeat that there is a problem with bevfusion |
Did you add LiDAR-branch when regenerating bevfusion? |
Without adding noise, the reported results in the GraphBEV paper are mAP and NDS of 70.1 and 72.9, respectively. However, my results are 45 and 52. I use the config file of bevfusion_graph_deformable.yaml as you said.
The text was updated successfully, but these errors were encountered: