<html>#2686: Rename CCTK_REAL -> double when float is not tested
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Zach Etienne</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>Comment (by Zach Etienne):</p>
<p>I like the idea of testing all the commonly used thorns with single precision, but I worry it’s going to take a long time to debug and fix all the issues. (I’d love to be proven wrong!)</p>
<p>Compiler errors are just the start I fear; consider all the algorithms with tolerances tuned to relative errors ~1e-15 like conservatives-to primitives solvers, AH finders, etc. Also I bet our more complex finite-difference-based and possibly finite-volume-based codes (BSSN & GRMHD codes) will become unstable & unusable. But again, I’d love to be proven wrong. <img class="emoji" src="https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/standard/a51a7674-8d5d-4495-a2d2-a67c090f5c3b/48x48/1f642.png" alt="🙂" title=":slight_smile:" data-emoji-short-name=":slight_smile:" /></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2686/rename-cctk_real-double-when-float-is-not'>https://bitbucket.org/einsteintoolkit/tickets/issues/2686/rename-cctk_real-double-when-float-is-not</a></p>
</html>