<html>#2861: Running qc0 with CarpetX
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Alejandra Gonzalez</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></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>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Alejandra Gonzalez):</p>
<p>Hi Lucas, </p>
<p>It seems it’s just a warning, since there don’t seem to be errors shown in the output for the AH and the waveform (which I’m also able to visualize without issues). </p>
<p>However I haven’t been able to visualize the silo and punturetracker output. For the silo files I try to open them with VisIt but it keeps showing errors so I can’t read anything (I’m outputting the same variable as your parfile ,`ADMBaseX::alp`). As for the puncture tracker, seeing the files by hand they seem to have sane numbers but I don’t really understand what all those indices are for each coordinate. It’s mostly probably me not understanding how the output is structured I fear, rather than maybe there’s a bug in the code. </p>
<p>Thanks again!</p>
<p></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx'>https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx</a></p>
</html>