<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 Lucas Timotheo Sanches):</p>
<p>Hi Alejandra. </p>
<p>I was unable to make <code>Punctures</code> work by simply modifying parameters, which suggests that the thorn has a more fundamental issue. This will need to be further investigated at another opportune moment. </p>
<p>Regardless, as you noted <code>TwoPuncturesX</code> is the preferred option for initial data and should be used instead. </p>
<p>Yes, your output seems to indicate that your execution of the parameter file was successful. As you may have noticed, this example parameter file only runs for a single iteration, which is probably not very useful for your needs. </p>
<p>As for output formats, here’s an abbreviated guideline </p>
<ul>
<li>Whenever you intend to visualize 3D data, use the <code>Silo</code> format. The <code>Silo</code> format can be used natively with <a data-is-external-link="true" href="https://visit-dav.github.io/visit-website/index.html" rel="nofollow">LLNL’s VisIt</a>. This is probably the easiest way to visualize <code>CarpetX</code> data, as it allows you to simply read the files and create plots by using a GUI. The <code>OpenPMD</code> file is also an option for visualization, but you may have to write custom Python scripts for it. </li>
<li>Whenever you wish to store data, in Checkpoints, for instance, the <code>ADIOS2</code> and <code>OpenPMD</code> files are adequate. </li>
<li><code>TSV</code> data, which is plain text, not recommended for storage, in general. It is more of a debug format, where you can look at grid function values in a human readable manner. <code>TSV</code> data is also adequate for storing the multipolar extractions of the Weyl scalar and the location of the punctures throughout the simulation. </li>
</ul>
<p>I have compiled a more complex <code>qc0</code> parameter file, which uses <code>TwoPunctureX</code> for initial data, but also performs Apparent Horizon finding, puncture tracking and multipole extractions of the Psi4 Weyl scalar. This example should give you a good idea on what production run looks like and may be use
<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>