# Output files

The APM Solver and Preprocessor can output files in **.csv**, **.vtu**, and **.dat** file formats. The **.csv** files can be opened with any text editor or data processing software such as [MATLAB](https://www.mathworks.com/products/matlab.html) or [RStudio](https://rstudio.com/). The **.vtu** files are specific to [ParaView](https://www.paraview.org/). ParaView is an open-source, multi-platform data analysis and visualization application which can be downloaded from <https://www.paraview.org/download/>. The **.dat** files are specific to [Tecplot](https://www.tecplot.com/). Tecplot is the name of a family of visualization & analysis software tools developed by Tecplot, Inc.&#x20;

To enable or disable ParaView or Tecplot output change the `paraview_output` and `tecplot_output` options in the **.conf** file.

![](/files/-MWGzl2rabRTFvnEzpbh)

## Output file descriptions

| File                                                             | Description                                                                                                                                                                                                                |
| ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<name>\_body\_panels.vtu</p><p>\<name>\_body\_panels.dat</p> | Files in **.vtu**, or **.dat** file formats which contain the source strengths, doublet strengths, reference velocities, relative velocities and the pressure coefficient of the body elements. Created by the APM Solver. |
| <p>\<name>\_wake\_panels.vtu</p><p>\<name>\_wake\_panels.dat</p> | Files in **.vtu**, or **.dat** file formats which contain the doublet strengths of the wake elements. Created by the APM Solver.                                                                                           |
| \<name>.loads                                                    | File in space delimited file format which contains the integrated loads of the body. Created by the APM Solver.                                                                                                            |
| \<name>.mdl                                                      | File in space delimited file format which contains the element types, vertices, and neighbours. Created by the APM preprocessor and used by the APM Solver.                                                                |
| \<name>.checkpoint                                               | File in binary file format which contains the latest solution. Created by the APM Solver.                                                                                                                                  |

The structure of an example **.loads** file is shown below:

```
Timestep Time CFx CFy CFz CMx CMy CMz CL CD CC
0 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000
1 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000
2 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000
3 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000 0.0000000000
...
```


---

# 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://docs.aviumtechnologies.com/user-guide/output-files.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.
