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

The formulation of training regression targets in FCOS paper #161

Open
geoexploring opened this issue Jul 17, 2020 · 4 comments
Open

The formulation of training regression targets in FCOS paper #161

geoexploring opened this issue Jul 17, 2020 · 4 comments

Comments

@geoexploring
Copy link

Hi, thank you all for making FCOS available!

Two things in the FCOS paper confuse me:

  1. As shown in the figure below, is there a comma missing in the red line? I found this in both the conference edition and the journal edition of FCOS paper.
    0

  2. As the FCOS paper says,
    1
    and, the training regression targets for the location is formulated as:
    2
    However, when I read the FCOS code, I found it was not the same as the definition in the paper,

    locations = torch.stack((shift_x, shift_y), dim=1) + stride // 2

    xs, ys = locations[:, 0], locations[:, 1]

    l = xs[:, None] - bboxes[:, 0][None]

    The definition in the code feels more like the following formula:
    3

Please correct me if I made any mistakes.
Thank you in advance

@tianzhi0549
Copy link
Member

@geoexploring 1) Thank you for pointing it out. You are right. We miss a comma here. 2) The implementation is consistent with our paper. locations are x and y in Eq (1).

@geoexploring
Copy link
Author

@tianzhi0549 Thank you for your reply!

To 2), my understanding is,

  • location (x,y) is in the coordinate system of the feature map, which can be mapped to the coordinate system of the input image and can be expressed as:
    1
  • and the Bi is the gt bbox's definition, which is also in the coordinate system of the input image.
    2

I feel that Eq (1) is subtracting the numbers from two different coordinate systems.

Please correct me if I made any mistakes.
Thank you in advance

@tianzhi0549
Copy link
Member

@geoexploring It seems you are right ... We mix up the two coordinate systems here. Sorry about that. We will fix it in a revision.

@geoexploring
Copy link
Author

@tianzhi0549 hahaha, thank you for your honesty! many thanks!

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