> For the complete documentation index, see [llms.txt](https://ibjects-app.gitbook.io/intuitiveai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ibjects-app.gitbook.io/intuitiveai/exploring-generated-data.md).

# Exploring Generated Data

In the previous section, we discussed how the stimulator is coded and how the game is played the rules,  and everything related to the IntuitiveAI stimulator. If you have played with the stimulator you understand how it works and we now have three main goals that we will be solving in the experiments with dataset section but will discuss the theory part here.

With the data, we have three goals in mind. When we explore the dataset you are required to keep these three goals in mind:

1. Predict the first box user will open when they start a new game.
2. Predict the next box use will open at any given position in a game
3. Predict the overall outcome of a game
4. Predicting if a game is won or lost using intuition or calculated moves

To elaborate on number 4, we use UserGamePlayPattern and see if there is a big jump we can say that it was intuition-based as the user took a risk.

The goal is to present the data first. I wanted to create a visualization that is more or less like the image below:


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ibjects-app.gitbook.io/intuitiveai/exploring-generated-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.