POSTPROCESS DATA FILES

In GiD Postprocess you can study the results obtained from a solver program. The solver and GiD Postprocess communicate through the transfer of files. The solver program has to write the results to a file that must have the extension .post.res, or the old .flavia.res, and its name must be the project name.

The solver program can also send the postprocess mesh to GiD (though this is not mandatory), where it should have the extension .post.msh, or the old version .flavia.msh. If this mesh is not provided by the solver program, GiD uses the preprocess mesh in Postprocess.

The extensions .msh and .res are also allowed, but only files with the extensions .post.res or .flavia.res - and potentially .post.msh or .flavia.msh - will automatically be read by GiD when postprocessing the GiD project.

Postprocessing data files are ASCII files, and can be separated into two categories:

Note: ProjectName.post.msh, or the old ProjectName.flavia.msh, handles meshes of different element types: points, lines, triangles, quadrilaterals, tetrahedra and hexahedra. The old format, which only handles one type of element per file, is still supported inside GiD (see Old postprocess mesh format ).

If a project is loaded into GiD, when changing to GiD Postprocess it will look for ProjectName.post.res, or the old ProjectName.flavia.res. If a mesh information file with the name ProjectName.post.msh, or the old ProjectName.flavia.msh is present, it will also be read, regardless of the information available from GiD Preprocess.

The files are created and read in the order that corresponds to the natural way of solving a finite element problem: mesh, surface definition and conditions and finally, evaluation of the results. The format of the read statements is normally free, i.e. it is necessary only to separate them by spaces.

Thus, files can be modified with any format, leaving spaces between each field, and the results can also be written with as many decimal places as desired. Should there be an error, the program warns the user about the type of mistake found.

GiD reads all the information directly from the preprocessing files whenever possible in order to gain efficiency.