SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2211.15975 · 2022

Analyzing Infrastructure LiDAR Placement with Realistic LiDAR Simulation Library

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 3 have no contract verdict; 0 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/2211.15975.json · badge: /api/ran/2211.15975.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
pjlab-adg/lidarsimlib-and-placement-evaluation canonical (classifier label)
classifier basis not recorded on the link
3 ran · 0 no recorded run
FunctionStatusWhere it lives
load_point_pillar_params Ran
ran on a synthesized input
pjlab-adg/lidarsimlib-and-placement-evaluation/Placement-Evaluation/v2xvit/hypes_yaml/yaml_utils.py
code served (permissive licence) · get_code("0619a274e6eb1850")
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 math
import numpy as np

ARGS = {
    'param': {
        'preprocess': {
            'cav_lidar_range': [-50.0, -50.0, -5.0, 50.0, 50.0, 3.0],
            'args': {
                'voxel_size': [0.2, 0.2, 0.4]
            }
        },
        'model': {
            'args': {
                'point_pillar_scatter': {}
            }
        },
        'postprocess': {
            'anchor_args': {
                'feature_map_stride': 2,
                'out_size_factor': 2
            }
        }
    }
}
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
load_voxel_params Ran
ran on a synthesized input
pjlab-adg/lidarsimlib-and-placement-evaluation/Placement-Evaluation/v2xvit/hypes_yaml/yaml_utils.py
code served (permissive licence) · get_code("9bc229f7a9f4df89")
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
import numpy as np

torch.manual_seed(0)

ARGS = {
    'param': {
        'preprocess': {
            'args': {
                'voxel_size': [0.1, 0.15, 0.2]
            }
        },
        'postprocess': {
            'anchor_args': {
                'cav_lidar_range': [-51.2, -51.2, -5.0, 51.2, 51.2, 3.0]
            }
        },
        'model': {
            'args': {}
        }
    }
}
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 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_yaml Ran
ran on a synthesized input
pjlab-adg/lidarsimlib-and-placement-evaluation/Placement-Evaluation/v2xvit/hypes_yaml/yaml_utils.py
code served (permissive licence) · get_code("c40c6561b37d440c")
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 re
import yaml
import os
import tempfile

# Create a temporary YAML file for testing
temp_dir = tempfile.mkdtemp()
yaml_file = os.path.join(temp_dir, 'test_config.yaml')

# Write a simple YAML configuration
yaml_content = """
learning_rate: 0.001
batch_size: 32
epochs: 100
model_name: test_model
nested:
  param1: value1
  param2: 42
"""

with open(yaml_file, 'w') as f:
    f.write(yaml_content)

# Create a simple argparser-like object
class SimpleOpt:
    def __init__(self, model_dir=None):
        self.model_dir = model_dir

# Test with opt=None (uses the file parameter directly)
opt_none = None

# Test with opt that has model_dir set
opt_with_dir = None  # We'll use None for the primary test case

ARGS = {
    'file': yaml_file,
    'opt': opt_none
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
yaml — 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

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, 0 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
load_point_pillar_params 3 other papers
2 dated earlier, 1 later
2203.10638 (2022-03)
V2X-ViT: Vehicle-to-Everything Cooperative Perception with Vision Transformer
2210.08451 (2022-10)
Bridging the Domain Gap for Multi-Agent Perception
2307.13929 (2023-07)
Spatio-Temporal Domain Awareness for Multi-Agent Collaborative Perception
load_voxel_params 3 other papers
2 dated earlier, 1 later
2203.10638 (2022-03)
V2X-ViT: Vehicle-to-Everything Cooperative Perception with Vision Transformer
2210.08451 (2022-10)
Bridging the Domain Gap for Multi-Agent Perception
2307.13929 (2023-07)
Spatio-Temporal Domain Awareness for Multi-Agent Collaborative Perception
load_yaml 3 other papers
2 dated earlier, 1 later
2203.10638 (2022-03)
V2X-ViT: Vehicle-to-Everything Cooperative Perception with Vision Transformer
2210.08451 (2022-10)
Bridging the Domain Gap for Multi-Agent Perception
2307.13929 (2023-07)
Spatio-Temporal Domain Awareness for Multi-Agent Collaborative Perception

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

Recently, Vehicle-to-Everything(V2X) cooperative perception has attracted increasing attention. Infrastructure sensors play a critical role in this research field; however, how to find the optimal placement of infrastructure sensors is rarely studied. In this paper, we investigate the problem of infrastructure sensor placement and propose a pipeline that can efficiently and effectively find optimal installation positions for infrastructure sensors in a realistic simulated environment. To better simulate and evaluate LiDAR placement, we establish a Realistic LiDAR Simulation library that can simulate the unique characteristics of different popular LiDARs and produce high-fidelity LiDAR point clouds in the CARLA simulator. Through simulating point cloud data in different LiDAR placements, we can evaluate the perception accuracy of these placements using multiple detection models. Then, we analyze the correlation between the point cloud distribution and perception accuracy by calculating the density and uniformity of regions of interest. Experiments show that when using the same number and type of LiDAR, the placement scheme optimized by our proposed method improves the average precision by 15%, compared with the conventional placement scheme in the standard lane scene. We also analyze the correlation between perception performance in the region of interest and LiDAR point cloud distribution and validate that density and uniformity can be indicators of performance. Both the RLS Library and related code will be released at https://github.com/PJLab-ADG/PCSim.

For agents

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

get_harvested_code_for_paper("2211.15975")
get_code_for_paper("2211.15975")
have("2211.15975")

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

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

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

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

Connect an agent — have() is free.