Comment (by Lucas Timotheo Sanches):

Hello Alejandra,

‌

Apologies for the long silence in my reply.

Since your original issue of not being able to run qc0 at all using CarpetX seems to be resolved, for organization purposes I’d like to suggest that we mark this issue as solved, if that is OK with you, i.e., if you feel that your issue has been resolved.

For completeness, your visualization issues could stem from a variety of reasons, one of them being a “weird” or somehow corrupted HDF5 installation in your system (Silo files are backed by HDF5). It is difficult to diagnose that without more details. If you are still facing those issues, I’d recommend opening a new ticket and including as much information about that specific problem as possible, such as your machine details, a thorn list and a parameter file so that we can try and reproduce whatever behavior you are encountering.

As for interpreting information in PunctureTrackers, here’s a brief guide:

1. Each iteration produces a tsv file with puncture data location called puncturetracker-pt_loc.itXXXXX.tsv.
2. Each file contains the (t, x, y, z)location of a puncture at that iteration and evolution time.
3. Since the thorn can track up to 10 punctures, you see each coordinate for each puncture represented in brackets. For example, the x position of the first two tracked punctures are given in columns labeled pt_loc_x[0] and pt_loc_x[1]

‌

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