# Inference Model Output

### Updates to other files

### \LLIK (inference runs only)

During inference runs, an additional file type, `llik`, is created, which is described in the [Inference Model Output](/flepimop/model-inference/inference-model-output.md) section ;

These files contain the log-likelihoods of the model simulation for each subpopulation, as well as some diagnostics on acceptance.

The meanings of the columns are:

`ll` - These values are the log-likelihoods of data given the model and parameter values for a single subpopulation (in `subpop` column) ;

`filename` - ...

`subpop` - The values of this column are the names of the nodes from the `geodata` file.

`accept` - Either 0 or 1, depending on whether the parameters during this iteration of the simulation were accepted (1) or rejected (0) in that subpopulation ;

`accept_avg` ;

`accept_prob` ;

For inference runs, `...` *flepiMoP* produces one file per parallel slot, for both global and chimeric outputs...

```
flepiMoP/examples/tutorials
├── model_output
│   ├── seir
│   ├── spar
│   ├── snpi
│   └── llik
│       └── sample_2pop
│           └── None
│               └── 2023.05.24.02/12/48.
│                   ├── chimeric
│                   └── global
│                       ├── final
│                       │   └── 000000001.2023.05.24.02/12/48..llik.parquet
│                       └── intermediate
│                           └── 000000001.000000001.2023.05.24.02/12/48..llik.parquet
```


---

# 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://iddynamics.gitbook.io/flepimop/model-inference/inference-model-output.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.