Trac July 2021

trac@lists.einsteintoolkit.org

1 participants
3 discussions

#2541: some predefined schedule bins missing from documentation
by Anonymous 25 Jul '21

25 Jul '21

#2541: some predefined schedule bins missing from documentation Reporter: Status: new Milestone: Version: development version Type: bug Priority: trivial Component: Cactus website The Cactus docs on schedule.ccl https://www.einsteintoolkit.org/usersguide/UsersGuide.html#x1-51000C1.2.3 currently only list: ``` CCTK_STARTUP For routines, run before the grid hierarchy is set up, for example, function registration. CCTK_PARAMCHECK For routines that check parameter combinations, routines registered here only have access to the grid size and the parameters. CCTK_BASEGRID Responsible for setting up coordinates, etc. CCTK_INITIAL For generating initial data. CCTK_POSTINITIAL Tasks which must be applied after initial data is created. CCTK_PRESTEP Stuff done before the evolution step. CCTK_EVOL The evolution step. CCTK_POSTSTEP Stuff done after the evolution step. CCTK_ANALYSIS For analysing data. ``` which is missing (at least): * `CCTK_POSTPOSTINITIAL` * `CCTK_WRAGH` * `CCTK_SHUTDOWN` * `CCTK_TERMINATE` * `CCTK_PREREGRID` * `CCTK_POSTREGRID` * the `INITIAL` variants of pre and postregrid -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2541/some-predefined-s…

1 0

#2540: Unexpected Hamiltonian violation from Carpet boundaries, using CCZ4
by Roland Haas 22 Jul '21

22 Jul '21

#2540: Unexpected Hamiltonian violation from Carpet boundaries, using CCZ4 Reporter: KennethZen Status: new Milestone: ET_2020_05 Version: ET_2020_05 Type: bug Priority: major Component: Carpet Comment (by Roland Haas): Peter Diener addressed some of this in the mailing list: [http://lists.einsteintoolkit.org/pipermail/users/2021-July/008064.html](htt… ‌ > It is expected that the mesh refinement boundaries will reflect Hamiltonian constraint violations. From what you have provided us, it is not clear whether the level of constraint violations that you see is a cause of concern. You specifically mention CCZ4, but have you tried with BSSN? Does the constraint violations look better, the same, or worse with BSSN? > > It is also possible that an issue like this might be caused by some other problem potentially related to parameter settings, so in order to investigate this can you provide your thornlist and parameter file? ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2540/unexpected-hamilt…

1 0

#2540: Unexpected Hamiltonian violation from Carpet boundaries, using CCZ4
by KennethZen 06 Jul '21

06 Jul '21

#2540: Unexpected Hamiltonian violation from Carpet boundaries, using CCZ4 Reporter: KennethZen Status: new Milestone: ET_2020_05 Version: ET_2020_05 Type: bug Priority: major Component: Carpet While using CCZ4 to simulate a single star, the Hamiltonian constraint violation initially came from the star surface as expected, but after some time, the violation was dominated by areas near corners of refinement levels \(by Carpet\) as shown in following figures, which were strange. Any suggestions? Thanks and regards, KZ attachment: dowload_0.png (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) attachment: download.png (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) attachment: download_1.png (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) attachment: download_2.png (https://api.bitbucket.org/2.0/repositories/einsteintoolkit/tickets/issues/2…) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2540/unexpected-hamilt…

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac July 2021