To combine more than one of the sets for a given server (what we may call a cluster of
sets), one must create a casefile which contains a Block_Continuation
section (as described in Block Continuation in the Ansys EnSight User Manual).
In our example on the previous page, there were five case files (with their associated .geo and .scl files).
set_1.case set_2.case set_3.case set_4.case set_5.case set_1.geo set_2.geo set_3.geo set_4.geo set_5.geo set_1.scl set_2.scl set_3.scl set_4.scl set_5.scl
and the contents of the first of these casefiles (set_1.case) would look something like:
FORMAT type: ensight gold GEOMETRY model: set_1.geo VARIABLE scalar per node: set_1.scl
With the contents of each of the other casefiles differing only in the digit following the underscore.
To cluster these as described (two sets in the first case and 3 sets in the second case), we would need to create the following two casefiles.
cluster_1.case, would contain:
FORMAT type: ensight gold GEOMETRY model: set_%.geo VARIABLE scalar per node: set_%.scl BLOCK_CONTINUATION number of sets: 2 filename start number: 1 filename increment: 1
Note: Note the use of % as the wildcard for VARIABLE block continuation
sets.
cluster_2.case, would contain:
FORMAT type: ensight gold GEOMETRY model: set_%.geo VARIABLE scalar per node: set_%.scl BLOCK_CONTINUATION number of sets: 3 filename start number: 3 filename increment: 1
And we could then easily use an SOS casefile (perhaps named, two_blocks.sos) that would use these two cluster files:
FORMAT type: master_server gold SERVERS number of servers: 2 #Server 1 machine id: node1 executable: ensight100.server casefile: cluster_1.case #Server 2 machine id: node2 executable: ensight100.server casefile: cluster_2.case
If you now run EnSight using this SOS casefile, the two block parts should appear as you would expect. Of course, to avoid any visual (or computational) effects from the partitioning, you would need to be using ghost cells between the original partitions (sets). See the example file below.
An example of such is the third set geometry file (set_3.geo), which is using uniform blocks with ranges:
Uniform Block Continuation Test - set 3
=======================================
node id assign
element id assign
extents
0.00000e+00 1.00000e+00
-5.00000e+00 1.00000e+00
0.00000e+00 5.00000e+00
part
1
horizontal
block uniform range
2 2 6
1 2 1 2 3 4
0.00000e+00
0.00000e+00
2.00000e+00
1.00000e+00
1.00000e+00
1.00000e+00
part
2
vertical
block uniform range
2 11 2
1 2 5 7 1 2
0.00000e+00
-2.00000e+00
0.00000e+00
1.00000e+00
-0.50000e+00
1.00000e+00Curvilinear, parallelepiped and rectilinear descriptions for block parts are of course also valid. This same file using ghost cells is:
Uniform Block Continuation Test - set 3
=======================================
node id assign
element id assign
extents
0.00000e+00 1.00000e+00
-5.00000e+00 1.00000e+00 0.00000e+00 5.00000e+00
part
1
horizontal
block uniform with_ghost range
2 2 6
1 2 1 2 2 5
0.00000e+00
0.00000e+00
1.00000e+00
1.00000e+00
1.00000e+00
1.00000e+00
ghost_flags
1
0
1
part
2
vertical
block uniform with_ghost range
2 11 2
1 2 4 8 1 2
0.00000e+00
-1.50000e+00
0.00000e+00
1.00000e+00
-0.50000e+00
1.00000e+00
ghost_flags
1
0
0
1Transient Example
If we change our example to be a simple transient model, using the same sets, but now with two time steps:
set_1_00.case set_2_00.case set_3_00.case set_4_00.case set_5_00.case set_1_00.geo set_2_00.geo set_3_00.geo set_4_00.geo set_5_00.geo set_1_00.scl set_2_00.scl set_3_00.scl set_4_00.scl set_5_00.scl set_1_01.case set_2_01.case set_3_01.case set_4_01.case set_5_01.case set_1_01.geo set_2_01.geo set_3_01.geo set_4_01.geo set_5_01.geo set_1_01.scl set_2_01.scl set_3_01.scl set_4_01.scl set_5_01.scl
The contents of the first of these casefiles (set_1_00.case) would now look something like:
FORMAT type: ensight gold GEOMETRY model: 1 set_1_**.geo changing_coords_only VARIABLE scalar per node: 1 set_1_**.scl TIME time set: 1 number of steps: 2 filename start number: 0 filename increment: 1 time values: 0.0 1.0
With the contents of each of the other casefiles differing only in the digit following the first underscore.
To cluster these as described (two sets in the first case and 3 sets in the second case), we would need to create the following two casefiles.
cluster_1.case, would contain:
FORMAT type: ensight gold GEOMETRY model: 1 set_%_**.geo changing_coords_only VARIABLE scalar per node: 1 set_%_**.scl TIME time set: 1 number of steps: 2 filename start number: 0 filename increment: 1 time values: 0.0 1.0 BLOCK_CONTINUATION number of sets: 2 filename start number: 1 filename increment: 1
cluster_2.case, would contain:
FORMAT type: ensight gold GEOMETRY model: 1 set_%_**.geo changing_coords_only VARIABLE scalar per node: 1 set_%_**.scl TIME time set: 1 number of steps: 2 filename start number: 0 filename increment: 1 time values: 0.0 1.0 BLOCK_CONTINUATION number of sets: 3 filename start number: 3 filename increment: 1
And we could then use the same SOS casefile that we showed in the static example.