> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/oscillators/momentum-concepts/momentum-wave.md).
# Momentum Wave
The **Momentum Wave** is the heartbeat of the indicator. It uses Ehlers SuperSmoother technology and Exponential Smoothing to create a "Lag-Less" momentum line.
### Calculation Logic
1. **ESA Baseline**: Calculates an Exponential Smoothed Average of the Typical Price.
2. **Cycle Identification**: Extracts the cyclical components of price movement.
3. **SuperSmoothing**: Applies a 2-pole Butterworth filter to eliminate aliasing and market noise without introducing significant lag.
4. **Soft Limiting**: Compresses extreme values (Hard-Capped at ±70) to keep the oscillator readable even during parabolic moves.
### Interpretation
* **Bullish Wave (Color 1)**: The wave is rising and above its signal line. Trend is positive.
* **Bearish Wave (Color 2)**: The wave is falling and below its signal line. Trend is negative.
* **Mid-Line (0)**: The equilibrium point. Crosses indicate a flip in trend direction.
* **Intensity Heatmap**: The background zones (OB/OS Boxes) change in transparency based on **Volatility-Momentum Intensity**, showing you where the wave is under the most pressure.
---
# 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://docs.candelacharts.com/oscillators/momentum-concepts/momentum-wave.md?ask=&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.
