<html>#2516: Different simulation result with different number of cores setting
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td></td></tr>
<tr><td style='text-align:right'> Status:</td><td>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2019_10</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></td></tr>
</table>
<p>Comment (by Ken Hui):</p>
<p>Thanks for the suggestion on the MoL parameter setting, I will give a try on that.</p>
<p>You mentioned that OpenMP might give different result due to the unfixed order of operations, but I have got exactly the same output data (I have been comparing is mainly the h+ hx in mp_Psi4_l2_m2_rXXX.00.asc and the rho_maximum in hydrobase-rho.scalars.asc) with no discrepancy at all if I ran the simulation again with the same number of core setting, does that mean the problem is not related to OpenMP?</p>
<p>For all simulations I have done, I start the simulation from scratch each time (reading from the BNS initial data all over again), so probably the issue I am having is not related to the checkpoint/recovery part.</p>
<p>Anyway thanks again for the suggestion, I will try re-run the simulations to see if I still got very different output using different core number.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2516/different-simulation-result-with-different'>https://bitbucket.org/einsteintoolkit/tickets/issues/2516/different-simulation-result-with-different</a></p>
</html>