> 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/api-docs/diagrams-with-basic-flows/5.-execute-equations.md).
# 5. Execute Equations
The Execute Equations sequence diagram illustrates the process of performing Equations within the GeoPard solution.
Typically, it is recommended to use pre-saved Equations from the account or organization level. An Equation invariably contains links to other datasets, such as the SoilDataset, AsAppliedDataset, YieldDataset, SatelliteImage, and so on. Attributes from these linked datasets serve as variables within the equation, indicating that dataset details are gathered beforehand. The most commonly used datasets are SoilDatasets ([Request 1 or R1](/geopard-tutorials/api-docs/geopard-api-requests-overview/17.-query-get-soildatasets.md)), AsAppliedDataset ([Request 1 or R1](/geopard-tutorials/api-docs/geopard-api-requests-overview/59.-query-get-asapplieddatasets.md)), and YieldDataset ([Request 1 or R1](/geopard-tutorials/api-docs/geopard-api-requests-overview/16.-query-get-yielddatasets.md)).
The Equation execution is initiated asynchronously. The first request triggers the execution of the Equation and returns UUIDs that identify the corresponding EquationMap ([Request 2 or R2](/geopard-tutorials/api-docs/geopard-api-requests-overview/75.-mutation-generate-equationmap-asynchronously.md)). The summary of this execution is delivered via GraphQL subscription events via WebSocket ([Request 3 or R3](/geopard-tutorials/api-docs/geopard-api-requests-overview/1.-subscription-get-events.md)). Upon delivery of the event, the GeoPard API consumer can fetch information such as metadata, statistics, and geometries ([Request 4 or R4](/geopard-tutorials/api-docs/geopard-api-requests-overview/76.-query-get-equationmap.md)).
The GeoPard event-driven architecture ensures a robust, efficient, and responsive system for executing equations and retrieving their results.
Sequence diagram: Execute Equation
---
# 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/api-docs/diagrams-with-basic-flows/5.-execute-equations.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.
