<html>#2120: check that all parfiles that set ADMMacros::spatial_order also set GRHydro::sources_spatial_order to the same value
<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>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2018_02</td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>task</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 helvi witek):</p>
<p>I agree with your pull request.</p>
<ul>
<li>Historically, has there been such a change from ADMMacros to thorn specific FD orders in other evolution thorns? If so, I would suggest to add a similar parameter check to those.</li>
<li>I suggest to change the relevant parameters in the gallery examples and tutorials to avoid this problem in the future. If no one objects I will do that in the TOV gallery example</li>
</ul>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2120/check-that-all-parfiles-that-set-admmacros'>https://bitbucket.org/einsteintoolkit/tickets/issues/2120/check-that-all-parfiles-that-set-admmacros</a></p>
</html>