> For the complete documentation index, see [llms.txt](https://docs.motivewave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motivewave.com/knowledge-base/charts/trend-lines-dont-line-up-on-different-bar-sizes.md).

# Trend Lines Don't Line up on Different Bar Sizes

When you draw a trend line it needs to have two anchor points. A start time and price and an end time and price. If you draw a trend line on a higher time frame like daily bars they do not contain detailed information on what time the high and low happened within that daily bar, you only know the time of the open and the close.

In the example below we have a trend line drawn on daily bars from the low of March 28 to the low of April 5. Since we are using daily bars we can’t attach an exact time to the start of the trend line, so we assign it to the open of the day. Remember the only times we can assign are either the open or the close.

![](/files/-MJ-6aMg_rm671xRVWMo)

Once we change to a 1 hour bar size you can see the trend line doesn’t appear to line up anymore. This is because the trend line is being drawn from the open on March 28 at the low price of the day all the way to the open of April 5 at the low price of the day.

![](/files/-MJ-6giof2AurTZoWgw0)

This applies to other chart drawings including Elliott Wave components.


---

# 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://docs.motivewave.com/knowledge-base/charts/trend-lines-dont-line-up-on-different-bar-sizes.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.