#2696: Update kuibit to 1.4.0
Reporter: Gabriele Bozzola
Status: new
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Roland Haas):
Python3.8 requirements will make kuibit fail \(first one I checked\) to run on stampede2 since it has no available Pyton3.8. Unfortunately for HPC clusters 2019 is “recent”. See:
```text
$ module avail python
-------------------------------- /opt/apps/intel18/impi18_0/modulefiles --------------------------------
python2/2.7.15 (L,D) python3/3.7.0 (D)
------------------------------------ /opt/apps/intel18/modulefiles -------------------------------------
python2/2.7.15 python3/3.7.0
---------------------------------------- /opt/apps/modulefiles -----------------------------------------
python_cacher/1.0 python_cacher/1.2 (D)
Where:
L: Module is loaded
D: Default Module
```
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…
#2674: Einstein Toolkit != Cactus
Reporter: Zach Etienne
Status: new
Milestone:
Version:
Type: bug
Priority: minor
Component:
Comment (by Gabriele Bozzola):
I recently gave a tutorial on the Einstein Toolkit, and made this \(confusing\) image to explain how I personally see our ecosystem.

* The _Einstein Toolkit_ is in the red circle. It includes several different modules.
* The most important module is _Cactus_, a high-performance computational infrastructure.
* Einstein Toolkit includes several components that are built on top of Cactus, these are called _thorns_ \(green circle\). Several thorns that are not part of the Einstein Toolkit exist, some open-source, many private. It is perfectly acceptable for a research group to develop their own thorns for internal use.
* Some of the thorns interact with tools that are not part of the Einstein Toolkit \(e.g., LORENE, but also GSL\). I call them _bridges_ because they interface codes that are developed completely outside of ET and bring functionalities in.
* The Einstein Toolkit also contains codes that do not depend on Cactus at all. I call them _stand-alone codes_, such as Self-force-1D.
* The Einstein Toolkit comes with several \*utilities\*, some that interact with Cactus based codes \(e.g., kuibit\), some that do not. There exist several utilities that work closely with the Einstein Toolkit but are not part of the ET.
* Finally, the Einstein Toolkit would not exist without a decent amount of \*infrastructure\*. In my personal view, this infrastructure is part of the project and its value.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2674/einstein-toolkit-…
#2696: Update kuibit to 1.4.0
Reporter: Gabriele Bozzola
Status: new
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
A new version of kuibit will be available by the time of the next release. The NEWS file contains a detailed list of improvements \([https://github.com/Sbozzolo/kuibit/blob/next/NEWS.md](https://github.com/Sbozzolo/kuibit/blob/next/NEWS.md)\).
Importantly, kuibit 1.4.0 will only support Python 3.8-3.11. Moving the minimum requirement to Python 3.8 is necessary to ensure compatibility with modern versions of NumPy. Python 3.8 was released at the end of 2019.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…
#2695: Inclusion of AsterX pre-release in the Einstein Toolkit
Reporter: Jay Kalinani
Status: new
Milestone:
Version:
Type: enhancement
Priority: minor
Component: EinsteinToolkit thorn
AsterX is a new GRMHD code based on the CarpetX infrastructure. It is currently under development, but is close to the stage where it can be used to simulate systems such as a single magnetized TOV star. Its source code availability in the ET checkout can also serve as a starting point for the ET community to write their own MHD codes or build upon it.
Since AsterX is based on CarpetX, its building requires inclusion of CarpetX in the ET.
The Wiki page with a TODO list is:
[https://docs.einsteintoolkit.org/et-docs/AsterX](https://docs.einsteintoolk…
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2695/inclusion-of-aste…
#2694: include CarpetX prerelease in Einstein Toolkit
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: enhancement
Priority: major
Component: EinsteinToolkit thorn
CarpetX is nearing the point where one can seriously experiment with it. To ease pick up by the ET community it might be good to include its source code in the ET checkout.
Automatically building it will most likely not work due to build option conflicts, incompatible public interfaces and duplicate variable declarations.
A wiki page with a TODO list is:
[https://docs.einsteintoolkit.org/et-docs/CarpetX\_Transition](https://docs.…
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2694/include-carpetx-p…
#2693: Adding read/write support to Baikal and BaikalVacuum
Reporter: Samuel Cupp
Status: new
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: minor
Component: EinsteinToolkit thorn
This update to Baikal and BaikalVacuum adds READ and WRITE declarations to the schedule.ccl files. It also adds a new function `specify_Driver_BoundaryConditions_Baikal*` that calls the function `Driver_SelectVarForBC` to select boundary conditions for all variables and register them with PreSync for automated scheduling. Another small change was the addition of `checkpoint="no"` to some auxiliary and RHS variables which don’t need checkpointing. Copies of the Baikal\* tests are also included with PreSync enabled, so that the thorns can be validated both with and without PreSync.
The PR for the thorn is [https://bitbucket.org/zach\_etienne/wvuthorns/pull-requests/13](https://bit…
and the PR for NRPy\+ to autogenerate the thorn is [https://github.com/zachetienne/nrpytutorial/pull/56](https://github.com/zac….
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2693/adding-read-write…
#2619: include Ellipitca (reader) in Einstein Toolkit
Reporter: Roland Haas
Status: open
Milestone:
Version:
Type: enhancement
Priority: major
Component:
Comment (by Samuel Cupp):
Hey @{5b32699bfa7c4336fcbd9647} . Do you plan for this to be included in the upcoming release? If so, please let us know. If so, it would be great if you or someone else working on this could attend the weekly call this Thursday, as we’ll be deciding what to include in the release during that call.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2619/include-ellipitca…