-
Notifications
You must be signed in to change notification settings - Fork 7
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
Issues in dataset preprocessing and ADE/FDE results #3
Comments
Thanks so much for pointing out this problem, fixing the bugs, and re-running the methods! |
Hi @CHENGY12, thank you for your prompt response. Please let me know once you update your results! :D |
Hi @InhwanBae, we have updated the results. Thank you very much! |
Hi @CHENGY12, thank you so much for updating the results! I'm closing this issue now. Thanks again! |
Hi @CHENGY12
Thank you for your great work. I was able to set up and run code quite quickly!
While reproducing results with your evaluation code using pre-processed dataset pickle file from Trajectron++, I noticed that the results were somewhat different.
I tried to analyze the cause of this, and I found that
data_utils.py
in your code is based on theeccv2020
branch of trajectron++. In that branch, there was a critical issue in data pre-processing that future two GT coordinates were additionally used while calculating the acceleration of the last observation points. Many issues have been raised in Trajectron++ regarding this problem (issues #26,#40 and #53).DisDis/trajectron/environment/data_utils.py
Line 27 in 55188a5
Fortunately, this issue was solved in the Trajectron++ code. Below are my PCMD results after fixing it and re-training the DisDis model:
Note that DisDis still performs much better than other comparable models (including reproduced Trajectron++). Also, I did not edit the config file, so there is room for better results when modifying the hyper-parameters.
As your paper compared the DisDis with other SOTA models which use Social-GAN data-loader (Social-GAN, STGAT, Social-STGCNN), I think the authors should fix this issue and update the numbers in the arXiv paper for a fair comparison.
Thank you.
The text was updated successfully, but these errors were encountered: