UG_IO SimSys MNODE 3D Node Data File Type
An MNODE file contains a list of node coordinates and a symmetric metric. No connectivity between the nodes is assumed.
{ [ ( X for node 1,
Y for node 1,
Z for node 1,
Met_0 for node 1,
Met_1 for node 1,
Met_2 for node 1,
Met_3 for node 1,
Met_4 for node 1,
Met_5 for node 1 ),
( X for node 2,
Y for node 2,
Z for node 2,
Met_0 for node 2,
Met_1 for node 2,
Met_2 for node 2,
Met_3 for node 2,
Met_4 for node 2,
Met_5 for node 2 ),
...
( X for node Number_of_Nodes,
Y for node Number_of_Nodes,
Z for node Number_of_Nodes,
Met_0 for node Number_of_Nodes,
Met_1 for node Number_of_Nodes,
Met_2 for node Number_of_Nodes,
Met_3 for node Number_of_Nodes,
Met_4 for node Number_of_Nodes,
Met_5 for node Number_of_Nodes ) ] }
Number_of_Nodes : Number of source nodes.
Met_0 : coefficient 0 of symmetric metric.
Met_1 : coefficient 1 of symmetric metric.
Met_2 : coefficient 2 of symmetric metric.
Met_3 : coefficient 3 of symmetric metric.
Met_4 : coefficient 4 of symmetric metric.
Met_5 : coefficient 5 of symmetric metric.
Met_0 Met_1 Met_2
Metric = Met_1 Met_3 Met_4
Met_2 Met_4 Met_5
In the above description, the parentheses ( ... ) are for grouping, the brackets [ ... ] enclose items in a loop, and braces { ... } enclose items in a single logical record.
The metric, Metric, must have real, non-zero eigenvalues and eigenvectors at each node. The data may be written out or read in using records the length of loops or of the individual data items. Data items may be written out in free format of any specific form. MNODE files must be formatted ASCII.