"Garth N. Wells" <[email protected]> writes: > A solution seems very simple - use the HDF5 hierarchal structure to > associate Vectors with a Function. This is the advantage of using a > hierarchal storage format.
Well, a normalized representation contains links, which are supported by HDF5, but are not hierarchical. With a hierarchical structure, it requires a complicated (nested) traversal to give a list of all fields that can be provided, but when the relational model is implemented using links, the traversal for all fields related to a given mesh is complicated. When I wrote an HDF5-based mesh format, I used a normalized relational representation (implemented using HDF5 links) and provided some standard traversals, but SQL is a much cleaner way to represent and query such relations.
pgp2TWavl9utA.pgp
Description: PGP signature
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
