<html>#2348: presync branch of McLachlan modifies generated code
<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>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>There are some commits in the presync branch of McLachlan that modify generated code. They can be found via <code>git log ML_*/</code> or by regenerating the code and checking what changed. None of these changes will survive the mandatory regeneration of ML’s code before the release (see <a data-is-external-link="true" href="https://docs.einsteintoolkit.org/et-docs/Release_Process#One_or_two_days_before_the_release" rel="nofollow">https://docs.einsteintoolkit.org/et-docs/Release_Process#One_or_two_days_before_the_release</a>). </p>
<p>In order to survive they must all be (somehow) incorporated into the Mathematica sources or possibly use the “MergeFiles” inclusion mechanism present in Kranc (see ML_ADMConstraints.m and its <code>MergeFiles → “prototype/ML_ADMConstraints”</code> line). The generated C code may require changes to Kranc.</p>
<p></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2348/presync-branch-of-mclachlan-modifies'>https://bitbucket.org/einsteintoolkit/tickets/issues/2348/presync-branch-of-mclachlan-modifies</a></p>
</html>