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

different results between monodepth2 script model(c++ libtorch) and original model(python pytorch) #1

Open
MRinel opened this issue Aug 13, 2020 · 2 comments

Comments

@MRinel
Copy link

MRinel commented Aug 13, 2020

Hi, thank you for the work, and have you tested your converted torchscript model? The results of my test just using
monodepth2(FP32) were different from the results of original model, which has both encoder module and decoder module.

@TengFeiHan0
Copy link
Owner

@MRinel In the demo/, you can see the source code about how to do inference based on a converted torchscript model. I only merged the encoder and decoder part, which is a little different from the original code.

@MRinel
Copy link
Author

MRinel commented Aug 14, 2020

@TengFeiHan0 thanks for your reply. I have got the disparity map from packnet.pt (FP32), like:
src
as a constract result from original monodepth2 two stage:
disp_norm

It looks better in detail from your model result compared with the original.and about 7fps in my test on 1080Ti. I wonder how to get the absolute distance(depth) from your model, I have tried just by STEREO_SCALE_FACTOR / disparity , but the result seems strange. In addition, which model do you use for conversion , monocular or mono+stereo?
Thank u.

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