...
ancestorAoS(x:y)/field(:) --> field(:,x:y)
Time issues
AoS
/path/ending/with/timedAoS(i1:i2)
HETERO - no additional actions
HOMO:
a) "global time" is copied to "local time" AoS/time (for every AoS in range i1:i2)
b) any other "time field" time should be copied????
In both cases an object representing AoS (that "owns" AoS array) will be returned - to be compatible with current Python implementation
(could be easily changed to list/array)
time independent data (no AoS3 on path)
/path/to/timeIndepArray(i1:i2)
/path/to/timeIndepField
HOMO: OK
HETERO: OK
No additional actions to be taken...
members of timed AoS (AoS3)
/path/with/timedAoS(i1:i2)/structure/data
From your email " get (« magnetics.flux_loop(i1:i2).flux.data ») returns data(i1:i2,t) in homogeneous case, and an error message otherwise."
So:
HETERO: ERROR (because of lack of time info available in returned data)
HOMO: OK (BTW Is "t" time or just size of "data" field ? Why data can be returned in such case (also no time info returned)
time dependent vectors/arrays
/path/to/timeDepArray(i1:i2) - path from root, no AoS3 on path
HOMO : OK
if field name is not "time" - no additional action
if field name is "time" - return ids%time
HETERO: OK
No special actions
Shape of returned arrays
...