Now that we have the mesh file compatible with Nektar++ and periodic boundary conditions,
ADR_mesh_aligned.xml
, and we have completed the condition file, ADR_conditions.xml
, we
can run the solver by using the following command:
$NEK/ADRSolver ADR_mesh_aligned.xml ADR_conditions.xml
As soon as the file finishes running, we should see the following screen output:
where the L2 and L inf errors are evaluated against the <FUNCTION NAME="ExactSolution">
provided in the ADR_conditions.xml
file. To have a more detailed view on the solver settings
and parameters used, it is possible to use the -v
option (which stands for verbose) as follows:
ADRSolver
with the verbose option:
$NEK/ADRSolver -v ADR_mesh_aligned.xml ADR_conditions.xml
The simulation has now produced 11 .chk
binary files and a final .fld
binary file (which in
this case is identical to the tenth .chk
file). These binary files contain the result of the
simulation every 100 time-steps. This output interval has been chosen through the parameter
IO_CheckSteps
in ADR_conditions.xml
, which was set equal to 100. Also, it is
possible to note that every 100 time-steps the solver outputs the physical time of the
simulation and the CPU time required for doing 100 time-steps. The interval of 100
time-steps is decided through the parameter IO_InfoSteps
, which was also equal to
100.