SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 1902.07830 · 2019

Deep Multi-modal Object Detection and Semantic Segmentation for Autonomous Driving: Datasets, Methods, and Challenges

arXiv · PDF · Open in the Atlas

Code that ran

3 of 3 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 2 have no contract verdict; 1 failure 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/1902.07830.json · badge: /api/ran/1902.07830.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
simonbaas-gif/PJI-BAAS-MEINAS community (classifier label)
classifier basis not recorded on the link
3 ran · 0 no recorded run
FunctionStatusWhere it lives
avg_for_each_vehicles Ran
ran on a synthesized input
simonbaas-gif/PJI-BAAS-MEINAS/object_detection_picture.py
code served (permissive licence) · get_code("6c9df3b8bf383b0f")
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 dict. 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.

import torch

torch.manual_seed(0)

# Analyze the function:
# - tab is iterated as a list of lists
# - Each element in the inner list (list_elem) is itself iterable
# - Each elem in that iteration is a dict-like object with labels as keys
# - The values in elem[lab] are numeric scores that can be added and divided

# Construct valid arguments:
# tab should be a list of lists, where each inner element is a dict with string keys and numeric values

tab = [
    [
        {"metric_a": 10.0, "metric_b": 20.0},
        {"metric_a": 15.0, "metric_b": 25.0}
    ],
    [
        {"metric_a": 5.0, "metric_b": 30.0},
        {"metric_a": 20.0, "metric_b": 35.0}
    ]
]

ARGS = {
    "tab": tab
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type dict — a dict output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a dict 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
load_image_into_numpy_array Ran
ran; our contract draft was wrong, not the code
simonbaas-gif/PJI-BAAS-MEINAS/object_detection_picture.py
code served (permissive licence) · get_code("cf34a278d5d3be18")
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 ndarray, ndim 3, dtype family int, shape (3, 4, 3) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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 PIL import Image
import numpy as np

# Create a simple PIL Image object with specific dimensions
# The function expects an image with .size attribute and .getdata() method
width = 4
height = 3
# Create an RGB image with test data
image_data = np.random.randint(0, 256, (height, width, 3), dtype=np.uint8)
image = Image.fromarray(image_data, mode='RGB')

ARGS = {
    'image': image
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
PIL, numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 3, dtype family int, shape (3, 4, 3) — shape (3, 4, 3) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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
testImage Ran
ran on a synthesized input
simonbaas-gif/PJI-BAAS-MEINAS/object_detection_picture.py
code served (permissive licence) · get_code("c0181dc41af37012")
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 float, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.

import torch

torch.manual_seed(0)

# Analyze the function:
# - testImage takes parameter 'tab'
# - tab is indexed like tab[i], suggesting it's a list/sequence
# - Each tab[i] is iterable with objects that have dict-like behavior (for obj in tab[i])
# - Each obj supports iteration over keys (for key in obj)
# - descriptionImage is a global list of dicts
# - descriptionImage[i] is a dict with elements as keys and numeric values
# - nbElements is a global counter (23)

# Set up globals
descriptionImage = [
    {'feature_a': 5, 'feature_b': 3},
    {'feature_c': 4, 'feature_d': 2},
    {'feature_e': 6}
]

nbElements = 23

# Build tab: a list of lists of dicts
# Each inner dict should have keys that may match descriptionImage keys
tab = [
    [
        {'feature_a': 1, 'other_key': 2},
        {'feature_b': 1, 'another_key': 3}
    ],
    [
        {'feature_c': 1, 'feature_d': 1},
        {'feature_c': 1}
    ],
    [
        {'feature_e': 1, 'feature_e': 1}
    ]
]

ARGS = {
    'tab': tab
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type float, ndim 0, dtype family float, shape () — shape () as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
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 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 1 are also present in other papers whose code we hold (1 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.

FunctionAlso present inEarliest-datedOthers named
load_image_into_numpy_array 2 other papers
2 dated earlier
1511.08060 (2015-11)
An open access repository of images on plant health to enable the development of mobile disease diagnostics
1612.08242 (2016-12)
YOLO9000: Better, Faster, Stronger

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

Recent advancements in perception for autonomous driving are driven by deep learning. In order to achieve robust and accurate scene understanding, autonomous vehicles are usually equipped with different sensors (e.g. cameras, LiDARs, Radars), and multiple sensing modalities can be fused to exploit their complementary properties. In this context, many methods have been proposed for deep multi-modal perception problems. However, there is no general guideline for network architecture design, and questions of "what to fuse", "when to fuse", and "how to fuse" remain open. This review paper attempts to systematically summarize methodologies and discuss challenges for deep multi-modal object detection and semantic segmentation in autonomous driving. To this end, we first provide an overview of on-board sensors on test vehicles, open datasets, and background information for object detection and semantic segmentation in autonomous driving research. We then summarize the fusion methodologies and discuss challenges and open questions. In the appendix, we provide tables that summarize topics and methods. We also provide an interactive online platform to navigate each reference: https://boschresearch.github.io/multimodalperception/.

For agents

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

get_harvested_code_for_paper("1902.07830")
get_code_for_paper("1902.07830")
have("1902.07830")

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

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

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

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

Connect an agent — have() is free.