<html>#2628: ADMBase, HydroBase, etc should not set up initial data
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Zach Etienne</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></td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Yup, WONTFIX. The *Base variables also declare the parameters that control what is set as ID an those parameter have to have value. Someone then has to act on that parameter value and it the thorn that introduced the value is (naturally) the only one guaranteed to be around.</p>
<p>The other issue is that the *Base thorns not setting ID can lead to situations of not setting ID at all (namely if no ID thorn is activated). Really the ID thorns are the ones that must look at the <code>intiail_foo</code> parameters and then set their ID. The *Base thorns already do look at those parameters and only set the data to vacuum / Minkowski if the parameter values tell them to do so.<br>
How many timelevels are needed for a variable is actually something that is usually determined by a combination of the evolution thorn, Carpet and the time stepper. Keep in mind that multiple <code>STORAGE: foo[n]</code> statements for the same <code>foo</code> in mulitple thorns is valid, the largest <code>n</code> is what gets used. Namely <code>STORAGE</code> allocates <em>at least</em> <code>n</code> levels of storage, not <em>exactly</em>.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2628/admbase-hydrobase-etc-should-not-set-up'>https://bitbucket.org/einsteintoolkit/tickets/issues/2628/admbase-hydrobase-etc-should-not-set-up</a></p>
</html>