#2861: Running qc0 with CarpetX
Reporter: Alejandra Gonzalez
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by Alejandra Gonzalez):
Hi Lucas, thank you so much for the information and the parfile.
To run it I had to download some additional thorns, i.e. \`Multipole PunctureTracker AEILocalInterp WeylScal4 …\` that I didn’t have before. But now I get a weird error in the HDF5 thorn:
```
libtool: compile: gfortran -I. -I../../src -std=f2008 -pedantic -Wall -Wextra -Wunderflow -Wimplicit-interface -Wsurprising -Waliasing -Wcharacter-truncation -Warray-temporaries -Wintrinsics-std -Wimplicit-procedure -Wreal-q-constant -Wfunction-elimination -Wrealloc-lhs -Wrealloc-lhs-all -Wno-c-binding-type -Wuse-without-only -Winteger-division -Wfrontend-loop-interchange -fcheck=all -g -Og -I../../src -I../../fortran/src -g -fcray-pointer -ffixed-line-length-none -O2 -fopenmp -c H5VLff.F90 -o H5VLff.o
H5VLff.F90:40:7:
40 | USE H5GLOBAL
| 1
Warning: USE statement at (1) has no ONLY qualifier [-Wuse-without-only]
H5VLff.F90:41:7:
41 | USE H5fortkit
| 1
Warning: USE statement at (1) has no ONLY qualifier [-Wuse-without-only]
H5VLff.F90:41:7: Fatal Error: Cannot open module file ‘h5fortkit.mod’ for reading at (1): No such file or directory
compilation terminated.
```
which I didn’t have before while compiling CarpetX with cuda. I attach my thornlist.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-…
#2848: updates to FLRWSolver
Reporter: Roland Haas
Status: new
Milestone: ET_2025_05
Version:
Type: enhancement
Priority: major
Component: EinsteinToolkit thorn
Comment (by Roland Haas):
@{557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278} may be able to review.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2848/updates-to-flrwso…
#2861: Running qc0 with CarpetX
Reporter: Alejandra Gonzalez
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by Alejandra Gonzalez):
Hi Lucas,
Thank you very much. Just one more question regarding the parfile you are sharing: Where can I find the thorn \`AEILocalInterp\`?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-…
#2861: Running qc0 with CarpetX
Reporter: Alejandra Gonzalez
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by Lucas Timotheo Sanches):
I have attached 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 useful to your applications.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-…
#2861: Running qc0 with CarpetX
Reporter: Alejandra Gonzalez
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
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](https://visit-dav.github.io/visit-website/index.html). 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.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2861/running-qc0-with-…