SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2011.10671 · 2020

A Review and Comparative Study on Probabilistic Object Detection in Autonomous Driving

arXiv · PDF · Open in the Atlas

Code that ran

2 of 2 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 2 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2011.10671.json · badge: /api/ran/2011.10671.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
asharakeh/pod_compare canonical (classifier label)
classifier basis: classifier_2025
2 ran · 0 no recorded run
FunctionStatusWhere it lives
create_coco_lists Ran
ran; our contract draft was wrong, not the code
asharakeh/pod_compare/src/core/datasets/convert_bdd_to_coco.py
code served (permissive licence) · get_code("1f47b3edfddf5652")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

from collections import defaultdict

# Construct input_labels - a list of detection objects in BDD JSON format
input_labels = [
    {
        'name': 'image_001.jpg',
        'category': 'car',
        'bbox': [10, 20, 100, 150]
    },
    {
        'name': 'image_001.jpg',
        'category': 'pedestrian',
        'bbox': [200, 50, 250, 300]
    },
    {
        'name': 'image_002.jpg',
        'category': 'car',
        'bbox': [50, 100, 200, 250]
    },
    {
        'name': 'image_002.jpg',
        'category': 'truck',
        'bbox': [300, 150, 450, 400]
    },
    {
        'name': 'image_003.jpg',
        'category': 'car',
        'bbox': [100, 100, 300, 350]
    }
]

# Category keys - which categories to include
category_keys = ['car', 'pedestrian', 'truck']

# Category mapper - maps category names to integer IDs
category_mapper = {
    'car': 1,
    'pedestrian': 2,
    'truck': 3
}

ARGS = {
    'input_labels': input_labels,
    'category_keys': category_keys,
    'category_mapper': category_mapper
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
none outside the standard library — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple — a tuple output has no array shape of its own; none is stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
group_by_key Ran
ran; our contract draft was wrong, not the code
asharakeh/pod_compare/src/core/datasets/convert_bdd_to_coco.py
code served (permissive licence) · get_code("94dfc249b44c13d2")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned defaultdict. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

from collections import defaultdict

# Create sample detections in BDD JSON format
# Each detection is a dict with various fields including ones we'll group by
detections = [
    {
        "id": "det_1",
        "image_id": "img_001",
        "category": "car",
        "bbox": [10, 20, 50, 60],
        "confidence": 0.95
    },
    {
        "id": "det_2",
        "image_id": "img_001",
        "category": "pedestrian",
        "bbox": [100, 120, 140, 200],
        "confidence": 0.87
    },
    {
        "id": "det_3",
        "image_id": "img_002",
        "category": "car",
        "bbox": [5, 15, 45, 55],
        "confidence": 0.92
    },
    {
        "id": "det_4",
        "image_id": "img_002",
        "category": "bicycle",
        "bbox": [200, 250, 280, 320],
        "confidence": 0.78
    }
]

key = "image_id"

ARGS = {
    "detections": detections,
    "key": key
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
none outside the standard library — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type defaultdict — a defaultdict output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a defaultdict output the recorded ndim 0 and dtype family float describe that coercion, not the output, and are not stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 2 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Capturing uncertainty in object detection is indispensable for safe autonomous driving. In recent years, deep learning has become the de-facto approach for object detection, and many probabilistic object detectors have been proposed. However, there is no summary on uncertainty estimation in deep object detection, and existing methods are not only built with different network architectures and uncertainty estimation methods, but also evaluated on different datasets with a wide range of evaluation metrics. As a result, a comparison among methods remains challenging, as does the selection of a model that best suits a particular application. This paper aims to alleviate this problem by providing a review and comparative study on existing probabilistic object detection methods for autonomous driving applications. First, we provide an overview of generic uncertainty estimation in deep learning, and then systematically survey existing methods and evaluation metrics for probabilistic object detection. Next, we present a strict comparative study for probabilistic object detection based on an image detector and three public autonomous driving datasets. Finally, we present a discussion of the remaining challenges and future works. Code has been made available at https://github.com/asharakeh/pod_compare.git

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2011.10671")
get_code_for_paper("2011.10671")
have("2011.10671")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2011.10671.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2011.10671.svg)](https://syntology.ai/paper/2011.10671)

Connect an agent — have() is free.