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

Actionness Regression not working #28

Open
makecent opened this issue Jul 1, 2023 · 0 comments
Open

Actionness Regression not working #28

makecent opened this issue Jul 1, 2023 · 0 comments

Comments

@makecent
Copy link

makecent commented Jul 1, 2023

The claimed improvement from actionness regression does not seem to materialize based on my implementation using this code repository. The results with and without actionness regression are very similar.

Upon inspecting the implementation, I noticed a potential issue:

TadTR/models/tadtr.py

Lines 314 to 325 in 983ae14

src_segments = outputs['pred_segments'].view((-1, 2))
target_segments = torch.cat([t['segments'] for t in targets], dim=0)
losses = {}
iou_mat = segment_ops.segment_iou(
segment_ops.segment_cw_to_t1t2(src_segments),
segment_ops.segment_cw_to_t1t2(target_segments))
gt_iou = iou_mat.max(dim=1)[0]
pred_actionness = outputs['pred_actionness']
loss_actionness = F.l1_loss(pred_actionness.view(-1), gt_iou.view(-1).detach())

On line 315, all target segments in the batch are concatenated, and on line 323 the maximum IoU between a predicted segment and all target segments is taken as the actionness ground truth. However, the IoUs are computed across videos, likely producing a maximum IoU between a predicted segment in video A and a ground truth segment in video B.

Even after correcting this issue, there was still no performance improvement from the actionness regression in my runs (the performance drops a lot actually). Upon my inspection, that because the actionness regression suffers from a serious label imbalance problem as most target IoUs are zero.

makecent added a commit to makecent/DITA that referenced this issue Jul 1, 2023
1. We only totally abandoned the Actionness Regression and delete all related functions and files. See this issue for details:xlliu7/TadTR#28
3. Reformat/clean code space.
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

1 participant