John Gibson Mon Dec 29 10:46:55 EST 2008
Miloš Ilak of Princeton MAE is working on this and we've been discussing over email. The following is my revision of Miloš's most recent proposed structure for HDF5 files.
|HDF5 field||meaning, issues|
|The x,y,z gridpoint values.|
|Number of gridpoints in x,y,z.|
|Lengths in x and z and bounds in y (a ⇐ y ⇐ b)|
|Components of scalar/vector/tensor field|
|All the integration parameters, set by DNS algorithm or to null values|
|channelflow version, e.g. 1.3.3|
|optional descriptive comment|
geom/x,y,z is shorthand for three separate HDF5 fields
geom/x,y,zmay or may not be worth including. Cost would be negligible, but they are redundant and trivially regenerable from more fundamental discretization parameters, e.g. x_n = n*Lx/Nx.
u0,u1,u2,…. FlowFields are meant to store fields of arbitrary meaning: pressure, velocity, stresses, vorticity, etc. Trying to change to labels based on the meaning of the field would lead to too much complexity in the FlowField IO function signature and/or the FlowField object.
responses go here, please give name and date