#2915: Include CapyrX: a GPU-accelerated multipatch infrastructure
Reporter: Beyhan Karakaş
Status: open
Milestone: ET_2026_05
Version:
Type: enhancement
Priority: major
Component: EinsteinToolkit thorn
Comment (by Lucas Timotheo Sanches):
The [latest commit to master](https://github.com/lucass-carneiro/CapyrX/commit/7e59d2ee3c155d1320… should fix this.
The issue is that that specific test case relied on `Multipole` from `SpacetimeX`. The ETK master thorn list has "vanilla" `Multipole`, which does not jive with the rest of the infrastructure. Removing this test case should solve this
For the manifest, I'm not sure what the procedure is. Should I just edit the master thornlist [here](https://bitbucket.org/einsteintoolkit/manifest/src/master/) and create a PR for this repo?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2915/include-capyrx-a-…
#2915: Include CapyrX: a GPU-accelerated multipatch infrastructure
Reporter: Beyhan Karakaş
Status: open
Milestone: ET_2026_05
Version:
Type: enhancement
Priority: major
Component: EinsteinToolkit thorn
Comment (by Roland Haas):
Adding all present thorns (and applying the NewRadX patch for multipatch support) I get a test failure:
```
multipole (from CapyrX_WaveToy)
```
with error message:
```
Error: Implementation 'COORDBASE' not activated.
This implementation is required by activated thorn(s):
Multipole (implementing multipole)
This implementation is provided by compiled thorn(s):
CoordBase
Add a thorn providing this implementation to the ActiveThorns parameter.
Error: Implementation 'GRID' not activated.
This implementation is required by activated thorn(s):
Multipole (implementing multipole)
This implementation is provided by compiled thorn(s):
CartGrid3D
Add a thorn providing this implementation to the ActiveThorns parameter.
Activation failed - 2 errors in activation sequence
WARNING level 0 from host haengie2.phas.ubc.ca process 0
in thorn Cactus, file /home/rhaas/postdoc/gr/cactus/ET_trunk/configs/sim/build/Cactus/main/SetParams.c:93:
-> CCTKi_SetParameter: Error at line 1 in parameter file /home/rhaas/postdoc/gr/cactus/ET_trunk/arrangements/CapyrX/CapyrX_WaveToy/test/multipole.par while activating thorns
```
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2915/include-capyrx-a-…
#2915: Include CapyrX: a GPU-accelerated multipatch infrastructure
Reporter: Beyhan Karakaş
Status: open
Milestone: ET_2026_05
Version:
Type: enhancement
Priority: major
Component: EinsteinToolkit thorn
Comment (by Roland Haas):
Is there a pull request for manifest with thorns to include?
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2915/include-capyrx-a-…
#2929: GRHayLET/IllinoisGRMHD convert_IllinoisGRMHD_to_HydroBase schedule compatibility with VolumeIntegrals_*
Reporter: Maxwell Rizzo
Status: new
Milestone: ET_2026_05
Version: ET_2025_05
Type: bug
Priority: major
Component: EinsteinToolkit thorn
Comment (by Leonardo Rosa Werneck):
In this case, the issue is not with `VolumeIntegrals`, but with `IllinoisGRMHD`. `VolumeIntegrals` expects `HydroBase` variables, and when using `IllinoisGRMHD`, those variables are only set correctly if one explicitly calls the routine that converts from `IllinoisGRMHD`'s native variables to `HydroBase`.
This is therefore not a diagnostic issue, but rather a consequence of `IllinoisGRMHD`'s choice of gridfunctions. For that reason, I think it is reasonable to expect `IllinoisGRMHD` to handle this conversion, rather than placing that responsibility on the diagnostic thorn.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2929/grhaylet-illinois…
#2932: Kuibit: detecting 0D and 1D files generated during Llama runs
Reporter: Jordan Nicoules
Status: new
Milestone:
Version:
Type: enhancement
Priority: minor
Component: EinsteinToolkit thorn
Comment (by Maxwell Rizzo):
Thanks for clarifying, in that case the PR looks complete.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2932/kuibit-detecting-…