Trac

trac@lists.einsteintoolkit.org

8708 discussions

#2834: Baikal regeneration instruction in README fail
by Zach Etienne 08 Nov '24

08 Nov '24

#2834: Baikal regeneration instruction in README fail Reporter: Roland Haas Status: new Milestone: ET_2024_11 Version: Type: bug Priority: major Component: Comment (by Zach Etienne): Largely this is a README issue: Only codes requiring NRPy generation will populate the thorns, so test/ doc/ and par/ will not be populated just by running NRPy. Instead, src/ and \*.ccl files should be deleted in the thorns and replaced with generated codes. The README should be updated to reflect this. In addition, there have been some minor reshufflings to improve maintainability, diagnostics, and performance, including 1. computing the squared momentum constraint \(MSQUAREDGF\). 2. sorting the parameters in param.ccl in a case-insensitive alphabetical way. 3. replacing pow\(x, -1/6\) with 1 / sqrt\(cbrt\(x\)\) \(it is faster!\) 4. Starting all function-level comment blocks with /\*\* instead of /\* . This enables syntax highlighting of @param \[parameter name\] in all IDEs I tried \(emacs & vscode\). 5. simd/simd\_intrinsics.h has been tidied up a bit, and a few new intrinsics \(currently unused by Baikal\*, but used by other \[future ET\] NRPy projects\) were added. The above changes reflect the Baikal\* thorns in the latest `NRPy-main`. Should I proceed in updating the README to use this? There is no functional change. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2834/baikal-regenerati…

1 0

#2834: Baikal regeneration instruction in README fail
by Roland Haas 08 Nov '24

08 Nov '24

#2834: Baikal regeneration instruction in README fail Reporter: Roland Haas Status: new Milestone: ET_2024_11 Version: Type: bug Priority: major Component: README says: > 4. Regenerating these thorns > > Baikal and BaikalVacuum can be automatically generated via > > pip install git\+[https://github.com/nrpy/nrpy.git@79774f69b2911fe5729b2d256c7e1fe754c2… python3 -m nrpy.examples.carpet\_baikal\_thorns > > The second command will generate the thorns in project/et\_baikal/ > and can then be copied into the WVUThorns directory. Yet following these I am missing the `test`, `doc` and `par` directories as well as the `README` file and get very many differences. Most of the differences are harmless \(comments\) but same changes affect `CCTK_ATTRIBUTE_NOINLINE` which, being something that Zach found to be required to cut down compilation time, is important. So currently I cannot regenerate the Baikal thorns. ‌ attachment: vacuum.diff (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) attachment: matter.diff (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2834/baikal-regenerati…

1 0

#2818: failing tests with gcc-14
by Roland Haas 08 Nov '24

08 Nov '24

#2818: failing tests with gcc-14 Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Failing tests have been addressed in git hash [81e426ff](https://github.com/EinsteinToolkit/CarpetX/commits/81e426ffe9bdfe… "Loop: explicitly create function args to avoid compiler issue" of [CarpetX](https://github.com/EinsteinToolkit/CarpetX) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2818/failing-tests-wit…

1 0

#2818: failing tests with gcc-14
by Roland Haas 08 Nov '24

08 Nov '24

#2818: failing tests with gcc-14 Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): Pull request for original issue \(failing tests\) is [https://github.com/EinsteinToolkit/CarpetX/pull/319](https://github.com/Ein… -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2818/failing-tests-wit…

1 0

#2818: failing tests with gcc-14
by Roland Haas 08 Nov '24

08 Nov '24

