<html>#2742: Change Seed_Magnetic_Fields scheduling so it can be used by more thorns
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Samuel Cupp</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2023_11</td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</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>Comment (by Samuel Cupp):</p>
<p><span class="ap-mention" data-atlassian-id="557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22">@Roland Haas</span> In regards to deprecation, correct me if I’m wrong: the best approach to merge the two thorns is to<br>
A) Introduce the extra stuff to SMF to allow for BNS as well<br>
B) Ensure the default behavior of Seed_Magnetic_Fields (SMF) is as before<br>
C) Add deprecation warning for SMF_BNS thorn<br>
D) In the release after the one where this is added, remove the SMF_BNS thorn entirely</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2742/change-seed_magnetic_fields-scheduling-so'>https://bitbucket.org/einsteintoolkit/tickets/issues/2742/change-seed_magnetic_fields-scheduling-so</a></p>
</html>