<html>#2947: CarpetX: Support 2D output
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Maxwell Rizzo</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></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>Currently 1D slices (x/y/z) and the full 3D output for Grid Functions are both supported output configurations from CarpetX. CarpetX is missing functionality to output 2D planes (xy, xz, yz). </p>
<p>There is a sublety for how the slice is chosen, given the different centering options, some variables likely will not contain data along the <code>x/y/z=0</code> planes exactly, which is a similar sublety that the 1D output slice must resolve, hopefully these can be resolve consistently.</p>
<p>Also from a discussion with Roland, 2D output is inefficient for a Carpet/CarpetX simulation to output, compared to 1D and 3D. A performance test could be useful in gauging if this feature would be worth implementing/using at all in CarpetX.</p>
<p>TSV (or another text file format) probably makes sense as the starting point, if functional a compressed format like OpenPMD would also be desirable, bringing the 2D CarpetX output features in-line to what was present in Carpet.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2947/carpetx-support-2d-output'>https://bitbucket.org/einsteintoolkit/tickets/issues/2947/carpetx-support-2d-output</a></p>
</html>