SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2405.14870 · 2024

An Empirical Study of Training State-of-the-Art LiDAR Segmentation Models

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; 1 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/2405.14870.json · badge: /api/ran/2405.14870.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
open-mmlab/mmdetection3d canonical (classifier label)
classifier basis: census
3 ran · 0 no recorded run
FunctionStatusWhere it lives
get_final_epoch Ran
ran, honoured the contract we drafted
open-mmlab/mmdetection3d/.dev_scripts/gather_models.py
code served (permissive licence) · get_code("8959afcb82c85624")
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 int, ndim 0, dtype family int, 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.

# Read the function body to understand what it does:
# - Takes a config parameter
# - Calls config.find('grid_rcnn') and config.find('2x') - so config must be a string
# - Calls config.find() on various schedule names
# - Returns an integer (epoch number)

# The function expects config to be a string and searches for substrings in it

# Test case 1: A config string that matches 'grid_rcnn' and '2x'
config_grid_rcnn_2x = 'grid_rcnn_2x_model'

# Test case 2: A config string that matches one of the schedule names
config_with_schedule = 'my_model_100e_config'

# Test case 3: A config string with no matches
config_no_match = 'simple_model_config'

ARGS = {
    'config': config_grid_rcnn_2x
}
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 int, ndim 0, dtype family int, 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
get_model_dataset Ran
ran; our contract draft was wrong, not the code
open-mmlab/mmdetection3d/.dev_scripts/gather_models.py
code served (permissive licence) · get_code("9cef05bbed8ed168")
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 torch
import numpy as np
from pathlib import Path

# The function takes a log_json_path parameter which is a string
# It searches for dataset keys within that string path
# We need to provide a path that contains one of the keys from RESULTS_LUT

log_json_path = "/home/user/experiments/coco/results.json"

ARGS = {
    "log_json_path": log_json_path
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — 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
process_checkpoint Ran
ran; our contract draft was wrong, not the code
open-mmlab/mmdetection3d/.dev_scripts/gather_models.py
code served (permissive licence) · get_code("e76a491553cf9fcf")
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 torch
import tempfile
import os

torch.manual_seed(0)

# Create a temporary directory for checkpoint files
temp_dir = tempfile.mkdtemp()

# Create a minimal checkpoint dict with a model state and optimizer
checkpoint = {
    'model': {
        'layer1.weight': torch.randn(4, 3),
        'layer1.bias': torch.randn(4),
    },
    'optimizer': {
        'state': {},
        'param_groups': [],
    },
    'epoch': 1,
}

# Save the checkpoint to a temporary file
in_file = os.path.join(temp_dir, 'checkpoint.pth')
torch.save(checkpoint, in_file)

# Define output file path
out_file = os.path.join(temp_dir, 'checkpoint_processed.pth')

ARGS = {
    'in_file': in_file,
    'out_file': out_file,
}
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 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

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, 3 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 3 the same month, 3 later) and 0 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
process_checkpoint 45 other papers
39 dated earlier, 1 the same month, 4 later, 1 undated
1904.11490 (2019-04)
RepPoints: Point Set Representation for Object Detection
1906.07155 (2019-06)
MMDetection: Open MMLab Detection Toolbox and Benchmark
1908.05612 (2019-08)
R3Det: Refined Single-Stage Detector with Feature Refinement for Rotating Object
and 42 more not named here
get_final_epoch 35 other papers
29 dated earlier, 1 the same month, 4 later, 1 undated
1904.11490 (2019-04)
RepPoints: Point Set Representation for Object Detection
1906.07155 (2019-06)
MMDetection: Open MMLab Detection Toolbox and Benchmark
1908.05612 (2019-08)
R3Det: Refined Single-Stage Detector with Feature Refinement for Rotating Object
and 32 more not named here
get_model_dataset 26 other papers
21 dated earlier, 1 the same month, 3 later, 1 undated
2104.06114 (2021-04)
Back-tracing Representative Points for Voting-based 3D Object Detection in Point Clouds
2104.10956 (2021-04)
FCOS3D: Fully Convolutional One-Stage Monocular 3D Object Detection
2112.04680 (2021-12)
SimIPU: Simple 2D Image and 3D Point Cloud Unsupervised Pre-Training for Spatial-Aware Visual Representations
and 23 more not named here

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

In the rapidly evolving field of autonomous driving, precise segmentation of LiDAR data is crucial for understanding complex 3D environments. Traditional approaches often rely on disparate, standalone codebases, hindering unified advancements and fair benchmarking across models. To address these challenges, we introduce MMDetection3D-lidarseg, a comprehensive toolbox designed for the efficient training and evaluation of state-of-the-art LiDAR segmentation models. We support a wide range of segmentation models and integrate advanced data augmentation techniques to enhance robustness and generalization. Additionally, the toolbox provides support for multiple leading sparse convolution backends, optimizing computational efficiency and performance. By fostering a unified framework, MMDetection3D-lidarseg streamlines development and benchmarking, setting new standards for research and application. Our extensive benchmark experiments on widely-used datasets demonstrate the effectiveness of the toolbox. The codebase and trained models have been publicly available, promoting further research and innovation in the field of LiDAR segmentation for autonomous driving.

For agents

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

get_harvested_code_for_paper("2405.14870")
get_code_for_paper("2405.14870")
have("2405.14870")

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

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

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

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

Connect an agent — have() is free.