Clarify management of coordinate systems #2033
Description
Description of the feature
The result.coordinate_system operator currently returns a field with 3x3 rotation matrix and origin coordinates for a given coordinate system ID.
This is now being exposed in other places such as the cyclic support (see #153).
This means the CS location should at least be made available and documented and the management of coordinate systems should be clarified.
Do we need a CoordinateSystem dedicated object? Do we need to manage the CS location in some other places? Do we need to allow to add coordinate systems to plots?
It could be argued that the location of the field should be overall and that the fact it represents a coordinate system could be communicated another way:
If for example we want to define the field of element coordinate systems, I would expect an Elemental field with the aforementioned matrix at each entity. Same for a field of coordinate systems at each node, at each part... etc.
@oparreno @rafacanton any input on this?
Steps for implementing the feature
No response
Useful links and references
No response