> 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/3559.md).

# 3559 - MODELING LIGHT DETECTION AND RANGING (LIDAR) RESPONSE IN SNOWY ENVIRONMENTS

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

**Authors:** *Brian Brady, Aaron Meyer, Sergey Vecherin, Mike Parker*

**Keywords:** LiDAR; snow; simulation; autonomous; vehicle

**Abstract:**

The sensors used by a robust, off-road autonomous vehicle must be capable of detecting obstacles in any weather conditions, but this becomes especially important during inclement weather with reduced visibility. Snowfall is no exception to this and poses extremely challenging conditions to vehicles exclusively employing Light Detection and Ranging (LiDAR) systems for object detection. Snowflakes may occlude “hard” targets in the vehicle’s path of travel or introduce noise from “soft” detections of the snowflakes themselves. This study highlights preliminary results from a simulation that reproduces these effects within the U.S. Army Corps of Engineers’ Virtual Autonomous Navigation Environment (VANE). The simulation accurately models snowflake size, concentration, and velocity while accounting for sensor-specific modes of operation. VANE simulations provide vehicle designers with a rapid and affordable method to evaluate LiDAR perception and autonomy response in snowy conditions.


---

# 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/3559.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.
