> For the complete documentation index, see [llms.txt](https://quantify-crypto.gitbook.io/the-quantify-crypto-trend-algorithm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quantify-crypto.gitbook.io/the-quantify-crypto-trend-algorithm/quantify-crypto-trend-time-frames.md).

# Quantify Crypto Trend Time Frames

| Name     | Candlestick      | Minutes | Hours | Days     |
| -------- | ---------------- | ------- | ----- | -------- |
| Spot     | 5                | 2500    | 41.67 | 1.736111 |
| Short    | 15               | 7500    | 125   | 5.208333 |
| Medium   | 30               | 15000   | 250   | 10.41667 |
| Critical | 60               | 30000   | 500   | 20.83333 |
| Long     | 120              | 60000   | 1000  | 41.66667 |
| Mean     | Average of above | 60000   | 1000  | 41.66667 |

 

To give an example, the “Short” *QC Trend algorithm* uses 15-minute candlesticks. When using a three period EMA, it would calculate using the trading history of the most recent 45 minutes, performing a calculation based on three 15-minute time periods. The same three period EMA calculation using the “Critical” QC Trend algorithm would use the three most recent one-hour time periods.  Each *QC Trend algorith*m using multiple EMA crossovers periods.   The "Short" *QC Trend algorithm*, has a historic look back period 125 hours when processing the past 11 EMA comparison price points.

Each *QC Trend algorith*m using multiple EMA crossovers periods.

The trend mean score uses a weighted average of the 5 trend time periods in the chart.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://quantify-crypto.gitbook.io/the-quantify-crypto-trend-algorithm/quantify-crypto-trend-time-frames.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.