User Tools

Site Tools


development:hdf5

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
development:hdf5 [2008/12/29 07:45]
gibson
development:hdf5 [2008/12/29 09:36]
milosilak Testing access using my new account. Also correcting the special character in my name.
Line 1: Line 1:
 ====== Switch binary FlowField IO to HDF5 ====== ====== Switch binary FlowField IO to HDF5 ======
  
-Milǒs ​Ilak of Princeton MAE is working on this and we've been discussing over email. The following is my revision of Milǒs's most recent proposed structure for HDF5 files.+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^ ^ HDF5 field ^ meaning, issues^
Line 13: Line 15:
  
 Note: ''​geom/​x,​y,​z''​ is shorthand for three separate HDF5 fields ''​geom/​x'',​ ''​geom/​y'',​ and ''​geom/​z''​. Note: ''​geom/​x,​y,​z''​ is shorthand for three separate HDF5 fields ''​geom/​x'',​ ''​geom/​y'',​ and ''​geom/​z''​.
 +
 +**Issues**
  
   * ''​geom/​x,​y,​z''​ may 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.   * ''​geom/​x,​y,​z''​ may 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.
Line 21: Line 25:
   * I think all data should be stored as ''​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.   * I think all data should be stored as ''​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.
   * Rather than storing additional fields like vorticity or pressure inside a given field'​s HDF5 file, it's better to create them as separate FlowFields in C++ and then save them as separate HDF5 files. That fits how FlowFields are used within C++ better. ​   * Rather than storing additional fields like vorticity or pressure inside a given field'​s HDF5 file, it's better to create them as separate FlowFields in C++ and then save them as separate HDF5 files. That fits how FlowFields are used within C++ better. ​
 +
 +----
 +
 +//responses go here, please give name and date //
 +
 +
development/hdf5.txt · Last modified: 2010/02/02 07:55 (external edit)