> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/product-tour-web-app/geopard-mcp/clean-and-calibrate-yield-data.md).

# Clean and Calibrate Yield Data

Learn how to ensure statistically sound cleaning and calibration of your yield datasets by using an LLM with GeoPard MCP.

In this use case, we work with yield datasets to understand the distribution and quality of harvested data across the field. Using the connected GeoPard MCP, an LLM retrieves statistical summaries for the original yield dataset, detects irregularities or sensor noise, and identifies where cleaning or calibration is required.

Once the quality checks are complete, the LLM triggers the GeoPard MCP cleaning and calibration workflow with the optimal parameters.

{% hint style="success" %}
Ensure GeoPard MCP is connected before running this workflow. Setup details are provided [here](/geopard-tutorials/product-tour-web-app/geopard-mcp/connect-geopard-mcp.md).
{% endhint %}

## Single Yield Dataset

{% @arcade/embed url="<https://app.arcade.software/share/Zjf8Hpwf0Ykij1Dl5r4L>" flowId="Zjf8Hpwf0Ykij1Dl5r4L" %}

### Before

<figure><img src="https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FBTboCq739Ds6EWIoN8YI%2Fimage.png?alt=media&amp;token=d7b2b51d-a67b-43c1-9a57-7e9338abc93a" alt=""><figcaption></figcaption></figure>

### After

<figure><img src="https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FcIBWxG32gH31rkN45Cq9%2Fimage.png?alt=media&amp;token=970b3cd3-1a7c-438d-bac0-a2db73d146de" alt=""><figcaption></figcaption></figure>

## Batch Yield Dataset Calibration

{% @arcade/embed url="<https://app.arcade.software/share/bibREyFI1hqQvPk7rBFq>" flowId="bibREyFI1hqQvPk7rBFq" %}

### Before

<figure><img src="https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FUATNQLP0u88zsnlLkAAm%2Fimage.png?alt=media&amp;token=a85329be-0cb9-4c38-88c5-8b591638edf9" alt=""><figcaption></figcaption></figure>

### After

<figure><img src="https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2Fimu4ak8G06puVVlpSS6w%2Fimage.png?alt=media&amp;token=51ec2b97-fa4e-403a-af7c-e68506a872c7" alt=""><figcaption></figcaption></figure>


---

# 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.geopard.tech/geopard-tutorials/product-tour-web-app/geopard-mcp/clean-and-calibrate-yield-data.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.
