<html>#2543: Consolidate data formats to simplify postprocessing
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Wolfgang Kastaun</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Comment (by Erik Schnetter):</p>
<p>I have added a routine to CarpetX that output metadata similar to the ones you request. See <a data-is-external-link="true" href="https://gist.github.com/eschnett/8ac85b09f0c156fe7c224d8420aa37d4" rel="nofollow">here</a> for an example.</p>
<p>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.</p>
<p>Since this is just a proof of concept, there are two metadata files (that should change later). The first, <code>cactus-metadata</code>, should have all the data requested above. The second, <code>carpetx-metadata</code>, 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.</p>
<p>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.</p>
<p>Wolfgang, Gabriele, could you comment?</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2543/consolidate-data-formats-to-simplify'>https://bitbucket.org/einsteintoolkit/tickets/issues/2543/consolidate-data-formats-to-simplify</a></p>
</html>