Trac

trac@lists.einsteintoolkit.org

8708 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

#2539: Unable to compile on Ubuntu 20.04 or run executable
by Steven R. Brandt 24 Jun '21

24 Jun '21

#2539: Unable to compile on Ubuntu 20.04 or run executable Reporter: Jason Kodish Status: open Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: SimFactory Comment (by Steven R. Brandt): What do you see when you type `free -h`? -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…

1 0

#2539: Unable to compile on Ubuntu 20.04 or run executable
by Jason Kodish 23 Jun '21

23 Jun '21

#2539: Unable to compile on Ubuntu 20.04 or run executable Reporter: Jason Kodish Status: open Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: SimFactory Comment (by Jason Kodish): I've attached the make.log file here as requested -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…

1 0

#2539: Unable to compile on Ubuntu 20.04 or run executable
by Jason Kodish 23 Jun '21

23 Jun '21

#2539: Unable to compile on Ubuntu 20.04 or run executable Reporter: Jason Kodish Status: open Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: SimFactory Comment (by Jason Kodish): <div class="preview-container wiki-content"></div> <div class="mask"></div> </div> </div> </form> -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…

1 0

#2539: Unable to compile on Ubuntu 20.04 or run executable
by Roland Haas 23 Jun '21

23 Jun '21

#2539: Unable to compile on Ubuntu 20.04 or run executable Reporter: Jason Kodish Status: open Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: SimFactory Comment (by Roland Haas): I just gave the instructions a try on a freshly installed and updated Ubuntu 20.04 VM. I could compile fine followign the instructions from the tutorial, which probably matches \(mostly\) with what Steve’s suggestion would achieve. So: worksforme. Since it clearly fails for you, one needs to find out why. Unfortunately the partial error output that was provided is not quite enough to do so. Instead the full build log would be helpful. Namely if you could attach the file `make.log` produced by: ```shell make sim-realclean VERBOSE=yes ./simfactory/bin/sim build -j1 sim 2>&1 | tee make.log ``` ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…

1 0

#2539: Unable to compile on Ubuntu 20.04 or run executable
by Steven R. Brandt 23 Jun '21

23 Jun '21

#2539: Unable to compile on Ubuntu 20.04 or run executable Reporter: Jason Kodish Status: open Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: SimFactory Comment (by Steven R. Brandt): I didn’t see the original email. He should try running the following: ``` sudo apt-get install -y libjpeg-turbo?-dev gcc git liblapack-dev make subversion g++ libpapi-dev libhwloc-dev hwloc rsync libopenmpi-dev libhdf5-openmpi-dev libssl-dev numactl gfortran libhdf5-dev libfftw3-dev patch libgsl-dev pkg-config ``` ‌ -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…

1 0

#2539: Unable to compile on Ubuntu 20.04 or run executable
by Roland Haas 23 Jun '21

23 Jun '21

#2539: Unable to compile on Ubuntu 20.04 or run executable Reporter: Jason Kodish Status: open Milestone: Version: ET_2021_05 Type: bug Priority: minor Component: SimFactory Changes (by Roland Haas): priority: minor (was blocker) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…

1 0

#2539: Unable to compile on Ubuntu 20.04 or run executable
by Roland Haas 23 Jun '21

23 Jun '21

#2539: Unable to compile on Ubuntu 20.04 or run executable Reporter: Jason Kodish Status: open Milestone: Version: ET_2021_05 Type: bug Priority: blocker Component: SimFactory Changes (by Roland Haas): status: open (was new) -- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2539/unable-to-compile…

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac