Papers › BSN++: Complementary Boundary Regressor with Scale-Balanced Relation Modeling for...

BSN++: Complementary Boundary Regressor with Scale-Balanced Relation Modeling for Temporal Action Proposal Generation

15 Sep 2020arXiv:2009.07641archive 2025-07-28

Haisheng Su, Weihao Gan, Wei Wu, Yu Qiao, Junjie Yan

Generating human action proposals in untrimmed videos is an important yet challenging task with wide applications. Current methods often suffer from the noisy boundary locations and the inferior quality of confidence scores used for proposal retrieving. In this paper, we present BSN++, a new framework which exploits complementary boundary regressor and relation modeling for temporal proposal generation. First, we propose a novel boundary regressor based on the complementary characteristics of both starting and ending boundary classifiers. Specifically, we utilize the U-shaped architecture with nested skip connections to capture rich contexts and introduce bi-directional boundary matching mechanism to improve boundary precision. Second, to account for the proposal-proposal relations ignored in previous methods, we devise a proposal relation block to which includes two self-attention modules from the aspects of position and channel. Furthermore, we find that there inevitably exists data imbalanced problems in the positive/negative proposals and temporal durations, which harm the model performance on tail distributions. To relieve this issue, we introduce the scale-balanced re-sampling strategy. Extensive experiments are conducted on two popular benchmarks: ActivityNet-1.3 and THUMOS14, which demonstrate that BSN++ achieves the state-of-the-art performance. Not surprisingly, the proposed BSN++ ranked 1st place in the CVPR19 - ActivityNet challenge leaderboard on temporal action localization task.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 9 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 9 samples from 1 repository, 9 ran (9 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

xxcheng0708/BSNPlusPlus-boundary-sensitive-network mentioned on GitHubpytorchMITSyntology: 9 samples, 9 ran (0 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

9 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

9ran

Licence: 0 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from xxcheng0708/BSNPlusPlus-boundary-sensitive-network. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

xxcheng0708/BSNPlusPlus-boundary-sensitive-network community (archive-listed) 9 samples, 9 ran (0 instrument-failed) · 0 unverified
bi_loss loss_function.py ran fingerprinted MIT (permissive) · 2a1b5cbf26a5e2ba · report fixture: signature pred_score:Tensor/2/float, gt_label:Tensor/2/float · returned Tensor · level recorded 2026-09-24
cbg_loss_func loss_function.py ran fingerprinted MIT (permissive) · d57bf724ccd7a70d · report fixture: signature pred_start:Tensor/2/float, pred_end:Tensor/2/float, gt_start:Tensor/2/float, gt_end:Tensor/2/float · returned Tensor · level recorded 2026-09-24
conv_block in 95 papers models.py ran MIT (permissive) · 83a6fac7349fd1f0 · report fixture: signature in_ch:int/0/int, out_ch:int/0/int, kernel_size:int/0/int, stride:int/0/int, bn_layer:bool/0/bool, activate:bool/0/bool · returned Sequential · level recorded 2026-09-24
getDatasetDict post_processing.py ran MIT (permissive) · 13551e06a372ae9c · report fixture: signature opt:dict/0/? · returned dict · level recorded 2026-09-24
get_mask in 119 papers
census: 9 implementations from 10 papers, 9 distinct outputs across 7 buckets, one shared input per bucket
loss_function.py ran fingerprinted MIT (permissive) · 1cd5e9eec5a11010 · report fixture: signature tscale:int/0/int · returned Tensor · level recorded 2026-09-24
ioa_with_anchors utils.py ran fingerprinted MIT (permissive) · 49b3db69edc148a7 · report fixture: signature anchors_min:ndarray/1/float, anchors_max:ndarray/1/float, box_min:ndarray/1/float, box_max:ndarray/1/float · returned ndarray · level recorded 2026-09-25
iou_with_anchors utils.py ran MIT (permissive) · 1ac2acb4c84fccca · report fixture: signature anchors_min:ndarray/1/float, anchors_max:ndarray/1/float, box_min:ndarray/0/float, box_max:ndarray/0/float · returned ndarray · level recorded 2026-09-25
load_json in 344 papers dataset.py ran MIT (permissive) · 1e0bb35d27bdc115 · report fixture: signature file:str/0/str · returned dict · level recorded 2026-09-24
load_json in 344 papers post_processing.py ran MIT (permissive) · e924a491a8d3290b · report fixture: signature file:str/0/str · returned dict · level recorded 2026-09-24

Tasks

Action LocalizationTemporal Action LocalizationTemporal Action Proposal Generation

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Temporal Action Localization ActivityNet-1.3 BSN++ mAP 34.88 #23 of 33 Archive leaderboard report
Temporal Action Localization ActivityNet-1.3 BSN++ mAP IOU@0.5 51.27 #23 of 33 Archive leaderboard report
Temporal Action Localization ActivityNet-1.3 BSN++ mAP IOU@0.75 35.70 #23 of 33 Archive leaderboard report
Temporal Action Localization ActivityNet-1.3 BSN++ mAP IOU@0.95 8.33 #23 of 33 Archive leaderboard report
Temporal Action Proposal Generation ActivityNet-1.3 BSN++ AR@100 76.52 #6 of 11 Archive leaderboard report
Temporal Action Proposal Generation ActivityNet-1.3 BSN++ AUC (val) 68.26 #6 of 11 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections