Download elsAxdt User Manual Python/CGNS interface for elsA

Profile
△ If you define a DataArray_t you will have to set the zone dimensions in order to be CGNS
compliant. Thus you will loose a lot of space if you do not lay on an existing solution you
want to keep. Moreover, as using the DataArray_t does not require the zone dimensions,
you can use a link to a given zone and then factorize your output declaration.
△ In the output tree, no links are created to the grids coordinates, reference state or any
other sub-trees of the input CGNS tree. The user as to post-process the result and add the
links to the grids.
△ As mentionned in the next section, a request to a conservative variable implicitely forces
the output of the corresponding convergence.
△ As the init solution and the output solution may have the same dimensions, it is possible
to use the init solution as output skeletton, again using the links mechanisms.
A special name is reserved, in the case your solution starts with
FlowSolution#AbsoluteCoordinates, the parser would force the coordinates output to be absolute.
These coordinates are put in the flow solution sub-node, not in the grid coordinates sub-node.
You can set the elsa specific parameters using the .Solver#Output node. You add a child with the elsa
parameter name as node name and its value with a DataArray_t node type.
Fig (8) Proprietary settings for a solution output
For example, for a given flow solution, the grid location of the data is fixed. If you want Vertex solutions and a CellCenter solutions you should have two separate solutions, or per grid location. Use
the loc attribute defined below. The default value is CellCenter.
The .Solver#Output node is a UserDefinedData_t node with the definition of some elsa output
control parameters:
period integer, sets output frequency w.r.t. iteration
refer to elsA manual
writingmode integer
1: end of run
2: one each period
refer to elsA manual
writingframe
integer
refer to elsA manual
loc integer
0: CellCenter
1: Vertex
2: cellfict
Sets the GridLocation for the
expected output
Please note the important case of the so-called cellfict output . This output is not CGNS compliant and
cannot be stored as a FlowSolution_t. Then we add a UserDefinedData_t node named
.Solver#CellFict which stores the cellfict array values.
/ELSA/MU-02052/v2.0
elsAxdt
19/49