> 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/multi-asset-monthly-returns-heatmap/usage.md).

# Usage

Multi-Asset Monthly Returns Heatmap Usage

By simultaneously comparing up to 28 assets, you can spot structural market rotations and intermarket trends. 

Here is how to incorporate this multi-asset data into your strategy:

1. **Set Timeframe**: Ensure your chart is set to the **1M (Monthly)** timeframe. A warning will appear if you are on a lower timeframe.
2. **Customize Your Basket**: In the settings, input your desired target ticker symbols for up to 28 assets. You can also customize the display names for cleaner table visualization.
3. **Select Calculation Mode**: Choose the statistical metric that fits your analysis. Use 'Mean' or 'Median' for average expected returns, 'Volatility' for risk assessment, or 'Max'/'Min' to see historical extremes.
4. **Identify Seasonality**: Spot structural seasonal trends across markets. For example, you might observe that certain agricultural commodities consistently perform well in Q2, while specific equity indices show strength in Q4.
5. **Compare Assets**: Quickly compare the historical average monthly performance of different asset classes side-by-side to inform asset allocation decisions.


---

# 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/multi-asset-monthly-returns-heatmap/usage.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.