Comment (by Lucas Timotheo Sanches):

Hi Alejandra.

I was unable to make Punctures 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.

Regardless, as you noted TwoPuncturesX is the preferred option for initial data and should be used instead.

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.

As for output formats, here’s an abbreviated guideline

• Whenever you intend to visualize 3D data, use the Silo format. The Silo format can be used natively with LLNL’s VisIt. This is probably the easiest way to visualize CarpetX data, as it allows you to simply read the files and create plots by using a GUI. The OpenPMD file is also an option for visualization, but you may have to write custom Python scripts for it.
• Whenever you wish to store data, in Checkpoints, for instance, the ADIOS2 and OpenPMD files are adequate.
• TSV 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. TSV data is also adequate for storing the multipolar extractions of the Weyl scalar and the location of the punctures throughout the simulation.

I have compiled a more complex qc0 parameter file, which uses TwoPunctureX 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

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-carpetx