> 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-valuation-and-on-chain/mayer-multiple-z-score/faqs.md).

# FAQs

Mayer Multiple Z-score FAQs

<details>

<summary>What is the Mayer Multiple here?</summary>

It’s `price ÷ SMA` using your chosen length (default 200). The script then converts that ratio into a Z-Score based on your undervalue/overvalued mapping.

</details>

<details>

<summary>Why use a cumulative-to-rolling SMA?</summary>

Early bars shouldn’t pretend you have a full 200-bar history. The average grows honestly until the lookback is filled, then behaves like a standard SMA—clean and non-repainting.

</details>

<details>

<summary>Do any plots repaint?</summary>

No. The SMA, Z-Score, and its EMA use completed historical data. Values only change intrabar while the bar is forming, then lock after close.

</details>

<details>

<summary>How should I pick the thresholds (0.5 / 2.0)?</summary>

Keep the span at roughly **6σ** for comparability; move the endpoints to match asset class. Higher-vol assets may warrant a higher “overvalued” multiple (e.g., 2.5) and/or a lower “undervalue” multiple.

</details>

<details>

<summary>Will bar coloring affect performance or visibility of other indicators?</summary>

Barcolor is purely visual; if it clashes, disable `Bar Color` and keep the Z-Score/EMA plots and fills as your primary cues.

</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-valuation-and-on-chain/mayer-multiple-z-score/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.
