Papers › A Ranking-based, Balanced Loss Function Unifying Classification and Localisation in...

A Ranking-based, Balanced Loss Function Unifying Classification and Localisation in Object Detection

28 Sep 2020NeurIPS 2020 12arXiv:2009.13592archive 2025-07-28

Kemal Oksuz, Baris Can Cam, Emre Akbas, Sinan Kalkan

We propose average Localisation-Recall-Precision (aLRP), a unified, bounded, balanced and ranking-based loss function for both classification and localisation tasks in object detection. aLRP extends the Localisation-Recall-Precision (LRP) performance metric (Oksuz et al., 2018) inspired from how Average Precision (AP) Loss extends precision to a ranking-based loss function for classification (Chen et al., 2020). aLRP has the following distinct advantages: (i) aLRP is the first ranking-based loss function for both classification and localisation tasks. (ii) Thanks to using ranking for both tasks, aLRP naturally enforces high-quality localisation for high-precision classification. (iii) aLRP provides provable balance between positives and negatives. (iv) Compared to on average ∼6 hyperparameters in the loss functions of state-of-the-art detectors, aLRP Loss has only one hyperparameter, which we did not tune in practice. On the COCO dataset, aLRP Loss improves its ranking-based predecessor, AP Loss, up to around 5 AP points, achieves 48.9 AP without test time augmentation and outperforms all one-stage detectors. Code available at: https://github.com/kemaloksuz/aLRPLoss .

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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

The archive's official repository (kemaloksuz/aLRPLoss) was not harvested; the 2 samples below come from 2 community repositories.

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

By repository: community (archive-listed): 2 samples from 2 repositories, 2 ran (2 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

kemaloksuz/aLRPLoss officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: not harvested report
kemaloksuz/aLRPLoss-AblationExperiments mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
xudangliatiger/ape-loss mentioned on GitHubpytorchNOASSERTIONSyntology: 1 sample, 1 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

2 samples harvested: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. “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.

2ran

Licence: 1 of the 2 samples is 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

kemaloksuz/aLRPLoss-AblationExperiments community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
aLRPLoss lib/model/alrploss.py ran MIT (permissive) · b33b07a0e7320129 · report fixture: returned aLRPLoss · level recorded 2026-09-22
xudangliatiger/ape-loss community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
aLRPLoss mmdet/models/losses/alrp_loss.py ran licence not identified · pointer only · 7628eda0d3740ba1 · report fixture: returned aLRPLoss · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

2 assemblies on this paper: 2 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

2 sibling assemblies for aLRP (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for aLRP (graph method: aLRP). 1 brick; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 2 siblings

  1. aLRPLoss entry · level 1 · ran · b33b07a0e7320129

harvested Assembly for aLRP (graph method: aLRP). 1 brick; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

one of 2 siblings

  1. aLRPLoss entry · level 1 · ran · 7628eda0d3740ba1

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2009.13592") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

ClassificationGeneral ClassificationObject Detectionobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Object Detection COCO minival Faster R-CNN+aLRP Loss (ResNet-50, 500 scale) AP50 60.7 #176 of 220 Archive leaderboard report
Object Detection COCO minival Faster R-CNN+aLRP Loss (ResNet-50, 500 scale) AP75 43.3 #176 of 220 Archive leaderboard report
Object Detection COCO minival Faster R-CNN+aLRP Loss (ResNet-50, 500 scale) box AP 40.7 #176 of 220 Archive leaderboard report
Object Detection COCO minival RetinaNet+aLRP Loss (ResNet-50, 500 scale) AP50 60.3 #183 of 220 Archive leaderboard report
Object Detection COCO minival RetinaNet+aLRP Loss (ResNet-50, 500 scale) AP75 42.3 #183 of 220 Archive leaderboard report
Object Detection COCO minival RetinaNet+aLRP Loss (ResNet-50, 500 scale) box AP 40.2 #183 of 220 Archive leaderboard report
Object Detection COCO minival FoveaBox+aLRP Loss (ResNet-50, 500 scale) AP50 58.8 #186 of 220 Archive leaderboard report
Object Detection COCO minival FoveaBox+aLRP Loss (ResNet-50, 500 scale) AP75 41.5 #186 of 220 Archive leaderboard report
Object Detection COCO minival FoveaBox+aLRP Loss (ResNet-50, 500 scale) box AP 39.7 #186 of 220 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, multiscale test) AP50 70.3 #90 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, multiscale test) AP75 53.9 #90 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, multiscale test) APL 63.0 #90 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, multiscale test) APM 53.1 #90 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, multiscale test) APS 32.0 #90 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, multiscale test) box mAP 50.2 #90 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, single scale) AP50 69.3 #100 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, single scale) AP75 52.5 #100 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, single scale) APL 62.1 #100 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, single scale) APM 51.5 #100 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, single scale) APS 30.8 #100 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, DCN, single scale) box mAP 48.9 #100 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, single scale) AP50 68.4 #113 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, single scale) AP75 51.1 #113 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, single scale) APL 59.1 #113 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, single scale) APM 50.8 #113 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, single scale) APS 30.2 #113 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101-64x4d, single scale) box mAP 47.8 #113 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101, DCN, 500 scale) AP50 65.0 #144 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101, DCN, 500 scale) AP75 47.5 #144 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101, DCN, 500 scale) APL 58.3 #144 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101, DCN, 500 scale) APM 48.1 #144 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101, DCN, 500 scale) APS 24.6 #144 of 225 Archive leaderboard report
Object Detection COCO test-dev aLRP Loss (ResNext-101, DCN, 500 scale) box mAP 44.6 #144 of 225 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