> For the complete documentation index, see [llms.txt](https://docs.tychos.org/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tychos.org/docs/learn/video-guides/untitled.md).

# Video Tutorial: Graphs and Bar Charts

{% hint style="warning" %}
This page is **out of date** and does not accurately represent the current user interface nor recent changes that we have made to the Tychos language. We are in the process of updating all of our documentation. Thank you for your patience!
{% endhint %}

Graphing is an incredibly powerful way to analyze the behavior of your simulation and one of the great tools offered as part of the application is the ability to easily plot points on a graph (or graphs!) With just a couple of lines of code, you can easily generate a motion graph, or really any graph for your simulation.

{% embed url="<https://vimeo.com/242511788>" %}
Learn how to use Graphs.
{% endembed %}

{% hint style="info" %}
This video is currently out of date due to some interface improvements. We hope to update this video soon! Thanks for your patience.
{% endhint %}


---

# 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.tychos.org/docs/learn/video-guides/untitled.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.