> 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/bg/produktova-obikolka-ueb-prilozhenie/geopard-mcp/pochistvane-i-kalibrirane-na-dannite-za-dobiv.md).

# Почистване и калибриране на данните за добив

Научете как да осигурите статистически издържано почистване и калибриране на вашите набори от данни за добив, като използвате LLM с GeoPard MCP.

В този случай на употреба работим с набори от данни за добива, за да разберем разпределението и качеството на прибраните данни в целия блок. Използвайки свързания GeoPard MCP, LLM извлича статистически обобщения за първоначалния набор от данни за добива, засича нередности или шум от сензора и определя къде е нужно почистване или калибриране.

След като проверките на качеството приключат, LLM стартира работния процес на GeoPard MCP за почистване и калибриране с оптималните параметри.

{% hint style="success" %}
Уверете се, че GeoPard MCP е свързан, преди да стартирате този работен процес. Подробности за настройката са предоставени [тук](/geopard-tutorials/bg/produktova-obikolka-ueb-prilozhenie/geopard-mcp/svrzvane-na-geopard-mcp.md).
{% endhint %}

## Единичен набор от данни за добива

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

### Преди

<figure><img src="https://190376946-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>

### След

<figure><img src="https://190376946-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>

## Пакетно калибриране на набори от данни за добива

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

### Преди

<figure><img src="https://190376946-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>

### След

<figure><img src="https://190376946-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/bg/produktova-obikolka-ueb-prilozhenie/geopard-mcp/pochistvane-i-kalibrirane-na-dannite-za-dobiv.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.