> 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/risk-adjusted-performance/monthly-return-heatmap/faqs.md).

# FAQs

Monthly Return Heatmap FAQs

<details>

<summary><strong>Why does the indicator show an error or warning on my chart?</strong></summary>

This indicator requires the chart to be set to the 1M (Monthly) timeframe to calculate returns correctly. If you are on a Daily, Weekly, or intraday timeframe, a warning will be displayed. Change your chart timeframe to 1M.

</details>

<details>

<summary><strong>What is the difference between Geo YTD and Ari YTD?</strong></summary>

Geo YTD (Geometric Year-to-Date) calculates the compounded return over the year, which is the true return on investment. Ari YTD (Arithmetic Year-to-Date) simply adds the percentage returns of each month together. Geo YTD is generally more accurate for measuring actual portfolio performance.

</details>

<details>

<summary><strong>Can I use this indicator on any asset?</strong></summary>

Yes, the Monthly Returns Heatmap can be applied to any asset available on TradingView, including stocks, cryptocurrencies, forex, and commodities, provided there is enough historical data.

</details>

<details>

<summary><strong>How far back does the heatmap look?</strong></summary>

You can configure the indicator to display up to 30 years of historical monthly data, depending on the data availability for the specific asset on TradingView.

</details>

<details>

<summary><strong>Does this indicator provide buy or sell signals?</strong></summary>

No, this indicator is a visual analysis tool designed to show historical seasonality and performance. It does not provide automated buy or sell alerts and should be used as part of a broader trading strategy.

</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/risk-adjusted-performance/monthly-return-heatmap/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.