> For the complete documentation index, see [llms.txt](https://docs.verge.aero/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.aero/drone-show-software/verge-design-studio/light-animation/pulse.md).

# Pulse

A smooth, repeating rise and fall in light intensity over time.

| Parameter | Type    | Description                                                                                                                                                                                                                                                                                                                                                                                            |
| --------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Unit Type |         | <p>Hz - the strobe or modulation rate in cycles per second. Higher Hz values produce faster, more intense flickering, while lower values create slower, more deliberate pulses.<br><br>BPM - the strobe or modulation rate in musical beats per minute. This allows lighting effects to synchronize naturally with music or rhythmic cues, aligning pulses to the tempo of a track or performance.</p> |
| Unit      | Decimal | amount applied to the unit type                                                                                                                                                                                                                                                                                                                                                                        |

<figure><img src="/files/Xidmol8OjQKAE9mkMNkb" alt="" width="353"><figcaption><p>Inspector for pulse lighting event</p></figcaption></figure>

<figure><img src="/files/iCreuQnwNsvYhGZVsYWk" alt="" width="375"><figcaption><p>Pulse lighting event</p></figcaption></figure>

A pulse lighting event is modeled as a sine wave because a sine function produces a smooth, continuous rise and fall over time, which matches how a pulse is intended to behave visually.

In this context, light intensity is mapped to the value of a sine wave as time progresses:

* The crest of the sine wave represents peak intensity.
* The trough represents minimum intensity.
* The zero crossings define the midpoint or base intensity.

As time advances, the sine wave oscillates, causing the light to gradually brighten, reach a maximum, then smoothly dim and repeat. This avoids abrupt transitions and hard edges, producing an organic, rhythmic motion often described as a “breathing” effect.

Because sine waves are mathematically smooth and periodic, they are ideal for pulse lighting events that need consistent timing, predictable behavior, and visually pleasing transitions without flicker.

<figure><img src="/files/10wnqLovmtGkEsSURbdc" alt="" width="375"><figcaption><p>Sin wave</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verge.aero/drone-show-software/verge-design-studio/light-animation/pulse.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
