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
1.Are semantic segmentation task and edge detection task independent of each other? Or do they have mutual influence?
My own thoughts:
In auto_weight_bce loss, the value of loss.mean() is the combination of two tasks(if the output_channel == 2).
2.What does the “beta” in auto_weight_bce loss mean?
My own thoughts:
It seems to have changed the shape of the target tensor from (B,C,H,W) to (B,C,1,1).
I guess it gave a weight to the two channels of each image in the batchsize.But I'm not sure why you're doing this?
Can we make the sum of the weights of the two channels of each predicted image at different resolution levels equal to 1 by doing this?
The text was updated successfully, but these errors were encountered:
They are in fact two independent loss terms. The auto_weight_bce loss function calculates both in parallel for efficiency.
Beta is equivalent to the term $|Y_+| / |Y_+ \cup Y_-|$ from eq. 1 in the paper. The purpose of this term is to adaptively weight the loss contributions of both classes to be equal. This is done because the classes are very imbalanced, especially for the edge detection task.
Sorry to bother you again.
1.Are semantic segmentation task and edge detection task independent of each other? Or do they have mutual influence?
My own thoughts:
In auto_weight_bce loss, the value of loss.mean() is the combination of two tasks(if the output_channel == 2).
2.What does the “beta” in auto_weight_bce loss mean?
My own thoughts:
It seems to have changed the shape of the target tensor from (B,C,H,W) to (B,C,1,1).
I guess it gave a weight to the two channels of each image in the batchsize.But I'm not sure why you're doing this?
Can we make the sum of the weights of the two channels of each predicted image at different resolution levels equal to 1 by doing this?
The text was updated successfully, but these errors were encountered: