-
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
bad render images on evaluation #13
Comments
@szhang963 psnr: 22.334688186645508
Evaluating 2/60
psnr: 21.38553237915039
Evaluating 3/60
psnr: 20.18088722229004
Evaluating 4/60
psnr: 19.331192016601562
Evaluating 5/60
psnr: 18.859142303466797
Evaluating 6/60 And I train it for 5w epochs How many epochs did you train? |
The epoch is 8.5w for the above evaluation. I think there are some hard codes and inconsistencies for training and evaluation. |
hey, did you just execute |
I execute 'eval.py' to get rendered results in a default setting. |
Also, the intrinsics is set to None in train_depends in line99 |
@szhang963 can you check the values and size of intrinsics in |
Thanks for your reply. I also used neScenes mini 0916 for training. Why is the intrinsic set to None for evaluation? Should I set the values to the default value from the camera sensor? |
@amoghskanda I fix the code 'images, poses, _, intrinsics, depth_gts, flow, cam_index, skymask, seg_masks, semantic = train_depends'. |
@szhang963 I'm not able to render because of an error I'm facing. NoneType object is not subscriptable on Line352 in |
@szhang963 I changed the 'render_image' function in models.py.
And, the code was changed for right input of intrinsic. |
@ZiYang-xie Hi, Could you please spare some time to assist me with this matter? I would greatly appreciate your help. |
@szhang963 thank you so much. I'm able to render the images now. Did you try experimenting on the renders like change the view or change the ego vehicle trajectory mentioned in the paper? And yes, the psnr is poor for me as well and diminishes after every eval. |
@amoghskanda No, the problem of rendering needs to be solved first. |
@ZiYang-xie thank you for this great work. Any insights on szhang's question? How do we improve the rendering results for nuScenes? |
Thank you for reaching out with your question. I'll look into this problem shortly. To address the issue you're encountering, I recommend experimenting with a different scene given the complexity of scene-0916 or try Waymo instead of nuScenes for the reconstruction. Please consider this approach, and feel free to reach out if you need further guidance or assistance. |
Hi, I appreciate your work very much. I encountered some questions when I reimplemented your work.
I got a high PSNR (about 46+) for the training in scene-0916 of nuscene. However, I got a poor PSNR and bad render image when I evaluated the model using eval.py and the quality of each frame will be worse than the previous frame (e.g. 20.123, 19.45, 17.32, 16.34 for PSNR). Could you provide some suggestions for me to solve it?
Thank you in advance.
The text was updated successfully, but these errors were encountered: