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

Photometric reconstruction loss mentioned in your conclusion #23

Closed
ghost opened this issue Nov 8, 2019 · 3 comments
Closed

Photometric reconstruction loss mentioned in your conclusion #23

ghost opened this issue Nov 8, 2019 · 3 comments

Comments

@ghost
Copy link

ghost commented Nov 8, 2019

Hello,

Many thanks for your great work! It's very impressive. Please forgive my ignorance since I am still new to this research.

In your conclusion you mention adopting a photometric reprojection loss. I assume similar to Goddard et al. and Zhou et al.

Is my assumption correct?

I was wondering if you have already begun working on this? What kind of timeline are you expecting?

If you have not yet begun this, I am also considering adding it to your pipeline as the loss function in place of supervised learning.

My Python/C++ skills are pretty good, but my CNN skills still need a lot of work. Would it be OK to reach out to someone on your team for collaboration on this? Is that even a possibility?

Thanks,
Sameh

@cogaplex-bts
Copy link
Collaborator

Yes, you are correct.
We are currently working on a forked project which uses a hybrid training loss defined in terms of photometric reconstruction error and direct supervision.
With this strategy, we can train our bts using both types of dataset: stereo pairs and images with gt.
Thanks for your interest in our work but sorry for that we have no room to give you ragarding this project.
However, you still have a chance to go on your own project if you have a new idea.
Cheers!

Best wishes,
Jin Han Lee

@jahaniam
Copy link

@tareeqav If you are interested, these two repos might give you an idea and help you with the hybrid loss:

  1. semodepth inference is public
  2. semidepth inference and training are public, and the code is based on monodepth v1.0 code(Goddard et al. you mentioned).

@ghost
Copy link
Author

ghost commented Nov 13, 2019

@a-jahani many thanks! looks very promising

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