Skip to content

Outputs

When Tolosa has run, one can verify that the expected outputs were created. Here, the /res repertory structure shoud be the following :

/res
    /bin
    /vtk
    /savefield_1d
    /savefield_2d
        /Window_1
        /Window_2

One can verify that all outputs were generated by checking the correspondance of this repertory structure and the input files input.txt and savefield.yaml (see Inputs).

One dimensional outputs

The specific 1D outputs are defined in the savefield.yaml file and are stored in the /savefield_1d directory. Here, all the outputs are stored in .csv files :

/savefield_1d
    TIDE_G_1.csv
    TIDE_G_2.csv
    TIDE_G_3.csv
    TIDE_G_4.csv

Info

These .csv files will be post-treated with PyTolosa.

Two dimensional outputs

VTK files

VTK files were generated in /vtk and in /savefield_2d/Window_1 since they were requested in the input.txt and savefield.yaml file (see Inputs). Each VTK file contains the state of the domain at each time step.

a. Entire domain

To get the state of the entire domain in VTK files, one has filled the input.txt file in Inputs by adding w_vtk = 1. At each timestep, Tolosa-sw has written the sea surface height, the domain bathymetry, and the vertical and horizontal speed components values at each cell.

In the vtk directory contains only the VTK files : 

/vtk
    result_000000.vtk
    ...
    result_XXXXXX.vtk

To access to the simulations results from these VTK files, one can use Paraview. For example, one can display the sea surface height of the entire domain at a specific time step and see its evolution by importing the files bundle into the software :

[IMAGE VTK RESULTS]

b. Subdomain

On the other hand, the VTK files in /savefield_2d/Window_1 are displaying the state of the subdomain Window_1 defined in the savefield.yaml file. 

/savefield_2d
    /Window_1
        Window_1_000000.vtk
        ...
        Window_1_XXXXXX.vtk

In our case, we chose to extract the default variables, i.e. the sea surface height, the bathymetry and the vertical and horizontal speed components. As before, the simulations results can be displayed by using Paraview.

[IMAGE VTK RESULTS]

Info

If one had chosen to get other simulation results in VTK files in another Window_X, another /Window_X directory would have been created in the /savefield/vtk directory.

Binary files

Binary files were generated in /bin and in /savefield_2d/Window_2 since they were requested in the input.txt and savefield.yaml file (see Inputs).

Info

For information, one can choose to generate a bundle of binary files each describing the state of the domain at each time step or to generate a unique binary file containing the results of all the time steps. See Tolosa-sw / Inputs.

a. Entire domain

In the /bin directory, all the binary files were generated at the frequency defined in input.txt. Here, the fields distribution is written for the entire domain. The structure of the /bin directory should be the following : 

/bin
    result_data_000001.bin
    ...
    result_data_XXXXXX.bin
    result_data_minmax.txt
    result_gmsh_element.bin
    result_info.txt
    result_mesh.bin
    result_lon_lat_degrees.bin
    result_lon_lat_radians.bin
  • result_info.txt summarizes all the informations contained in the binary output files.
  • result_mesh.bin encapsulates the mesh connectivity to link data to the mesh nodes.
  • result_gmsh_element.bin contains the global index of the mesh cells as defined in GMSH.
  • result_lon_lat_degrees.bin contains the nodes coordinates in longitude and latitude (degrees)
  • result_lon_lat_radians.bin contains the nodes coordinates in longitude and latitude (radians)
  • result_data_000001.bin to result_data_XXXXXX.bin are the output files with the fields values at each cell.
  • result_data_minmax.txt contains the minimum and maximum values of each field at each time step.

Info

More details concerning those files and their post-treatment with PyTolosa will be handed in the Post-treatment section.

b. Subdomain

In the /savefield_2d/Window_2 directory, all the binary files were generated at the frequency and in the subdomain defined in savefield.yaml. The structure of the /Window_2 directory should be the following : 

/savefield_2d
    /Window_2
        Window_2_data_000000.bin
        ...
        Window_2_data_XXXXXX.bin
        Window_2_data_minmax.txt
        Window_2_gmsh_element.bin
        Window_2_info.txt
        Window_2_mesh.bin
        Window_2_lon_lat_degrees.bin
        Window_2_lon_lat_radians.bin

The informations concerning the directory structure, the files and their post-treatment are the same as in the previous paragraph.

Back to top