<html>#2248: incorrect use of "opcodes" for "operation_codes" param table entry in AEILocalInterp users
<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>bug</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>Some thorns using AEILocalInterp incorrectly name the table of operation codes (plain interpolation, derivative, etc.) "opcodes" instead of the correct "operation_codes". Apparently an old api proposals (2.2) did indeed use "opcodes" and the affected thorns are probably descendants of a code using this early API.</p>
<p>The affected thorns are:</p>
<ul>
<li>Outflow (probably the one disseminating the incorrect usage, and having picked it up from earlier codes at PSU and GT) maintained by <a href="https://bitbucket.org/rhaas80/" rel="nofollow" title="@rhaas80" class="ap-mention mention ap-connect-link" data-atlassian-id="557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22">@Roland Haas</a></li>
<li>particle_tracerET maintained by <a href="https://bitbucket.org/zach_etienne/" rel="nofollow" title="@zach_etienne" class="ap-mention mention ap-connect-link" data-atlassian-id="557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278">@Zach Etienne</a></li>
<li>plus a number of non-public Zelmani thorns (since they descend from Outflow)</li>
</ul>
<p>None of the thorns actually produces incorrect results since they all set the operation to be 0 (plain interpolation) which is the default.</p>
<p>In all cases the fix is to change "opcodes" to "operation_codes" in the name of the table entry. Changing the name of the variables used to hold the operation codes is optional.</p>
<p>Kindly pointed out by <a href="https://bitbucket.org/shawngr2/" rel="nofollow" title="@shawngr2" class="ap-mention mention ap-connect-link" data-atlassian-id="557058:adf4d1a2-8ed1-411d-aaf4-fd6db1b5e043">@Shawn Rosofsky</a> who ran into this when actually having to compute derivatives.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2248/incorrect-use-of-opcodes-for'>https://bitbucket.org/einsteintoolkit/tickets/issues/2248/incorrect-use-of-opcodes-for</a></p>
</html>