> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/section-02-using-velogic-studio/spark-lines.md).

# Spark Lines in the Fit Log

How to use spark lines to visualize changes in MotionMetriqs over the course of a fit

Sometimes it's useful to get a graphical indication of how a particular MotionMetriq has changed over the course of a fit, such as after you've completed a [sustainability test](/section-04-aero/sustainability-test.md).

Velogic Studio makes that easy through the use of a feature called "Spark Lines". To see a spark line, just click "SHOW GRID" to open the fit log grid, and then click on one or more body metrics.

You will see a series of lines displayed overtop of the fit log grid:

![Fit log grid displaying spark lines visualization with colored trend lines for selected metrics](https://11145950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-c0374b596fad48184cb099403040ec6e1f70dbf3%2Fspark-lines-grid-display.png?alt=media)

If a metric has left/right values, you will see a solid line for the left metric and a dotted line for the right.

You can click on multiple metrics and the lines will be automatically assigned different colors.

Simply click on the same metric again to turn the spark line off for that metric.


---

# 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.velogicfit.com/section-02-using-velogic-studio/spark-lines.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.