Trac July 2026

trac@lists.einsteintoolkit.org

1 participants
59 discussions

#2966: ExternalLibraries-AMReX: Fix CMake MPI detection against from-source OpenMPI
by Max Morris 20 Jul '26

20 Jul '26

#2966: ExternalLibraries-AMReX: Fix CMake MPI detection against from-source OpenMPI Reporter: Max Morris Status: submitted Milestone: Version: Type: bug Priority: major Component: This fixes an issue which prevents the ET from building when both OpenMPI and AMReX are built from source via ExternalLibraries. PR is here: https://github.com/EinsteinToolkit/ExternalLibraries-AMReX/pull/2 -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2966/externallibraries…

1 0

#1077: evaluate steered value as formula in AEIThorns::Trigger
by Jordan Nicoules 16 Jul '26

16 Jul '26

#1077: evaluate steered value as formula in AEIThorns::Trigger Reporter: Roland Haas Status: open Milestone: Version: Type: enhancement Priority: minor Component: Other Comment (by Jordan Nicoules): Can formulas be used for `Trigger_Checked_Variable` too (I think that was mainly the point of the conversation during the call of July 9)? What should be the syntax, I'm not sure I'm getting it? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/1077/evaluate-steered-…

1 0

#2965: GetComponents option to obtain new branch
by Jordan Nicoules 16 Jul '26

16 Jul '26

#2965: GetComponents option to obtain new branch Reporter: Jordan Nicoules Status: new Milestone: Version: Type: enhancement Priority: minor Component: GetComponents ## Context Typically on a new release, calling `GetComponents`, even with the update option, will check out new components, but existing ones will not deal with the `!REPO_BRANCH = $ET_RELEASE` which changes in the thornlist. On the other hand, a change in the repo's URL is detected and triggers some error, asking for a clean checkout (at least I could see that for `Carpet` and `POWER`, between ET_2023_05 and ET_2026_05). >From a naive user perspective, I expected that updating components with a thornlist that indicates an ET version would put the repos on the corresponding branch, ready to be compiled. ## Suggested feature (details TBD) **Either with the update option or a new option, add the `!REPO_BRANCH` to the fetch list, create the corresponding branch, and check it out if possible.** Possibly (as an option), it could also remove the previous one. This makes the most sense for branches that are release versions, but may not in general. A minima, if there are possible conflicts (unstaged changes etc.), it could raise a warning/error like for the URL, that the user would then deal with manually. ## Discussion 1. Is this feature desirable? Does it correspond better to a user's expectation? 2. Can it be harmful? 3. Does it actually save work and effort, compared to recreating a brand new Cactus directory? About point 2, a conservative addition of a fetched ref and corresponding local branch, even if not checked out, looks benign to me. Regarding point 3, to me one of the issues is the following. With a new Cactus directory, it's needed to manually move and redo possible local changes and/or additions (tracking more branches/remotes, local commits,...) -- even for forked/owned repositories, although it's less critical in that case. This manual adjustment may not disappear completely, but could be alleviated (and be more explicit). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2965/getcomponents-opt…

1 0

#2870: Test "Black-hole hair in axi-dilaton gravity" example
by Beyhan Karakaş 16 Jul '26

16 Jul '26

#2870: Test "Black-hole hair in axi-dilaton gravity" example Reporter: Maxwell Rizzo Status: resolved Milestone: ET_2026_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Beyhan Karakaş): status: resolved (was open) Comment (by Beyhan Karakaş): The example was last tested by Noora and website updated. Thank you. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2870/test-black-hole-h…

1 0

#2172: Test "Binary black hole GW150914" example
by Beyhan Karakaş 16 Jul '26

16 Jul '26

#2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: resolved Milestone: ET_2026_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Beyhan Karakaş): status: resolved (was closed) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…

1 0

#2172: Test "Binary black hole GW150914" example
by Beyhan Karakaş 16 Jul '26

16 Jul '26

#2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: closed Milestone: ET_2026_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Beyhan Karakaş): status: closed (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…

1 0

#2172: Test "Binary black hole GW150914" example
by Beyhan Karakaş 16 Jul '26

16 Jul '26

#2172: Test "Binary black hole GW150914" example Reporter: Roland Haas Status: open Milestone: ET_2026_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Beyhan Karakaş): The example was last tested by Yuvraj and website updated. Thank you. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2172/test-binary-black…

1 0

#2964: Test Derivs fails on stampede with NaNs.
by Steven R. Brandt 16 Jul '26

16 Jul '26

#2964: Test Derivs fails on stampede with NaNs. Reporter: Steven R. Brandt Status: new Milestone: Version: Type: bug Priority: major Component: CarpetX According to Claude, the reason the CarpetX derivs test fail on Stampede3 is bad masking logic that fails for 512. Here is Claude's proposed fix. https://github.com/EinsteinToolkit/CarpetX/tree/bug/vec-fix -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2964/test-derivs-fails…

1 0

#2963: ET website inconsistency on Kuibit version for ET_2026_05
by Roland Haas 15 Jul '26

15 Jul '26

#2963: ET website inconsistency on Kuibit version for ET_2026_05 Reporter: Jordan Nicoules Status: resolved Milestone: ET_2026_05 Version: Type: bug Priority: trivial Component: EinsteinToolkit website Changes (by Roland Haas): status: resolved (was open) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2963/et-website-incons…

1 0

#2963: ET website inconsistency on Kuibit version for ET_2026_05
by Roland Haas 15 Jul '26

15 Jul '26

#2963: ET website inconsistency on Kuibit version for ET_2026_05 Reporter: Jordan Nicoules Status: open Milestone: ET_2026_05 Version: Type: bug Priority: trivial Component: EinsteinToolkit website Comment (by Roland Haas): Corrected in git hash [ef67aaa](https://bitbucket.org/einsteintoolkit/www/commits/ef67aaa555a8ac28… "download: bump kuibit to 1.6.1, remove Python version notice" of [www](https://bitbucket.org/einsteintoolkit/www) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2963/et-website-incons…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac July 2026