> For the complete documentation index, see [llms.txt](https://2025.istvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://2025.istvs.org/submissions/papers/8969.md).

# 8969 - SURVEY OF LIDAR EFFECTS FOR AUTONOMOUS DRIVING SIMULATIONS

{% hint style="info" %}
Paper presented at ISTVS 2025 | 55th Conference of the International Society for Terrain-Vehicle Systems <https://doi.org/10.56884/O5B2MXY7>
{% endhint %}

**Authors:** *John Kaniarz, Brian Brady, Laura Walizer, Phillip Price, Mike Parker*

**Keywords:** LiDAR; simulation; autonomous; fidelity

**Abstract:**

A wide variety of software packages are available for modeling Light Detection and Ranging (LiDAR) sensors in the context of autonomous driving simulations. This report highlights ten effects that a high-fidelity LiDAR simulation should be capable of delivering. Examples are provided from real-world data collected in the field, synthetic results generated in simulation, and published literature. Simulation users must carefully consider performance versus fidelity tradeoffs when selecting a suitable LiDAR simulation package for use


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://2025.istvs.org/submissions/papers/8969.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
