Trac July 2026

trac@lists.einsteintoolkit.org

1 participants
59 discussions

#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): I will remove the minimum Python version clause as this seems to not be consistently maintainable. -- 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): The kuibit docs https://sbozzolo.github.io/kuibit/1.6.1/index.html say "The minimum version of Python required is 3.9." -- 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): on the other hand, the downloads page says "# requires Python3 version 3.7 or greater" while the release description file on Zenodo (https://zenodo.org/records/21298233) says "assumes Python3 version 3.6.1 or greater". -- 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 Changes (by Roland Haas): status: open (was new) -- 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 Jordan Nicoules 15 Jul '26

15 Jul '26

#2963: ET website inconsistency on Kuibit version for ET_2026_05 Reporter: Jordan Nicoules Status: new Milestone: ET_2026_05 Version: Type: bug Priority: trivial Component: EinsteinToolkit website The [download page](https://einsteintoolkit.org/download.html) shows > ```pip install --user -U kuibit==1.5.0 # requires Python3 version 3.7 or greater``` while the [ET_2026_05 announcement](https://einsteintoolkit.org/about/releases/ET_2026_05_announc… rightfully indicates > pip install --user -U kuibit==1.6.1 -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2963/et-website-incons…

1 0

#2962: Split the ET
by Steven R. Brandt 11 Jul '26

11 Jul '26

#2962: Split the ET Reporter: Steven R. Brandt Status: new Milestone: Version: Type: enhancement Priority: major Component: Cactus Current toolkit problems: (1) CarpetX replaces low-level interfaces, e.g. ADMBase with ADMBaseX which leads to massive breakage and duplication of code. (2) The list of thorns in the ET has become massive. It takes a long time to compile and test. (3) There's always been this ambiguity in the name of our software product vs. the name of the umbrella name. I.e. the thing built from einsteintoolkit.th is "The Einstein Toolkit", but the same term applies to the thing build from einsteintoolkit.th and to Peter's self-force code collectively. Proposed solution to all of these problems: Split into two thornlists, one for carpet and one for carpetx, each to be built and tested separately. This means, for example, that ADMBaseX could be renamed to ADMBase and still remain completely distinct. TwoPunctures could compile and run without modification in either collection of thorns. In addition, we could provide flags -DCARPET or -DCARPETX which thorns could use to write conditional code if only a minor modification would be needed to make a code compatible with either framework. A little farther down the road down the road, we might consider renaming ODESolvers to MoL and making them look a little more uniform. Each codebase would have a distinct name: "The Carpet Toolkit"/"The CarpetX Toolkit" seem fairly logical. It would also eliminate the ambiguity in the name ET. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2962/split-the-et

1 0

#2961: util_ExpressionEvaluate fails with custom evaluator
by Roland Haas 09 Jul '26

09 Jul '26

#2961: util_ExpressionEvaluate fails with custom evaluator Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: Cactus Comment (by Roland Haas): Now it does. One needs to name a variable with a ""::" in it (note that `util_ExpressionEvaluate` is not supposed to make *any* assumption about the allowed names of variables). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2961/util_expressionev…

1 0

#2961: util_ExpressionEvaluate fails with custom evaluator
by Roland Haas 09 Jul '26

09 Jul '26

#2961: util_ExpressionEvaluate fails with custom evaluator Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: Cactus Comment (by Roland Haas): Uh, correction, the SEGFAULT was a fault of mine. Now of course the simple test case works. Will need to make it more like Trigger t trigger a failure I guess. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2961/util_expressionev…

1 0

#2961: util_ExpressionEvaluate fails with custom evaluator
by Roland Haas 09 Jul '26

09 Jul '26

#2961: util_ExpressionEvaluate fails with custom evaluator Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: Cactus Changes (by Roland Haas): responsible: [] (was ) assignee: Steven R. Brandt (was ) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2961/util_expressionev…

1 0

#2961: util_ExpressionEvaluate fails with custom evaluator
by Roland Haas 09 Jul '26

09 Jul '26

#2961: util_ExpressionEvaluate fails with custom evaluator Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: major Component: Cactus The piraha provides `util_ExpressionEvaluate` fails when passed a custom evaluator. For Trigger (see #1077) it tries to evaluate a string itself (it should pass it to the evaluator) for the test case of the original utils code (in cactustest/testexpr https://bitbucket.org/cactuscode/cactustest/branch/rhaas/testexpr) it produces a SEGFAULT (parfile is in par). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2961/util_expressionev…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac July 2026