Trac August 2022

trac@lists.einsteintoolkit.org

1 participants
121 discussions

#2629: MoL_PseudoEvolution vs ANALYSIS
by Gabriele Bozzola 31 Aug '22

31 Aug '22

#2629: MoL_PseudoEvolution vs ANALYSIS Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Gabriele Bozzola): I guess the solution is to leave it up to the user to make sure the they set the correct value for “compute\_every”. Here’s two PR: [https://bitbucket.org/canuda/lean\_public/pull-requests/6/address-2629-amon… [https://bitbucket.org/canuda/proca/pull-requests/5/npscalars\_proca-compute… Everything compiles and runs. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2629/mol_pseudoevoluti…

1 0

#2629: MoL_PseudoEvolution vs ANALYSIS
by Roland Haas 30 Aug '22

30 Aug '22

#2629: MoL_PseudoEvolution vs ANALYSIS Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Roland Haas): In the call I said I knew how to do the scheduling in MoL\_PseudoEvolution. Turns out that this is not true. Here’s my current thoughts: ```text rl=0 delta_t=4.0 timefac=1 rl=1 delta_t=2.0 timefac=2 rl=2 delta_t=1.0 timefac=4 it == 0: rl=0 t_of_level=0.0 rl=1 t_of_level=0.0 rl=2 t_of_level=0.0 it == 1: rl=0 t_of_level=4.0 rl=1 t_of_level=2.0 rl=2 t_of_level=1.0 it == 2: rl=2 t_of_level=2.0 it == 3: rl=1 t_of_level=4.0 rl=2 t_of_level=3.0 it == 4: rl=2 t_of_level=4.0 if wanting to compute every Delta_t = 4.0 which is every 4 iterations, need to evaluate at: it = 0 for rl=0,1,2 and it = 1 for rl=0 it = 3 for rl=1 it = 4 for rl=2 ``` and I am not sure to to come up with an expression that involves only `iteration`, `timefac` and the `every` value that would give those iterations \(ie not referring to the unknown maximum `timefac` value in the simulation\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2629/mol_pseudoevoluti…

1 0

#2635: Remove warning in GRHydro_InitData
by Roland Haas 30 Aug '22

30 Aug '22

#2635: Remove warning in GRHydro_InitData Reporter: Zach Etienne Status: resolved Milestone: Version: Type: bug Priority: major Component: Changes (by Roland Haas): status: resolved (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2635/remove-warning-in…

1 0

#2635: Remove warning in GRHydro_InitData
by Roland Haas 30 Aug '22

30 Aug '22

#2635: Remove warning in GRHydro_InitData Reporter: Zach Etienne Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Roland Haas): Fixed in git hash [8e3dda4](https://bitbucket.org/einsteintoolkit/einsteinevolve/commits/8e3dd… "GRHydro\_InitData: check for curvilinear grid at runtime" of [einsteinevolve](https://bitbucket.org/einsteintoolkit/einsteinevolve) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2635/remove-warning-in…

1 0

#2637: update Cactus COPYRIGHT file to LGPL
by Roland Haas 30 Aug '22

30 Aug '22

#2637: update Cactus COPYRIGHT file to LGPL Reporter: Roland Haas Status: new Milestone: Version: Type: bug Priority: minor Component: Cactus Cactus originally used GPL with a spelled out exception that linking is exempt from the GPL copyleft, ie the same exception that LGPL used. Some time ago \(around 2015, see eg commit logs in cactus\* repos\) we switched to explicitly using LGPL and updated the README files. Cactus itself however was forgotten \(has no README file, but has COPYRIGHT\). Pull request [https://bitbucket.org/cactuscode/cactus/pull-requests/144](https://bitbucke… addresses this. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2637/update-cactus-cop…

1 0

#2549: inlcude FLRWSolver in ET
by Zach Etienne 29 Aug '22

29 Aug '22

#2549: inlcude FLRWSolver in ET Reporter: Roland Haas Status: new Milestone: ET_2022_05 Version: development version Type: enhancement Priority: major Component: Comment (by Zach Etienne): @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} : Yes that was the warning I saw. Probably innocuous but better to be safe than sorry, by looking into it. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…

1 0

#2549: inlcude FLRWSolver in ET
by Roland Haas 29 Aug '22

29 Aug '22

#2549: inlcude FLRWSolver in ET Reporter: Roland Haas Status: new Milestone: ET_2022_05 Version: development version Type: enhancement Priority: major Component: Comment (by Roland Haas): Sure. I can move it. Some groups like the “branding” of the arrangement. Any location is fine with me though \(well except the Cactus\* locations which come with special license requirements\). I will update the thornlist. @{557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278} the warning you saw was that: ``` /data/rhaas/postdoc/gr/cactus/ET_trunk/arrangements/FLRWSolver/FLRWSolver/src/powerspec_ics.F90:16: Warning: While tracing include dependencies: Include file "fftw3.f03" not found Searched in thorn directory and in [/data/rhaas/postdoc/gr/cactus/ET_trunk/configs/sim/build/FLRWSolver/../FFTW3, /data/rhaas/postdoc/gr/cactus/ET_trunk/configs/sim/build/FLRWSolver/../SpaceMask] Checking status of thorn IDBrillData ``` ? If so the most likely it can be ignored. It is due to Cactus trying to set up makefile dependencies for include files in Fortran code. Those are maybe non-trivial \(and may not correctly take ExternalLibraries into account, being rarely used\). If that is the one then it is no showstopper though I will try and take a look \(reluctant as I am to change anything in that part of CST, fearing ripple effects if I touch anything…\). -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2549/inlcude-flrwsolve…

1 0

#2485: include complex and real scalar evolution code from Canuda in ET
by Roland Haas 29 Aug '22

29 Aug '22

#2485: include complex and real scalar evolution code from Canuda in ET Reporter: Roland Haas Status: open Milestone: Version: Type: task Priority: major Component: Comment (by Roland Haas): Taishi confirmed \(private email\) that the thorns do no harm. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2485/include-complex-a…

1 0

#2636: CoordinateSymmetry has a parameter `rotating_90` that is never used
by Roland Haas 29 Aug '22

29 Aug '22

#2636: CoordinateSymmetry has a parameter `rotating_90` that is never used Reporter: Gabriele Bozzola Status: resolved Milestone: Version: Type: bug Priority: major Component: Changes (by Roland Haas): status: resolved (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2636/coordinatesymmetr…

1 0

#2636: CoordinateSymmetry has a parameter `rotating_90` that is never used
by Roland Haas 29 Aug '22

29 Aug '22

#2636: CoordinateSymmetry has a parameter `rotating_90` that is never used Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Roland Haas): Thank you. Fixed as git hash [a2b11a0](https://bitbucket.org/llamacode/llama/commits/a2b11a0fa79f99336d4c… "CoordinateSymmetry: remove unused parameter" of [llama](https://bitbucket.org/llamacode/llama) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2636/coordinatesymmetr…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac August 2022