#2818: failing tests with gcc-14 Reporter: Roland Haas Status: open Milestone: Version: Type: bug Priority: major Component: EinsteinToolkit thorn Comment (by Roland Haas): The negative array index warning is actually from within AMReX: ```text COMPILING CarpetX/CarpetX/src/reduction.cxx In file included from /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/scratch/external/AMReX/include/AMReX_Box.H:9, from /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/scratch/external/AMReX/include/AMReX_BaseFab.H:9, from /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/scratch/external/AMReX/include/AMReX_FArrayBox.H:6, from /data/rhaas/postdoc/gr/cactus/ET_Next/arrangements/CarpetX/Loop/src/loop.hxx:4, from /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/bindings/include/loop.hxx:4, from /data/rhaas/postdoc/gr/cactus/ET_Next/arrangements/CarpetX/CarpetX/src/driver.hxx:4, from /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/build/CarpetX/reduction.cxx:1: In member function ?constexpr int& amrex::IntVectND<dim>::operator[](int) [with int dim = 3]?, inlined from ?amrex::Box amrex::BATbndryReg::operator()(const amrex::Box&) const? at /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/scratch/external/AMReX/include/AMReX_BoxArray.H:223:25: /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/scratch/external/AMReX/include/AMReX_IntVect.H:240:79: warning: array subscript -1 is below array bounds of ?int [3]? [-Warray-bounds=] 240 | int& operator[] (int i) noexcept { BL_ASSERT(i>=0 && i < dim); return vect[i]; } | ~~~~^ /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/scratch/external/AMReX/include/AMReX_IntVect.H: In member function ?amrex::Box amrex::BATbndryReg::operator()(const amrex::Box&) const?: /data/rhaas/postdoc/gr/cactus/ET_Next/configs/sim/scratch/external/AMReX/include/AMReX_IntVect.H:788:9: note: while referencing ?amrex::IntVectND<3>::vect? 788 | int vect[dim] = {}; | ^~~~ ``` and from the output I cannot see who may be calling `amrex::Box amrex::BATbndryReg::operator()(const amrex::Box&)` other than “somewhere in `reduction.cxx`". -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2818/failing-tests-wit…

1 0

#2175: Test "Single, stable neutron star" example
by Roland Haas 07 Nov '24

07 Nov '24

#2175: Test "Single, stable neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2024_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by Roland Haas): uploading only the new one should be sufficient. Maybe add a comment to #2520 that before you updated the parfile everything looked the same as before to document that the change observed is only due to the changed gauge. -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2175/test-single-stabl…

1 0

#2175: Test "Single, stable neutron star" example
by David Boyer 07 Nov '24

07 Nov '24

#2175: Test "Single, stable neutron star" example Reporter: Roland Haas Status: open Milestone: ET_2024_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Comment (by David Boyer): @{557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22} I have run the gallery example and everything looks good, same outcome as before. The new runs are tarred up and ready to go. However, I have also rerun the test with the new gauge settings from ticket #2520, and now since I know what I need to do, I could upload those instead if you like, taking out both tickets at the same time. Would this alternative be preferred? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2175/test-single-stabl…

1 0

#2173: Test "Poisson equation" example
by Roland Haas 07 Nov '24

07 Nov '24

#2173: Test "Poisson equation" example Reporter: Roland Haas Status: open Milestone: ET_2024_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was []) milestone: ET_2024_11 (was ET_2024_05) assignee: Lucas Timotheo Sanches (was Steven R. Brandt) Comment (by Roland Haas): @{5f2f18c8e8c45600229698f5} will run this for 2024-11 -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equa…

1 0

#2173: Test "Poisson equation" example
by Roland Haas 07 Nov '24

07 Nov '24

#2173: Test "Poisson equation" example Reporter: Roland Haas Status: open Milestone: ET_2024_05 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): status: open (was resolved) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2173/test-poisson-equa…

1 0

#2174: Test "Multi Patch Scalar Wave Equation" example
by Roland Haas 07 Nov '24

07 Nov '24

#2174: Test "Multi Patch Scalar Wave Equation" example Reporter: Roland Haas Status: open Milestone: ET_2024_11 Version: development version Type: task Priority: major Component: EinsteinToolkit website Changes (by Roland Haas): responsible: [] (was []) assignee: William Gabella (was Lucas Timotheo Sanches) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2174/test-multi-patch-…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac