<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:8bc23f2a-45c0-477d-8ac4-a5a16c734278">@Zach Etienne</span> , I would like your input on how you’d like me to change the scheduling, and whether you prefer two thorns or one. It seems strange for Seed_Magnetic_Fields_BNS to be in the diagnostics repo, especially when we can just have 1 thorn to provide both.</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>