SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 1904.01416 · 2019

SemanticKITTI: A Dataset for Semantic Scene Understanding of LiDAR Sequences

arXiv · PDF · Open in the Atlas

Code that ran

8 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; 0 honoured the contract we drafted, 0 violated it and 5 have no contract verdict; 3 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/1904.01416.json · badge: /api/ran/1904.01416.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
PRBonn/semantic-kitti-api canonical (classifier label)
classifier basis: classifier_2025
1 ran · 0 no recorded run
theia-4869/semantic-poss-api community (classifier label)
classifier basis not recorded on the link
7 ran · 0 no recorded run
FunctionStatusWhere it lives
get_eval_mask Ran
ran on a synthesized input
theia-4869/semantic-poss-api/evaluate_completion.py
code served (permissive licence) · get_code("aa916373de196b7f")
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 float, shape (2, 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 numpy as np

# Create small numpy arrays for labels and invalid_voxels
# labels: ground truth voxels with some set to 255 (ignore label)
labels = np.array([
    [[0, 1, 255, 2],
     [1, 2, 3, 255]],
    [[5, 6, 7, 8],
     [9, 10, 11, 12]]
], dtype=np.int32)

# invalid_voxels: binary mask where 1 indicates invalid voxels
invalid_voxels = np.array([
    [[0, 1, 0, 0],
     [1, 0, 0, 0]],
    [[0, 0, 1, 0],
     [0, 0, 0, 1]]
], dtype=np.int32)

ARGS = {
    "labels": labels,
    "invalid_voxels": invalid_voxels
}
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 3, dtype family float, shape (2, 2, 4) — shape (2, 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
load_gt_volume Ran
ran on a synthesized input
theia-4869/semantic-poss-api/evaluate_completion.py
code served (permissive licence) · get_code("e6b6ef383c5835d7")
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.

import numpy as np
import os
import tempfile

# Create temporary directory and files for testing
temp_dir = tempfile.mkdtemp()

# Create a valid compressed voxel grid file
# 10 bytes of uint8 data, each byte encodes 8 voxels
compressed_data = np.array([0b10101010, 0b11001100, 0b11110000, 0b00001111,
                            0b10101010, 0b11001100, 0b11110000, 0b00001111,
                            0b10101010, 0b11001100], dtype=np.uint8)
filename = os.path.join(temp_dir, "test_volume.raw")
compressed_data.tofile(filename)

# Create the corresponding invalid voxels file
invalid_data = np.array([0b10101010, 0b11001100, 0b11110000, 0b00001111,
                         0b10101010, 0b11001100, 0b11110000, 0b00001111,
                         0b10101010, 0b11001100], dtype=np.uint8)
basename = os.path.splitext(filename)[0]
invalid_filename = basename + '.invalid'
invalid_data.tofile(invalid_filename)

ARGS = {
    "filename": filename
}
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 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
parse_calibration Ran
ran; our contract draft was wrong, not the code
theia-4869/semantic-poss-api/convert_points_pos.py
code served (permissive licence) · get_code("32b4a6da14b662c0")
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 tempfile
import os
import numpy as np

# Create a temporary calibration file
temp_file = tempfile.NamedTemporaryFile(mode='w', delete=False, suffix='.txt')
temp_filename = temp_file.name

# Write sample calibration data
# Each line has format: key: val1 val2 val3 val4 val5 val6 val7 val8 val9 val10 val11 val12
calib_content = """P0: 1.0 2.0 3.0 4.0 5.0 6.0 7.0 8.0 9.0 10.0 11.0 12.0
P1: 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 1.1 1.2
P2: 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3.0 3.1 3.2
"""

temp_file.write(calib_content)
temp_file.close()

ARGS = {
    'filename': temp_filename
}
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 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
parse_calibration Ran
ran; our contract draft was wrong, not the code
theia-4869/semantic-poss-api/generate_sequential.py
code served (permissive licence) · get_code("42deada6e4037511")
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 tempfile
import os
import numpy as np

# Create a temporary calibration file with valid content
temp_dir = tempfile.mkdtemp()
calib_filename = os.path.join(temp_dir, "calibration.txt")

with open(calib_filename, 'w') as f:
    f.write("P0: 721.5377 0.0 609.5593 44.85 0.0 721.5377 172.854 0.2163 0.0 0.0 1.0 0.0027\n")
    f.write("P1: 721.5377 0.0 609.5593 -40.8 0.0 721.5377 172.854 0.0 0.0 0.0 1.0 0.0\n")
    f.write("R0_rect: 0.9999 0.0073 -0.0084 0.0 -0.0073 1.0 0.0027 0.0 0.0084 -0.0027 0.9999 0.0\n")
    f.write("Tr_velo_to_cam: 0.0 -1.0 0.0 0.0 0.0 0.0 -1.0 -0.02 1.0 0.0 0.0 -0.27 0.0 0.0 0.0 1.0\n")

ARGS = {
    "filename": calib_filename
}
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 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
parse_poses Ran
ran on a synthesized input
theia-4869/semantic-poss-api/convert_points_pos.py
code served (permissive licence) · get_code("ade3294f7451aa46")
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 3, dtype family float; 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
import tempfile
import os

# Create a temporary file with pose data
temp_file = tempfile.NamedTemporaryFile(mode='w', delete=False, suffix='.txt')
temp_filename = temp_file.name

# Write 3 lines of pose data (12 values per line)
# Each line represents a 3x4 pose matrix in row-major order
pose_lines = [
    "1.0 0.0 0.0 0.5 0.0 1.0 0.0 1.5 0.0 0.0 1.0 2.5",
    "0.9 0.1 0.0 1.0 -0.1 0.9 0.0 2.0 0.0 0.0 1.0 3.0",
    "0.8 0.2 0.0 1.5 -0.2 0.8 0.0 2.5 0.0 0.0 1.0 3.5"
]

for line in pose_lines:
    temp_file.write(line + '\n')

temp_file.close()

# Create a calibration dict with a Tr transformation matrix
calibration = {
    'Tr': np.array([
        [1.0, 0.0, 0.0, 0.0],
        [0.0, 1.0, 0.0, 0.0],
        [0.0, 0.0, 1.0, 0.0],
        [0.0, 0.0, 0.0, 1.0]
    ])
}

ARGS = {
    'filename': temp_filename,
    'calibration': calibration
}
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 3, dtype family float — 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
parse_poses Ran
ran on a synthesized input
theia-4869/semantic-poss-api/generate_sequential.py
code served (permissive licence) · get_code("fedc700ffd730434")
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 3, dtype family float; 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
from numpy.linalg import inv
import tempfile
import os

# Create a temporary poses file
temp_file = tempfile.NamedTemporaryFile(mode='w', delete=False, suffix='.txt')
temp_filename = temp_file.name

# Write sample pose data (3 rows of 12 values each, representing 3x4 matrix rows)
pose_lines = [
    "1.0 0.0 0.0 0.1 0.0 1.0 0.0 0.2 0.0 0.0 1.0 0.3",
    "0.9 0.1 0.0 0.15 -0.1 0.9 0.0 0.25 0.0 0.0 1.0 0.35",
    "0.8 0.2 0.0 0.2 -0.2 0.8 0.0 0.3 0.0 0.0 1.0 0.4"
]
for line in pose_lines:
    temp_file.write(line + '\n')
temp_file.close()

# Create calibration dict with a 4x4 Tr matrix
Tr = np.array([
    [1.0, 0.0, 0.0, 0.0],
    [0.0, 1.0, 0.0, 0.0],
    [0.0, 0.0, 1.0, 0.0],
    [0.0, 0.0, 0.0, 1.0]
], dtype=np.float64)

calibration = {
    'Tr': Tr
}

ARGS = {
    'filename': temp_filename,
    'calibration': calibration
}
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 3, dtype family float — 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
read_points Ran
ran on a synthesized input
theia-4869/semantic-poss-api/convert_points_pos.py
code served (permissive licence) · get_code("5537415954f69877")
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 (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 numpy as np
import tempfile
import os

# Create a temporary binary file with float32 data
# The function expects data that can be reshaped to (-1, 4)
temp_dir = tempfile.mkdtemp()
bin_file_path = os.path.join(temp_dir, "points.bin")

# Create sample data: 8 float32 values (will reshape to 2x4)
sample_data = np.array([1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0], dtype=np.float32)
sample_data.tofile(bin_file_path)

ARGS = {
    "bin_file": bin_file_path
}
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 (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
unpack Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
PRBonn/semantic-kitti-api/auxiliary/SSCDataset.py
code served (permissive licence) · get_code("b6ce60277ddab1d7")
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 1, dtype family int, shape (24,) 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

# Create a small compressed voxel grid
# The function expects a 1D array of uint8 values where each byte encodes 8 bits
# Let's create a simple compressed array with a few bytes
compressed = np.array([0b10101010, 0b11110000, 0b00001111], dtype=np.uint8)

ARGS = {
    "compressed": compressed
}
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 1, dtype family int, shape (24,) — shape (24,) 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 8 samples lifted from this paper's linked repositories, 8 carry a function identity and 0 do not. Of the 7 distinct functions with an identity, 2 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 2 later) and 5 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
parse_calibration 6 other papers
6 later
2204.08084 (2022-04)
Learning 3D Semantics from Pose-Noisy 2D Images with Hierarchical Full Attention Network
2206.00927 (2022-06)
DPM-Solver: A Fast ODE Solver for Diffusion Probabilistic Model Sampling in Around 10 Steps
Nunes_Temporal_Consistent_3D_LiDAR_Representation_Learning_for_Semantic_Perception_in_CVPR_2023_paper (2023 (year only))
Temporal Consistent 3D LiDAR Representation Learning for Semantic Perception in Autonomous Driving
and 3 more not named here
unpack 1 other paper
1 later
2008.11459 (2020-08)
Semantic Graph Based Place Recognition for 3D Point Clouds

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

Semantic scene understanding is important for various applications. In particular, self-driving cars need a fine-grained understanding of the surfaces and objects in their vicinity. Light detection and ranging (LiDAR) provides precise geometric information about the environment and is thus a part of the sensor suites of almost all self-driving cars. Despite the relevance of semantic scene understanding for this application, there is a lack of a large dataset for this task which is based on an automotive LiDAR. In this paper, we introduce a large dataset to propel research on laser-based semantic segmentation. We annotated all sequences of the KITTI Vision Odometry Benchmark and provide dense point-wise annotations for the complete $360^{o}$ field-of-view of the employed automotive LiDAR. We propose three benchmark tasks based on this dataset: (i) semantic segmentation of point clouds using a single scan, (ii) semantic segmentation using multiple past scans, and (iii) semantic scene completion, which requires to anticipate the semantic scene in the future. We provide baseline experiments and show that there is a need for more sophisticated models to efficiently tackle these tasks. Our dataset opens the door for the development of more advanced methods, but also provides plentiful data to investigate new research directions.

For agents

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

get_harvested_code_for_paper("1904.01416")
get_code_for_paper("1904.01416")
have("1904.01416")

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

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

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

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

Connect an agent — have() is free.