> 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/market-structure-and-rotation/investor-tool/faqs.md).

# FAQs

Investor Tool FAQs

<details>

<summary>How is the MA length computed across different timeframes?</summary>

`ma_length = years × bars_per_year`, where bars/year adapts to the chart: Daily≈365, Weekly≈52, Monthly≈12, Intraday≈252. Your “2 years” remains time-comparable across TFs.

</details>

<details>

<summary>Do WVAPs repaint?</summary>

They’re **cumulative within the active anchor** and **reset at the new anchor** (e.g., new Month/Quarter/Year). They update as new bars arrive but don’t revise completed anchor history after the bar closes.

</details>

<details>

<summary>My WVAP didn’t reset—why?</summary>

Resets occur only when the platform detects a true boundary via `timeframe.change(...)`. If your anchor is Year but you’re on a custom/time-compressed dataset, ensure the chart has full calendar continuity and that the selected anchor granularity is supported on that symbol.

</details>

<details>

<summary>Can I use this on symbols with little or no volume (indices, some CFDs, synthetics)?</summary>

Yes—**Investor MA** and **bands** work normally because they use price only. However, **WVAPs** depend on volume; on symbols without reliable volume they may be `na` or noisy. In that case, disable WVAPs and rely on MA + bands (and anchors on higher-quality proxies, if needed).

</details>

<details>

<summary>Do the MA and bands repaint or change after the bar closes?</summary>

No. The MA (`ta.sma`) and bands (`± multiplier × stdev`) use only past data and **do not repaint** once a bar closes. They will look different when you **change timeframe** because `bars_per_year` adjusts (Daily≈365, Weekly≈52, etc.), and early bars can be `na` until the lookback fills—both expected behavior, not repainting.

</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/market-structure-and-rotation/investor-tool/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.
