#2173: Test "Poisson equation" example
Reporter: Roland Haas
Status: open
Milestone: ET_2024_11
Version: development version
Type: task
Priority: major
Component: EinsteinToolkit website
Changes (by Maxwell Rizzo):
status: open (was resolved)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equa…
#2861: Running qc0 with CarpetX
Reporter: Alejandra Gonzalez
Status: open
Milestone:
Version:
Type: bug
Priority: major
Component: EinsteinToolkit thorn
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-…
#2869: Modify cactus flesh and SimFactory to enable post processing during testsuite
Reporter: Deborah Ferguson
Status: new
Milestone:
Version:
Type: enhancement
Priority: major
Component: Cactus
Changes (by Roland Haas):
Comment (by Roland Haas):
@{557058:1671c5c3-29cc-4e83-9850-a152d33a6235} care to review?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2869/modify-cactus-fle…
#2869: Modify cactus flesh and SimFactory to enable post processing during testsuite
Reporter: Deborah Ferguson
Status: new
Milestone:
Version:
Type: enhancement
Priority: major
Component: Cactus
Context: The Cactus testing framework includes the ability to provide an executable in the test.ccl file to run over files and then compare the output rather than comparing the files themselves. This enables, for example, running a script to print the contents of an h5 file so they can be compared during testing.
The issue: this executable is currently only looked for inside <thorn>/util but that isn’t where compiled utilities generally are put. Additionally, when using SimFactory to perform the tests, it copies everything needed to run the tests into scratch, but doesn’t currently copy these compiled utilities.
To enable usage of this feature, we need to
1\) In the cactus flesh, tell it to also look in exe/<config-name> where utilities are compiled to and
2\) In simfactory, also copy the utilities in exe/<config-name> when copying everything else \(the test data, the executable, etc\)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2869/modify-cactus-fle…
#2856: CarpetX: CarpetX errors out when it cycles time levels if those levels are not valid everywhere
Reporter: Steven R. Brandt
Status: resolved
Milestone: ET_2025_05
Version:
Type: bug
Priority: major
Component: Other
Changes (by Roland Haas):
status: resolved (was open)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2856/carpetx-carpetx-e…