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

I have a question about your ESANet model inference time. #35

Open
suesuekkim opened this issue May 20, 2022 · 1 comment
Open

I have a question about your ESANet model inference time. #35

suesuekkim opened this issue May 20, 2022 · 1 comment

Comments

@suesuekkim
Copy link

suesuekkim commented May 20, 2022

Firstly, I really appreciate about your clean and kind code.

I have trained ESANet model with SUNRGBD dataset and scenenet dataset. For the SUNRGBD dataset, when i implemented the code prepare_dataset.py in the src colder, the refined depth data was generated, and when i train the depth mode to 'refined', it was trained with the refined depth dataset. Also when i downloaded scenenet dataset, the depth file was refined depth. And I have a question here, in the paper of this model, is the inference time that you mentioned in Fig 4. and Fig 5. include the data pre-processing time (making the raw depth to refined depth)? Without refining the depth data, is it able to implement in the real-time application?

Thank you for reading my issue.

@mona0809
Copy link
Collaborator

mona0809 commented May 20, 2022

Yes, we did train on refined depth data, as it is common practice. Still, you can use the model and apply it on "raw depth" samples. However, you can also train on raw depth data, which results in only slightly lower mIoU. For application, I think, you will not notice the difference.

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