The Nektar++ native file format is compliant with XML version 1.0. The root element is NEKTAR which contains a number of other elements which describe configuration for different aspects of the simulation. The required elements are shown below:
The different sub-elements can be split across multiple files, however each file must have a top-level NEKTAR tag. For example, one might store the geometry information separate from the remaining configuration in two separate files as illustrated below:
geometry.xml
conditions.xml
For example, the NekMesh
utility will produce a default EXPANSIONS
element and blank
CONDITIONS
element. Specifying a custom-written XML file containing these sections after the
file produced by NekMesh
will override these defaults.
The exception to this rule is when an empty XML sub-element would override a
non-empty XML sub-element. In this case the empty XML sub-element will be ignored.
If the custom-written XML file containing CONDITIONS
were specified before the
file produced by NEKMESH
, the empty CONDITIONS
tag in the latter file would be
ignored.