[MOAB-dev] file formats

Lukasz Kaczmarczyk Lukasz.Kaczmarczyk at glasgow.ac.uk
Wed Apr 6 06:34:28 CDT 2016


Hello,

I am not convinced that this is the best approach, however I can tell how I do it.

I create meshset with number of contained meshsets equal to number of time steps. Each of contained meshsets has tag, which data on all entities on meshset which I store for time step. That can be saved in native HD5 file and read  back if needed without data redundancies and allow to add time steps. However is a issue of post-processing, that will need some proper reader for post-procssor which I not currently have.

There are additional complexities, when you store multiple fields and you store data for variable number of entities for each step. In may case I implemented it like tape recorder, that I have different tapes for which I record and play tapes depending on need. If this will be any use for you pleas look at example,
http://mofem.eng.gla.ac.uk/mofem/html/record__series__atom_8cpp_source.html
In example I have two tapes there and two moab instances, one use for recording another for reading for testing proposes. This works ok, but is missing proper reader for paraview and at the end I produce series of VTKs for paraview. This is very specific to my development by you can use it as idea if you like it.

I would be great to have some common interface to record and read time series of tags for moab. That if one will write reader for paraview it could be used by several developers woking on different codes.


Regards,
Lukasz





On 6 Apr 2016, at 10:02, Nico Schlömer <nico.schloemer at gmail.com<mailto:nico.schloemer at gmail.com>> wrote:

Hi everyone,

I'll start tackling a time-series problem rather soon and I'm wondering about file formats here. Ideally, I'd have one time series per file (particularly since the mesh isn't changing over time, perhaps that could be made use of), but I'm not sure if MOAB's custom HDF5 supports that yet.

Thinking of which, I faintly remember there had been talk about switching to a better-supported format in the future (xdmf and exodus came to mind). Is this still a thing?

Cheers,
Nico

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20160406/bd7c3c02/attachment.html>


More information about the moab-dev mailing list