> For the complete documentation index, see [llms.txt](https://support.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.tiger.com/english/windows/chart/main-indicators-in-chart-window/heatmap.md).
# Heatmap
The indicator shows data changes in the DOM.
It has minimum and maximum volumes, the basic ask and bid colors, and the colors of asks and bids that exceed the maximum volumes.
If the volume of the limit level in the DOM is between the minimum and maximum, the price level color is proportional to the volume. If the volume of the limit level exceeds the maximum, the price level will be the maximum volume color.
This indicator is best used for tick charts with a value of 1, where every bar (tick) stands for a separately aggregated trade.
### Indicator settings
#### 
#### Parameters
| **Name** | **Description** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Depth of market | Changes the DOM |
| Expanded DOM | Extends levels from the current price to the price scale. |
| Color map | Visualization settings for volume in the indicator. |
| Lower cutoff % | Corresponds to the upper cutoff.
|
| Lower cutoff V | Minimum volume. Levels with order volumes lower than the minimum value will not be displayed.
|
| Upper cutoff %
| Let’s say the maximum volume permitted in the visible range is 1000. We can also say there’s a level with volume 800.
If the cutoff is 0, the color for that level is 80% of the maximum color in the gradient.
If the value is 20%, the maximum volume will be 1000 - 20% = 800. In that case, levels with volume 800 will be the maximum volume color.
|
| Upper cutoff V | The maximum volume. If the order volume exceeds the maximum, the price level will be the maximum volume color. |
| Contrast | Controls the contrast between the levels on display.
|
| Large volumes | Sets the maximum value for every bar, with the last value in each bar taken the moment it is closed if this is not checked. |
| Brightness | Filters levels from smallest to largest. The higher the brightness, the easier it is to see weak levels.
|
#### Indicator
| **Name** | **Description** |
| --------- | ------------------------------------------------------------------------- |
| Indicator | Enabling or disabling the indicator display on the chart. |
| Name | Enabling or disabling the indicator name display in the information line. |
| Area | Selection of an area to display the indicator. |
---
# 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://support.tiger.com/english/windows/chart/main-indicators-in-chart-window/heatmap.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.