where: datatype is required and is one of the formats of EnSight’s internal readers (which use the Part builder), namely: gold ensight6 ensight5 plot3d or it can be the string used to name any of the user-defined readers.

If datatype is blank, it will default to EnSight6 data type.

Optional for structured or unstructured data)

EnSight server will automatically distribute data to the servers (also called Server decompose) specified below if this option is present and set to on. This will require that each of the servers have access to the same data (or identical copies of it). For structured data: use only if the datatype is gold, plot3d or a 2.06 or greater user-defined reader (which has implemented structured cinching). For unstructured data: use only if the datatype is gold, or a 2.08 (or greater) user-defined reader. Additionally, be aware that 2.* user-defined readers should implement the special functions defined in README_USERD_IN_BUFFERS file if memory is to be used efficiently in the unstructured auto-distribute process.

Optional for unstructured auto_distribute - default is on (before version 10.1.4(a)), and is off for later versions

Allows user to control whether ghost cells will be produced between the distributed portions.

Optional for unstructured auto_distribute and do_ghosts - default is 100000

Allows user to modify the default buffer size that is used when reading node and element information of the model when producing ghost cells.

Optional for unstructured auto_distribute and do_ghosts - default is on (before version 10.1.4(a), and is off for later versions.

If set on, a simple metric will be printed in the shell window that can indicate the quality of the auto_. The unstructured auto_distribute method relies on some coherence in the element connectivity - namely, that elements that lie next to each other are generally listed close to each other in the data format.

The metric is simply the (#total_nodes / #nodes_needed_if_no_ghosts).

When no ghosts, the value will be 1.0. The more ghosts you must have, the higher this metric will be. If the number gets much more than 2.0, you may want to consider partitioning yourself.

where: num is the number of network interfaces to be used for the sos host.

num [repeat](Required)

where: num is the number of servers that will be started and run concurrently.

repeat indicates that the first server specification should be repeated num times for use with resources. Other server specifications will be ignored.

Required

where: mid is the machine id of the server.

or ensight_server.bat

[directory: wd]

Windows only Required, must use .bat extension

Optional

where: wd is the working directory from which ensight_server will be run

where: id is the login id. Only needed if it is different on this machine.

where: dd is the directory where the data resides. (Full path must be provided if you use this).

(Required, but depending on format, may vary as to whether it is a casefile, geometry file, neutral file, universal file, etc. Relates to the first data field of the Data Reader Dialog.)

(Depends on format as to whether required or not. Relates to the second data field of the Data Reader Dialog.)

(Depends on format as to whether required or not. Relates to the third data field of the Data Reader Dialog.)

(Depends on format as to whether required or not. Relates to the fourth data field of the Data Reader Dialog.)