SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2203.10981 · CVPR · 2022

MonoDTR: Monocular 3D Object Detection with Depth-Aware Transformer

Kuan-Chih Huang, Winston Hsu, Hung-Ting Su, Tsung-Han Wu

arXiv · PDF · Open in the Atlas

Code that ran

7 of 8 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; 1 honoured the contract we drafted, 1 violated it and 1 has no contract verdict; 4 failures of our instrument; 1 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/2203.10981.json · badge: /api/ran/2203.10981.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
kuanchihhuang/monodtr canonical (classifier label)
classifier basis not recorded on the link
7 ran · 1 no recorded run
FunctionStatusWhere it lives
anchors_for_shape Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
kuanchihhuang/monodtr/visualDet3D/networks/heads/anchors.py
code served (permissive licence) · get_code("2a214da3b52ccc74")
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 2, dtype family float, shape (18144, 4) 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 numpy as np

ARGS = {
    'image_shape': (256, 384, 3),
    'pyramid_levels': [3, 4, 5],
    'ratios': np.array([0.5, 1, 2]),
    'scales': np.array([2 ** 0, 2 ** (1.0 / 3.0), 2 ** (2.0 / 3.0)]),
    'strides': [8, 16, 32],
    'sizes': [16, 32, 64],
    'shapes_callback': None,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 2, dtype family float, shape (18144, 4) — shape (18144, 4) 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
bin_depths Ran
ran on a synthesized input
kuanchihhuang/monodtr/visualDet3D/networks/heads/depth_losses.py
code served (permissive licence) · get_code("87726458df330951")
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 Tensor, ndim 2, dtype family float, shape (2, 4) 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
import math

torch.manual_seed(0)

# Create a small depth map tensor (batch_size=2, spatial_dims=4)
depth_map = torch.rand(2, 4) * 10 + 1  # values between 1 and 11

# Set up parameters
mode = 'UD'  # Can be 'UD', 'LID', or 'SID'
depth_min = 0.5
depth_max = 100.0
num_bins = 32
target = False

ARGS = {
    'depth_map': depth_map,
    'mode': mode,
    'depth_min': depth_min,
    'depth_max': depth_max,
    'num_bins': num_bins,
    'target': target
}
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 Tensor, ndim 2, dtype family float, shape (2, 4) — shape (2, 4) 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
compute_shape Ran
ran, violated the contract we drafted
kuanchihhuang/monodtr/visualDet3D/networks/heads/anchors.py
code served (permissive licence) · get_code("0e14588c12c9c1b4")
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 list, ndim 2, dtype family int; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim 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 numpy as np

# Analyze the function:
# - image_shape: used as image_shape[:2], then converted to np.array, so needs to be array-like with at least 2 elements
# - pyramid_levels: used in a list comprehension with "for x in pyramid_levels", so needs to be iterable of numbers

# Create distinct sizes for clarity
image_shape = (480, 640, 3)  # 3-element tuple (height, width, channels)
pyramid_levels = [0, 1, 2]   # list of integers representing pyramid levels

ARGS = {
    "image_shape": image_shape,
    "pyramid_levels": pyramid_levels,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type list, ndim 2, dtype family int — a list output has no array shape of its own; none is stated
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
conv3x3 Ran
ran; our contract draft was wrong, not the code
kuanchihhuang/monodtr/visualDet3D/networks/backbones/dla.py
pointer only (licence: MIT); the stored copy get_code serves, from lixiaotong97/DSU, is pointer only (licence: NONE) · get_code("fac5364e2f53c6db")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (MIT), but get_code serves the stored copy, first harvested from lixiaotong97/DSU, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

elu_feature_map Ran
ran, honoured the contract we drafted
kuanchihhuang/monodtr/visualDet3D/networks/detectors/dtr.py
code served (permissive licence) · get_code("0d5505bd782b4a89")
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 Tensor, ndim 2, dtype family float, shape (2, 4) 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)

# The function takes a single parameter 'x' which is passed to torch.nn.functional.elu
# and then 1 is added to it. This means x should be a tensor.

x = torch.randn(2, 4)

ARGS = {
    "x": x
}
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 Tensor, ndim 2, dtype family float, shape (2, 4) — shape (2, 4) 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
generate_anchors Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
kuanchihhuang/monodtr/visualDet3D/networks/heads/anchors.py
code served (permissive licence) · get_code("1279986e0f62b111")
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 2, dtype family float, shape (9, 4) 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 numpy as np

ARGS = {
    "base_size": 16,
    "ratios": np.array([0.5, 1, 2]),
    "scales": np.array([2 ** 0, 2 ** (1.0 / 3.0), 2 ** (2.0 / 3.0)])
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 2, dtype family float, shape (9, 4) — shape (9, 4) 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
get_model_url Ran
ran; our contract draft was wrong, not the code
kuanchihhuang/monodtr/visualDet3D/networks/backbones/dla.py
code served (permissive licence) · get_code("3c9867a84d7c18d9")
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 str. 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 os

ARGS = {
    'data': 'imagenet',
    'name': 'dla34',
    'hash': 'ba72cf86'
}
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 str — a str output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a str 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
dla34 Not yet run
unverified (harvested, no recorded run)
kuanchihhuang/monodtr/visualDet3D/networks/backbones/dla.py
code served (permissive licence) · get_code("1e380a5690a619ef")
How it ran

no invocation recorded.

Also present in other papers' code

Of 8 samples lifted from this paper's linked repositories, 8 carry a function identity and 0 do not. Of the 8 distinct functions with an identity, 7 are also present in other papers whose code we hold (7 with at least one paper dated earlier, 2 the same month, 3 later) and 1 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
conv3x3 686 other papers
374 dated earlier, 11 the same month, 290 later, 11 same year, order not determinable · 31 only as an assembly brick
1406.2661 (2014-06)
Generative Adversarial Networks
1409.0575 (2014-09)
ImageNet Large Scale Visual Recognition Challenge
1412.6572 (2014-12)
Explaining and Harnessing Adversarial Examples
and 683 more not named here
elu_feature_map 14 other papers
1 dated earlier, 2 the same month, 11 later · 2 only as an assembly brick
2104.00680 (2021-04)
LoFTR: Detector-Free Local Feature Matching with Transformers
2203.09645 (2022-03)
MatchFormer: Interleaving Attention in Transformers for Feature Matching
2203.11483 (2022-03)
Practical Stereo Matching via Cascaded Recurrent Network with Adaptive Correlation
and 11 more not named here
get_model_url 4 other papers
2 dated earlier, 2 later
2107.13774 (2021-07)
Geometry Uncertainty Projection Network for Monocular 3D Object Detection
2112.04628 (2021-12)
Learning Auxiliary Monocular Contexts Helps Monocular 3D Object Detection
2207.08531 (2022-07)
DID-M3D: Decoupling Instance Depth for Monocular 3D Object Detection
and 1 more not named here
anchors_for_shape 2 other papers
2 dated earlier
1911.09070 (2019-11)
EfficientDet: Scalable and Efficient Object Detection
2005.13899 (2020-05)
Deep Learning for Automatic Pneumonia Detection
compute_shape 2 other papers
2 dated earlier
1911.09070 (2019-11)
EfficientDet: Scalable and Efficient Object Detection
2005.13899 (2020-05)
Deep Learning for Automatic Pneumonia Detection
generate_anchors 2 other papers
2 dated earlier
1911.09070 (2019-11)
EfficientDet: Scalable and Efficient Object Detection
2005.13899 (2020-05)
Deep Learning for Automatic Pneumonia Detection
dla34 1 other paper
1 dated earlier
2107.13774 (2021-07)
Geometry Uncertainty Projection Network for Monocular 3D Object Detection

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

Monocular 3D object detection is an important yet challenging task in autonomous driving. Some existing methods leverage depth information from an off-the-shelf depth estimator to assist 3D detection, but suffer from the additional computational burden and achieve limited performance caused by inaccurate depth priors. To alleviate this, we propose MonoDTR, a novel end-to-end depth-aware transformer network for monocular 3D object detection. It mainly consists of two components: ( 1) the Depth-Aware Feature Enhancement (DFE) module that implicitly learns depth-aware features with auxiliary supervision without requiring extra computation, and (2) the Depth-Aware Transformer (DTR) module that globally integrates context-and depth-aware features. Moreover, different from conventional pixel-wise positional encodings, we introduce a novel depth positional encoding (DPE) to inject depth positional hints into transformers. Our proposed depth-aware modules can be easily plugged into existing image-only monocular 3D object detectors to improve the performance. Extensive experiments on the KITTI dataset demonstrate that our approach outperforms previous state-of-the-art monocularbased methods and achieves real-time detection. Code is available at https:// github.com/ kuanchihhuang/ MonoDTR.

For agents

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

get_harvested_code_for_paper("2203.10981")
get_code_for_paper("2203.10981")
have("2203.10981")

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

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

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

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

Connect an agent — have() is free.