[ET Trac] #2543: Consolidate data formats to simplify postprocessing

[Erik Schnetter]

#2543: Consolidate data formats to simplify postprocessing

 Reporter: Wolfgang Kastaun
   Status: new
Milestone: 
  Version: development version
     Type: enhancement
 Priority: minor
Component: 

Comment (by Erik Schnetter):

I have added a routine to CarpetX that output metadata similar to the ones you request. See [here](https://gist.github.com/eschnett/8ac85b09f0c156fe7c224d8420aa37d4) for an example.

It is difficult to create a single file that contains information about all iterations, because this means that this file needs to be overwritten at each iteration. Instead, I’m creating a new file per iteration, and the post-processing tool should read all these files.

Since this is just a proof of concept, there are two metadata files \(that should change later\). The first, `cactus-metadata`, should have all the data requested above. The second, `carpetx-metadata`, already existed in CarpetX. It describes the grid structure \(that’s probably not interesting here\), but incidentally also all parameters in the very explidit format requested.

The metadata files are output in yaml. That’s a standard format that should be easy to read in Python, resulting in dictionaries and arrays.

Wolfgang, Gabriele, could you comment?

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2543/consolidate-data-formats-to-simplify
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einsteintoolkit.org/pipermail/trac/attachments/20210803/1aca5feb/attachment.html