#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
Comment (by Leonardo Werneck):
@{5bae587b96242d2e2b6110a4} will be the reviewer.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2693/adding-read-write…
#2690: Include new IllinoisGRMHD with tabulated and hybrid EOS support
Reporter: Leonardo Werneck
Status: new
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Leonardo Werneck):
@{557058:088051f9-5b94-4b5e-bfbe-71137030b9c1} will be the reviewer.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2690/include-new-illin…
#2694: include CarpetX prerelease in Einstein Toolkit
Reporter: Roland Haas
Status: new
Milestone:
Version:
Type: enhancement
Priority: major
Component: EinsteinToolkit thorn
Comment (by Samuel Cupp):
After discussion, CarpetX will be included in the November 2023 release, but the code review will begin during the 2023\_05 release due to the complexity of a driver thorn and its importance as a core component for future work in the Toolkit.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2694/include-carpetx-p…
#2695: Inclusion of AsterX pre-release in the Einstein Toolkit
Reporter: Jay Kalinani
Status: new
Milestone:
Version:
Type: enhancement
Priority: minor
Component: EinsteinToolkit thorn
Comment (by Samuel Cupp):
After discussion, the AsterX developers decided to delay the addition of AsterX into the Toolkit until the November 2023 release to align with the planned CarpetX full release.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2695/inclusion-of-aste…
#2691: New features to particle_tracerET
Reporter: Leonardo Werneck
Status: new
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Roland Haas):
Not having read most of the remainder of the ticket nor looked at the code. it can also be useful to in cases like this, add:
```
CarpetIOASCII::compact_format = yes
```
which removes a lot of the extra whitespace and comments \(but also changes the column mapping so you must not rely on say column 10 being “time” and have to parse the header on top for a column name to column mapping\).
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-p…
#2691: New features to particle_tracerET
Reporter: Leonardo Werneck
Status: new
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Leonardo Werneck):
Gabriele---
Upon further discussion, the functionality you seek is already provided by the thorn, although it is not its default behavior. For example, the following non-standard output configuration:
```
particle_tracerET::output_freq = 4
particle_tracerET::output_format = "ascii" # Default
```
can be made standard by doing
```
particle_tracerET::output_freq = 0
<...>
CarpetIOASCII::out1D_every = 128 # Or whatever
CarpetIOASCII::out1D_vars = "
<...>
particle_tracerET::particle_position_arrays{out_every=4}
"
```
Note that in the standard output the particle positions would be in the file `particle_traceret-particle_position_arrays.x.asc`, while the non-standard output file is named `particles.asc`. In fact one can enable both outputs at the same time using e.g.,
```
particle_tracerET::output_freq = 4
<...>
CarpetIOASCII::out1D_every = 128 # Or whatever
CarpetIOASCII::out1D_vars = "
<...>
particle_tracerET::particle_position_arrays{out_every=particle_tracerET::output_freq}
"
```
Granted, this is not well documented, so we should add this to the thorn’s documentation.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-p…
#2697: Include BBH+scalar field initial data code from Canuda in ET
Reporter: Cheng-Hsin Cheng
Status: new
Milestone:
Version:
Type: enhancement
Priority: minor
Component:
We propose for inclusion the thorns TwoPunctures\_BBHSF and NPScalars\_SF from Canuda/Scalar. The codes are hosted in the UIUC branch: [https://bitbucket.org/canuda/scalar/src/Canuda\_SF\_UIUC/](https://bitbucke…
TwoPunctures\_BBHSF is an initial data solver based on TwoPunctures for a black hole binary plus a cloud of massive scalar field. Namely, it solves the Hamiltonian constraint for the BBH system with back-reaction from a massive scalar field minimally-coupled to GR. Currently, it supports scalar field configurations with vanishing initial momentum and a spherically symmetric or dipolar angular profile, centered at the origin.
NPScalars\_SF is an extension of the NPScalars thorn that computes the gravito-electric and gravito-magnetic fields taking into account contributions from the massive scalar field.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2697/include-bbh-scala…
#2691: New features to particle_tracerET
Reporter: Leonardo Werneck
Status: new
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Leonardo Werneck):
We can add the standard Cactus output as an option as well, but as far as I know the default output will have to remain as is for the sake of backwards compatibility.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-p…
#2691: New features to particle_tracerET
Reporter: Leonardo Werneck
Status: new
Milestone: ET_2023_05
Version:
Type: enhancement
Priority: major
Component:
Comment (by Gabriele Bozzola):
\(The thorn name got fixed in the PR, so ignore my first point!\)
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-p…