You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @dingmyu , Thanks for your work! I have some questions about the loss.
In config, you set conf.corner_in_3d = False, So you don't compute the corners diff in 3D with the GT, am I right?
In use_hill_loss, I guess the hill loss is for Post 3D→2D Optimization , i.e., compute the L1 loss of reprojected 2d coords with respect to GT, am I right?
Why do you disable the two above-mentioned losses in config? Does it deteriorate the final performance by setting them True?
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
Yes, learning corner in 3D space and the hill loss degrades the performance and the training speed slightly.
It’s my unsuccessful attempt, you can have a try it you are interested.
Thanks
Mingyu
On Jul 6, 2020, at 23:29, shuluoshu ***@***.***> wrote:
Hi @dingmyu , Thanks for your work! I have some questions about the loss.
In config, you set conf.corner_in_3d = False, So you don't compute the corners diff in 3D with the GT, am I right?
In use_hill_loss, I guess the hill loss is for Post 3D→2D Optimization , i.e., compute the reprojected 2d coords with respect to GT, am I right?
Why do you disable the two above-mentioned loss in config? Does it deteriorate the final performance by setting them True?
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Hi @dingmyu , I have the same question here.
I want to reproduce your result in corner loss, but what you said above makes me confused.Did the corner loss useful here?How can I reproduce "3DNet+CL" ?
Hi @dingmyu , Thanks for your work! I have some questions about the loss.
In config, you set
conf.corner_in_3d = False
, So you don't compute the corners diff in 3D with the GT, am I right?In
use_hill_loss
, I guess the hill loss is for Post 3D→2D Optimization , i.e., compute the L1 loss of reprojected 2d coords with respect to GT, am I right?Why do you disable the two above-mentioned losses in config? Does it deteriorate the final performance by setting them True?
Thank you.
The text was updated successfully, but these errors were encountered: