Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2691: New features to particle_tracerET
by Gabriele Bozzola 31 Jan '23

31 Jan '23

#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): ``` CCTK_VWarn (1, __LINE__, __FILE__, CCTK_THORNSTRING, "VolumeIntegrals_GRMHD:file_output_routines.C Problem creating directory '%s' " "for output", actual_dir); ``` The thorn name here is `VolumeIntegrals_GRMHD` which is not the correct one. > The thorn’s output is non-standard because it deals with arrays, not grid functions. Each particles' position is evolved using the thorn’s own RK method. Thus each line of the output file looks like “time x\_1 y\_1 z\_1 x\_2 y\_2 z\_2 …” where the subscript is the particle ID and $x,y,z$ the particle position. The positions are already grid arrays, why not outputting those with Carpet directly? E.g., one could directly output `particle_tracerET::particle_position_x`as an HDF5 file in CarpetIOHDF5 $or as an ASCII file in CarpetIOASCII$. $In that case, it would be nice if the size of the array was not hardcoded in the `interface.ccl`$. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-p…

1 0

#2696: Update kuibit to 1.4.0
by Gabriele Bozzola 31 Jan '23

31 Jan '23

#2696: Update kuibit to 1.4.0 Reporter: Gabriele Bozzola Status: new Milestone: ET_2023_05 Version: Type: enhancement Priority: major Component: Comment (by Gabriele Bozzola): In that case, kuibit 1.3.6 will still work. Unfortunately, it is pretty much impossible to support at the same time Python 3.7 and Python 3.11 if I want to ensure that all the dependencies are satisfied and known to be compatible. I am acutely aware of how clusters are stuck back in time, and I tried hard to see if I could squeeze in at least Python 3.7. Given [NEP29](https://numpy.org/neps/nep-0029-deprecation_policy.html), that meant hard-coding a several versions of packages specifically for Python 3.7, and the result was that the dependency solver wouldn’t even convergence. $At the moment, the usage of features available only in Python>3.7 is either 0 or very minimal, so the main problem is with the dependencies.$ We can discuss how to handle this, but form a technical point of view the only solution is to forgo any check on the dependency tree and cross fingers that things will install and work $as 80% of the Python world routinely does anyway$. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2696/update-kuibit-to-…

1 0

#2619: include Ellipitca (reader) in Einstein Toolkit
by Alireza R. 31 Jan '23

31 Jan '23

#2619: include Ellipitca (reader) in Einstein Toolkit Reporter: Roland Haas Status: open Milestone: Version: Type: enhancement Priority: major Component: Comment (by Alireza R.): Hey @{557058:088051f9-5b94-4b5e-bfbe-71137030b9c1} .Yes, I’ll plan to do so. Sure, me and @{5d6ebe02608c0a0dae6f564c} will be attending. Thanks! -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2619/include-ellipitca…

1 0

#2691: New features to particle_tracerET
by Leonardo Werneck 31 Jan '23

31 Jan '23

#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): The thorn’s output is non-standard because it deals with arrays, not grid functions. Each particles' position is evolved using the thorn’s own RK method. Thus each line of the output file looks like “time x\_1 y\_1 z\_1 x\_2 y\_2 z\_2 …” where the subscript is the particle ID and $x,y,z$ the particle position. I do not see the typo in line 43 of `file_output_routines.C`. Could you be more specific? Also note that you are looking at the master branch, but the proposed changes have not been merged yet. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2691/new-features-to-p…

1 0

#2674: Einstein Toolkit != Cactus
by Gabriele Bozzola 31 Jan '23

31 Jan '23

#2674: Einstein Toolkit != Cactus Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: minor Component: Comment (by Gabriele Bozzola): Indeed, I listed it among the stand-alone codes in my message $and the icon in the plot was supposed to represent it$ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2674/einstein-toolkit-…

1 0

#2696: Update kuibit to 1.4.0
by Roland Haas 31 Jan '23

31 Jan '23

#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-…

1 0

#2674: Einstein Toolkit != Cactus
by Roland Haas 31 Jan '23

31 Jan '23

#2674: Einstein Toolkit != Cactus Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: minor Component: Comment (by Roland Haas): Note that there is also the SelfForce-1D code which is part of the ET but not related to Cactus at all. [http://einsteintoolkit.org/components.html](http://einsteintoolkit.org/comp… has a partial list. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2674/einstein-toolkit-…

1 0

#2689: Include NRPyLeakage in next ET release
by Gabriele Bozzola 31 Jan '23

31 Jan '23

#2689: Include NRPyLeakage in next ET release Reporter: Leonardo Werneck Status: new Milestone: ET_2023_05 Version: Type: enhancement Priority: major Component: Comment (by Gabriele Bozzola): Does this fix [https://bitbucket.org/einsteintoolkit/tickets/issues/2497/illinoisgrmhd-is-… ? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2689/include-nrpyleaka…

1 0

#2674: Einstein Toolkit != Cactus
by Gabriele Bozzola 31 Jan '23

31 Jan '23

#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. ![](https://bitbucket.org/repo/8zBLME5/images/129090827-1.png) * 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-…

1 0

#2687: add Fishbone-Moncrief disk gallery example to ET
by Gabriele Bozzola 31 Jan '23

31 Jan '23

#2687: add Fishbone-Moncrief disk gallery example to ET Reporter: Roland Haas Status: new Milestone: Version: Type: enhancement Priority: minor Component: EinsteinToolkit website Comment (by Gabriele Bozzola): I am all for more gallery examples, but I think that the Fishbone-Moncrief thorn should first be fixed $see [https://bitbucket.org/einsteintoolkit/tickets/issues/2503/various-small-pro…). The par file also has lots of commented instructions \(some for thorns that are not in the toolkit$. ‌ ‌ ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2687/add-fishbone-monc…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac