Displays extra info.
Displays software version, and source control information if applicable.
Displays help information about the available command-line options for the executable.
Override a parameter (or define a new one) specified in the XML file.
Override a solverinfo (or define a new one) specified in the XML file.
By default when running in parallel the complete mesh is loaded by all processes, although partitioning is done uniquely on the root process only and communicated to the other processes. Each process then writes out its own partition to the local working directory. This is the most robust approach in accounting for systems where the distributed nodes do not share a common filesystem. In the case that there is a common filesystem, this option forces only the root process to load the complete mesh, perform partitioning and write out the session files for all partitions. This avoids potential memory issues when multiple processes attempt to load the complete mesh on a single node.
When using a fully-Fourier expansion, specifies the number of processes to use in the x-coordinate direction.
When using a fully-Fourier expansion or 3D expansion with two Fourier directions, specifies the number of processes to use in the y-coordinate direction.
When using Fourier expansions, specifies the number of processes to use in the z-coordinate direction.
Prints detailed information about the generated partitioning, such as number of elements, number of local degrees of freedom and the number of boundary degrees of freedom.
Partition the mesh only into the specified number of partitions, write to file and exit. This can be used to pre-partition a very large mesh on a single high-memory node, prior to being executed on a multi-node cluster.
Forces the use of METIS for mesh partitioning. If Nektar++ is compiled with Scotch support, the default is to use Scotch.
Forces the use of Scotch for mesh partitioning.