<html>#2064: Add GiRaFFE to the Einstein Toolkit
<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>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2019_10</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>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Zach Etienne):</p>
<p><span class="ap-mention" data-atlassian-id="557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22">@Roland Haas</span> We have decided to go in a different direction from this pull request. We are currently NRPy-fying GiRaFFE in a way that pulls each component of GiRaFFE into a unit test that validates against the original version. Having the entire GiRaFFE written & documented in Jupyter notebooks (where one need only run the Jupyter notebooks to generate the entire thorn/thorn family, and every equation is NRPy-fied + documented with a hyperlink to the relevant paper) will be most sustainable moving forward.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2064/add-giraffe-to-the-einstein-toolkit'>https://bitbucket.org/einsteintoolkit/tickets/issues/2064/add-giraffe-to-the-einstein-toolkit</a></p>
</html>