-
Notifications
You must be signed in to change notification settings - Fork 97
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
How to chose the threshold for LocLoss? #6
Comments
I think you misunderstand the definition for theta_1_3 and theta_2_3. They should not be too large and should be of the same scale with other thetas. All thetas are defined to map a location from the source image to the target image in [-1, 1] scale, instead of the actual pixel space scale, e.g. [0, 224], [0, 256]. For example, any location in the source image or the target image is defined to be in [-1, 1], which is the relative location within the whole image. Hope my reply answer your question. Thank you. |
Got it. I misunderstand it. Thanks a lot. @daerduoCarey |
Another question about the details. Consider the feature map is CHW. C is the channel. H, W are the height and width of the feature maps. Are the parameters [theta_1_1 theta_1_2 theta_1_3] correspond with the transform of features' width (denoted as x in original paper)? Or I misunderstand the order of x and y in the original paper? Thanks. @daerduoCarey |
Yes. You're right. |
OK. Thanks a lot. @daerduoCarey |
Hi, author。In your code, I find that x_t and y_t are reversed, here is your source code
And based on these codes, theta is also reversed, [theta_1_1 theta_1_2 theta_1_3] correspond with [y_t x_t translation]。 |
Usually the [theta_1_1 theta_1_2; theta_2_1 theta_2_2] is mall (less than 1). The parameters [theta_1_3 theta_1_3] will be much bigger (because this is the offset of cropped feature map or image part). So how to set the threshold of LocLoss for those two different types of parameters? Or I misunderstand the implement? Any suggestions? @daerduoCarey
The text was updated successfully, but these errors were encountered: