Wr_HDF5_Field creates files that can be read back with Rd_HDF5_field. Wr_HDF5_Time_ Field is similar to Wr_HDF5_Field, except that its input is a time-dependent field.
Wr_HF5_Field is the higher-level version of H5write_field. The interface is quite simple, because H5write_field has few parameters. The entire field is always written out - all node data components (if any), all cell data components (if any), etc. The user does not have the ability to write out only a part of the field.The meaning of filename typein box, the browse button, and the "Write File" button are all fairly self-explanatory. Under the write file button there is a toggle box (UItoggle) labeled "Write Compressed" If this box is checked, some of the larger arrays in the field (example node_data.values) will be written out in compressed form potentially resulting in a smaller file size. Note: the effectiveness of data compression will vary widely from dataset to dataset. As a rule of thumb, floating point data will compress poorly. Also, using subsetting operations (crop/downsize) when reading a compressed dataset can be extremely slow.Wr_HF5_Time_Field is the higher-level version of H5write_time_field. Its very similar to Wr_HF5_Field, except that its input is a time-dependent field. The user interface is exactly the same as Wr_HF5_Field. The entire field is always written out - all time steps, all node data components (if any), all cell data components (if any), etc.