Alternate Proposal for Allowing User-Defined Data
Under each of the following nodes:
- ArbitraryGridMotion_t <-- note new location
allow the following child node:
Name: User defined
Data-Type: user defined
Dimensions: user defined
Dimension Values: user defined
Data: user defined
Parameters: DataType, dimension of data, size of data
Child Nodes: Figure 26
Advantages to this new proposal:
- This construct is identical to the one currently allowed under RigidGridMotion, ZoneIterativeData, and BaseIterativeData. So there is consistency.
It is definitely
do-able (and there is no confusion) to allow it under:
But under FlowSolution_t and ConvergenceHistory_t, a very large list of DataArray_t data-name identifiers exist, that require a certain dimension. And under DiscreteData_t, the list is infinite. Thus it could be very difficult / confusing to allow additional DataArray_t nodes of ARBITRARY dimension here.
This begs the question: do we really NEED to allow arbitrary-sized DataArray_t nodes under ALL of the above-mentioned nodes, or is it enough to allow them only under CGNSBase_t, Zone_t, ArbitraryGridMotion_t, and GridCoordinates_t?