Trac

trac@lists.einsteintoolkit.org

8708 discussions

[Einstein Toolkit] #1287: Allow setting parameters at build time
by Einstein Toolkit 25 Mar '13

25 Mar '13

#1287: Allow setting parameters at build time -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- Allow setting parameter values at build time, enabling additional compiler optimisations. I measured that e.g. ML_BSSN runs 5% to 10% faster if its parameters are chosen at build time. This introduces macros CCTK_PARAMETER__${thorn}__${parameter}. If unset, the parameter value is taken from the parameter file (default). If set at compile time, e.g. via a -D option in CPPFLAGS, this overrides the parameter database, and DECLARE_CCTK_PARAMETERS will always use this value. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1287> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1293: Improved documentation for thorn CactusNumerical/Dissipation
by Einstein Toolkit 22 Mar '13

22 Mar '13

#1293: Improved documentation for thorn CactusNumerical/Dissipation ---------------------------------------+------------------------------------ Reporter: bernard.j.kelly@… | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: ET_2012_11 Keywords: documentation dissipation | ---------------------------------------+------------------------------------ I've added to the documentation for the Dissipation thorn, since what was there was just a pointer to the Kreiss & Oliger paper. Now there's an expression for what actually happens in the thorn, and some discussion of the main parameters. I've added my name to the author list. I also changed the date by hand, but perhaps the CMS will over-ride this when/if committed. Attaching the full " documentation.tex" file, and the result of "git diff" against the latest stable releast (ET_2012_11). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1293> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1272: Disable shared libraries for all ExternalLibraries
by Einstein Toolkit 19 Mar '13

19 Mar '13

#1272: Disable shared libraries for all ExternalLibraries -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- Having a shared library build by an ExternalLibraries thorn means that the executable will not be self-contained, potentially leading to segfaults during long-running simulations. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1272> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 10

[Einstein Toolkit] #1285: Commits to LSUThorns/PeriodicCarpet do not go to the ET commits mailing lists
by Einstein Toolkit 14 Mar '13

14 Mar '13

#1285: Commits to LSUThorns/PeriodicCarpet do not go to the ET commits mailing lists -----------------------------------+---------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- Commits to LSUThorns/PeriodicCarpet do not go to the ET commits mailing lists. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1285> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1288: off-line source code extractor for Formaline
by Einstein Toolkit 11 Mar '13

11 Mar '13

#1288: off-line source code extractor for Formaline -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: Formaline | -----------------------------------+---------------------------------------- the attached python script for gdb allows one to extract the source tarballs from a formaline enabled executable, even if one is unable to runs the code anymore. Would that be of interest to be included in Formaline's utils folder? Usage is: gdb -P formaline.py exe/cactus_sim which will dump the tarballs in the current directory. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1288> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1286: SimFactory should not run queued chained jobs if a previous job fails
by Einstein Toolkit 11 Mar '13

11 Mar '13

#1286: SimFactory should not run queued chained jobs if a previous job fails -------------------------+-------------------------------------------------- Reporter: hinder | Owner: eschnett Type: enhancement | Status: new Priority: major | Milestone: Component: SimFactory | Version: Keywords: | -------------------------+-------------------------------------------------- When a simulation consists of multiple chained jobs, the failure of one job is likely to lead to the failure of subsequent jobs. Possible reasons for failure of a job include: 1. Running out of disk quota; 2. An error in the code; 3. A numerical problem; 4. A problem with the cluster Of all these, only the last could potentially be recovered from by simply running the next job in the chain, and in any case, if this is done immediately, it is likely to fail because the problem may not have resolved itself. As a result, to avoid wasting CPU hours on the remaining jobs in the chain, I think simfactory should hold or remove the subsequent chained jobs. Probably removing the jobs would be easier and simpler, and users can always run "submit" on them to restart them. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1286> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #624: Replace Cactus complex number implementation with C/C++ standard implementation
by Einstein Toolkit 08 Mar '13

08 Mar '13

#624: Replace Cactus complex number implementation with C/C++ standard implementation -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- Cactus offers CCTK_COMPLEX. This maps to the standard datatype in Fortran, but not in C or C++. It should map to the standard datatypes in C and C++ as well, so that the growing body of code written in C and C++ can reasonably make use of complex numbers. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/624> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1148: New thorn CactusTest/TestCrayPointers
by Einstein Toolkit 08 Mar '13

08 Mar '13

#1148: New thorn CactusTest/TestCrayPointers -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: | -----------------------------------+---------------------------------------- I want to add a thorn CactusTest/TestCrayPointers that tests whether the Cray pointer syntax is accepted by the Fortran compiler. If so, please create the respective repository. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1148> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1284: Want stand-alone parameter parser
by Einstein Toolkit 08 Mar '13

08 Mar '13

#1284: Want stand-alone parameter parser -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- I would like to have an easy-to-use stand-alone parameter file parser. Presumably, this utility would be build as a Cactus utility in the flesh. I would take a parameter file as input, and would output parameter values as output (probably either in some ASCII format or in xml). It would also know about default values of parameters. This utility could answer the following questions: - which parameters are set in a parameter file? - what is the value of parameter X (which may have its default value)? - list all parameters that are set in the parameter file - list all parameters and their values Bonus points if it also knows about which thorns are active; this is non- trivial since some thorns are activated automatically. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1284> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 8

[Einstein Toolkit] #1277: GRHydro updates
by Einstein Toolkit 05 Mar '13

05 Mar '13

#1277: GRHydro updates -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: GRHydro | -----------------------------------+---------------------------------------- mostly Christian Reisswig's work on WENO and MP5 reconstruction in GRHydro. One trivial patch to remove a parfile for test output. Will commit on Wednesday unless objections are raised. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1277> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac