> 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-and-portfolio-management/ath-drawdown/faqs.md).
# FAQs
ATH Drawdown FAQs
Does this repaint?
No. The series is based on a running maximum (ATH) and current price. It will update intra-bar as price moves (like any real-time series), then fix at bar close. There is no look-ahead.
Why did my drawdown change after switching symbols or loading more history?
ATH is computed from the first available bar on your chart. Different symbols/exchanges or added history can reveal an earlier/higher ATH, changing the baseline. Use the feed with the most complete history for consistency.
Close vs. High—what should I choose?
Close anchors ATH to settled prices (more conservative, fewer false peaks). High includes wicks, catching fleeting spikes—useful for identifying maximum extremes but more sensitive to noise.
What thresholds define a “deep” drawdown?
There’s no universal rule. Many high-volatility assets historically see −60% to −80% during major cycles, but you should calibrate bands to your asset class and risk model.
How do I reduce noisy alerts?
Set alerts to Once per bar close, use a higher timeframe, add a small EMA smoothing length (e.g., 3–8), or widen your alert band (e.g., −72% to −78% instead of −70% to −80%).
---
# 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-and-portfolio-management/ath-drawdown/faqs.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.