> 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/investing/momentum-and-oscillators/momentum-pulse/faqs.md).

# FAQs

Momentum Pulse FAQs

<details>

<summary>Does the gradient repaint or shift after the bar closes?</summary>

No. Colors are derived from current momentum and its stdev over the chosen length; values settle at bar close like any standard indicator.

</details>

<details>

<summary>My gradient looks too “hot” or too “cold”—what should I change first?</summary>

Adjust the Multiplier (k). Raise k to widen the color range (less “hot”); lower k to tighten it (more sensitive heat).

</details>

<details>

<summary>How do I pick good Level 1/Level 2 values?</summary>

Scan history: set L1 to catch routine pushes and L2 to capture true thrusts. If L2 triggers too often, increase it; if almost never, decrease it.

</details>

<details>

<summary>What’s the difference between the two MAs?</summary>

“Normal MA” = SMA(close,len); “Smoothed MA” = SMA(src,len). The latter tracks the blended source used by the momentum calculation and typically reduces noise.

</details>

<details>

<summary>Can I use this intraday?</summary>

Yes. The log math is time-scale agnostic. For choppy intraday names, increase Length and/or k, and rely more on L2 and the zero-line to avoid over-trading.

</details>


---

# 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/investing/momentum-and-oscillators/momentum-pulse/faqs.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.
