> For the complete documentation index, see [llms.txt](https://docs.irs.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.irs.systems/report-analyzer/documentation/manual/graph-comparison.md).
# Graph Comparison
#### YY Diagram
In the History & Statistics module, graphs for the same measurement from different groups can already be compared. The "Graph Comparison" module also offers the possibility to compare any measurements within the same group. This is helpful, for example, if the measurements are similar to each other, but were taken at different measurement points.
**Procedure**
1. Select the desired group and click on **New YY Diagram**
2. Rename the title if necessary:
3. Drag the desired measurement from the "ID" column in the graphs near the Y-axis When a green solid vertical bar appears, release the mouse button. The measurement series is added to the graph:
4. Repeat step 3 until all desired graphs are included in the diagram:
5. After adding three measurement series our example now looks like this
6. Each graph has an additional Y-axis. If all values are in a similar range, you should activate **Single Y-Axis**:
#### XY Diagram
For an X-Y diagram, proceed in the same way, but here one measurement is drawn to the X-axis and a second to the Y-axis. The resulting X/Y values are entered as points:
---
# 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.irs.systems/report-analyzer/documentation/manual/graph-comparison.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.
