<html>#2836: add support for different data types to GPU arrays
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</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>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>This adds proper support for data types other than <code>double</code> to CarpetX, also for GPUs.</p>
<p>It introduces a helper class <code>AnyVector</code>that can hold any data type (similar to <code>gdata</code> in CarpetLib), as well as a number of switch statements to handle openPMD's typed output routines. </p>
<p>I am told that very new versions of openPMD-api lets one call the internal un-typed output routine, but at the time this code was written, that was not yet possible, and thus may not be possible on all cluster installed copies of openPMD.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2836/add-support-for-different-data-types-to'>https://bitbucket.org/einsteintoolkit/tickets/issues/2836/add-support-for-different-data-types-to</a></p>
</html>