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

why should we use "softmax" twice in "run.py"? #16

Open
9p15p opened this issue Mar 6, 2020 · 3 comments
Open

why should we use "softmax" twice in "run.py"? #16

9p15p opened this issue Mar 6, 2020 · 3 comments

Comments

@9p15p
Copy link

9p15p commented Mar 6, 2020

  1. in 71 line: msv_E2[sc] = F.softmax(e2[0], dim=1)[:,1].data.cpu()

  2. in 116 line: all_E[:,:,f+1] = F.softmax(Variable(all_E[:,:,f+1]), dim=1).data

Why should we use "softmax" twice?

@seoungwugoh
Copy link
Owner

Hi @9p15p,
For multi-object inference, we first estimate the probability map for each object. Then, we combine them with the soft aggregation.
The first softmax (L71) is for the estimation of each object, and the second softmax (L116) is for implementing the soft aggregation operation.

@ryancll
Copy link

ryancll commented Jun 1, 2020

Hi Seoung,

I'm very interested in your soft aggregation approach for multi-object task and I can understand your mindset after reading your paper. I'm wondering how this approach improve the performance compared with winner-take-all approach?

Thank you!

@seoungwugoh
Copy link
Owner

Hi @ryancll,

It is because maintaining uncertainty is important during propagation. After Soft aggregation the results is a probability map, while, with winner-take-all approach, it is a binary map. I think soft probability map gives the network more information to address challenges during propagation.

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

3 participants