# Data Locations

## :open\_file\_folder: Folders and Files Generated by SLM Lab

Now that we know how to run SLM Lab, let's see how to interpret the data it produces.

As a run (Session, Trial, or Experiment) completes, its data is saved to the `data/` folder with an identifying **spec name** appended with a timestamp, e.g. `ppo_lunar_2019_11_30_002958`. The folder is also automatically zipped for convenient file transfer. A lab data folder is organized as follows:

```
slm_lab/data/
  ppo_lunar_2019_11_30_002958/
    graph/    # all the plotted graphs for Session, Trial, Experiment
    info/     # all the data: metrics and evaluation dataframes, etc.
    log/      # log files
    model/    # PyTorch model weights
    *graphs   # important graphs from graph/ for easy access
    *metrics  # important metrics from info/ for easy access
    *specs    # important specs from info/ for easy access
```

The data files are generated mostly by the lab's [analysis module](https://github.com/kengz/SLM-Lab/blob/master/slm_lab/experiment/analysis.py), with self-explanatory names. For most purposes, we are interested in the graphs and metrics files saved directly under the data folder produced by a run. Next, we will look at how to make use of these data files to interpret the lab results corresponding to the [Lab Organization](/slm-lab/master/using-slm-lab/lab-organization.md).


---

# Agent Instructions: 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:

```
GET https://slm-lab.gitbook.io/slm-lab/master/analyzing-results/analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.