<html>#2174: Test "Multi Patch Scalar Wave Equation" example
<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_08</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 website</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p><a href="https://bitbucket.org/ianhinder/" rel="nofollow" title="@ianhinder" class="ap-mention mention ap-connect-link" data-atlassian-id="557058:5785f23c-5444-46da-876b-61f027b7bbc3">@Ian Hinder</a> the tarfiles each contain the date when they were created. No data is updated, instead it is added. The idea is to give a dataset that was produced with the current release. I do expect that there will be slight differences depending on compiler etc. I would rather have a dataset that documents "this was the data that the person who claimed to have run the test saw" rather than having the data slowly drift away from the data produced by the newest compiler on the newest machine with the newest release. The tarballs are all kept here: <a href="https://bitbucket.org/einsteintoolkit/www/downloads/" rel="nofollow" class="ap-connect-link">https://bitbucket.org/einsteintoolkit/www/downloads/</a> I see no harm (other than using space on btibucket's servers) in updating the data files
so updating them would seem the less troublesome option.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation'>https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-scalar-wave-equation</a></p>
</html>