Trac September 2022

trac@lists.einsteintoolkit.org

1 participants
67 discussions

#2485: include complex and real scalar evolution code from Canuda in ET
by Giuseppe Ficarra 05 Sep '22

05 Sep '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 Giuseppe Ficarra): > Oh, yes, sorry.. This is my typo. My point is that compute\_fluxes ==1 with use\_jacobian == true is not available. So, we should add comment saying “Flux can not be computed with multipatch“. perfect, thanks! comment added in [https://bitbucket.org/canuda/scalar/commits/aa56f4304016d6366969c7cd4cd4d95… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2485/include-complex-a…

1 0

#2485: include complex and real scalar evolution code from Canuda in ET
by Taishi Ikeda 05 Sep '22

05 Sep '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 Taishi Ikeda): > Do you mean “use\_jacobian = true“? If you have a look at line 254 of Scalar\_calc\_Tmunu.F90, you can see that there is an if statement that uses the combination "compute\_fluxes==1" and "use\_jacobian=false". Oh, yes, sorry.. This is my typo. My point is that compute\_fluxes ==1 with use\_jacobian == true is not available. So, we should add comment saying “Flux can not be computed with multipatch“. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2485/include-complex-a…

1 0

#2485: include complex and real scalar evolution code from Canuda in ET
by Giuseppe Ficarra 05 Sep '22

05 Sep '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 Giuseppe Ficarra): ScalarEvolve: > In current version, in Scalar\_calc\_Tmunu, "compute\_fluxes==1" and "use\_jacobian=false" is not available....Should we add the comments in param file ? Do you mean “use\_jacobian = true“? If you have a look at line 254 of Scalar\_calc\_Tmunu.F90, you can see that there is an if statement that uses the combination "compute\_fluxes==1" and "use\_jacobian=false". > in schedule, flux grid function is allocated, and Scalar\_zero\_densities is called when compute\_fluxes is true. But, in Scalar\_zero\_densities, flux grid functions are initialized only when use\_jacobian is false. So, if compute\_fluxes is true and use\_jacobian is true, flux grid function is not initialized. fixed in [https://bitbucket.org/canuda/scalar/commits/cb03ec3b4d1bd2e32787ffbf2d32f4d… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2485/include-complex-a…

1 0

#2485: include complex and real scalar evolution code from Canuda in ET
by Giuseppe Ficarra 02 Sep '22

02 Sep '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 Giuseppe Ficarra): added test parameter files in [https://bitbucket.org/canuda/scalar/commits/87e99ae9163e3125f5a3165562beb05… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2485/include-complex-a…

1 0

#2629: MoL_PseudoEvolution vs ANALYSIS
by Gabriele Bozzola 01 Sep '22

01 Sep '22

#2629: MoL_PseudoEvolution vs ANALYSIS Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Gabriele Bozzola): Upon further reflection, and reading more carefully the previous message, my impression is that there’s no easy way to implement a `compute_every` function. I originally implemented the function following `WeylScal4`, which simply takes the modulo of the current iteration and the `compute_every` parameter. But, if I understand what is going on, this is not the correct thing to do, as I can see in my test runs \(unless `compute_every` is 1\). So, should `compute_every` be removed from the `canuda` codes and `WeylScal4` ? \(Or at least, forced to be 1 for backwards compatibility\) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2629/mol_pseudoevoluti…

1 0

#2629: MoL_PseudoEvolution vs ANALYSIS
by Gabriele Bozzola 01 Sep '22

01 Sep '22

#2629: MoL_PseudoEvolution vs ANALYSIS Reporter: Gabriele Bozzola Status: new Milestone: Version: Type: bug Priority: major Component: Comment (by Gabriele Bozzola): It runs, but I am not sure it produces the correct results, so the PRs shouldn’t be merged at the moment. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2629/mol_pseudoevoluti…

1 0

#2485: include complex and real scalar evolution code from Canuda in ET
by Miguel Zilhão 01 Sep '22

01 Sep '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 Miguel Zilhão): ‌ > Also, Rout\_excision1, Rout\_excision2, Rin\_excision1, Rin\_excision2 can be outside grid loop ? fixed in [https://bitbucket.org/canuda/scalar/commits/f0e3b8f2d7c7d943f8002d1f7294404… ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2485/include-complex-a…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac September 2022