Trac June 2017

trac@lists.einsteintoolkit.org

1 participants
96 discussions

[Einstein Toolkit] #1170: ExtrenalLibraries handle XXX_DIR XXX_INC_DIRS and XXX_LIB_DIRS incosistently
by Einstein Toolkit 20 Mar '18

20 Mar '18

#1170: ExtrenalLibraries handle XXX_DIR XXX_INC_DIRS and XXX_LIB_DIRS incosistently -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: Keywords: ExternalLibraries | -----------------------------------+---------------------------------------- This is a companion ticket to #1006. Different thorns (eg. MPI and HDF5 and LAPACK) handle XXX_DIR and XXX_INC_DIRS etc differently. MPI for example sets the include path to $MPI_DIR/include if MPI_INC_DIRS is not explicitly set and to MPI_INC_DIRS if it is set. HDF5 has no HDF5_INC_DIRS option and always sets the include path to HDF5_DIR/include. LAPACK has not INC_DIRS option and sets the linker path to LAPACK_DIR while the other two thorns set it to XXX_DIR/lib (unless overridden by MPI_LIB_DIRS in the case of MPI). I would be good to present a uniform set of option for all these thorns. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1170> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #1769: External libraries: moving towards multiarch library directory structure
by Einstein Toolkit 20 Mar '18

20 Mar '18

#1769: External libraries: moving towards multiarch library directory structure ----------------------------------------------+----------------------------- Reporter: bmundim | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2015_05 Component: EinsteinToolkit thorn | Version: development version Keywords: ExternalLibraries HDF5 Multiarch | ----------------------------------------------+----------------------------- Several Linux distributions have already started to move their libraries to a new directory structure that reflects the target architecture and allows the installation of packages from multiple architectures in the same system. The following links provide more details of this change: {{{ https://wiki.debian.org/Multiarch/TheCaseForMultiarch https://wiki.ubuntu.com/MultiarchSpec }}} This change potentially affects several of external library scripts shipped with ET. For example the HDF5/src/detect.sh script is not able to detect the hdf5 libraries installed in the directory /usr/lib/x86_64 -linux-gnu for Ubuntu 14.04.2 LTS. I have attached a simple patch to remedy this issue and open a discussion on the best way to proceed here. This patch does depend on the availability of gcc on the system. It currently works fine for me, but we might need a better solution for systems without gcc. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1769> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 40

[Einstein Toolkit] #1474: compile ExternalLibraries with other thorns rather than when CST runs
by Einstein Toolkit 20 Mar '18

20 Mar '18

#1474: compile ExternalLibraries with other thorns rather than when CST runs -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: development version Keywords: | -------------------------+-------------------------------------------------- Compiling external libraries takes a long time by now. Currently this happens very early in the compilation phase, before the other thorns are compiled. It would be better if the compilation happened at the same time as that of other thorns. This will entail splitting the configuration ie. detecting whether to build the included source or use a system wide copy from the compilation, most likely either using Cactus makefile variables or temporary files to transfer the decisions from the configuration stage to the build stage. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1474> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 5

[Einstein Toolkit] #1946: sim setup should create a section for the current machine
by Einstein Toolkit 26 Feb '18

26 Feb '18

#1946: sim setup should create a section for the current machine -------------------------+-------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: development version Keywords: | -------------------------+-------------------------------------------------- When calling sim setup on a machine in the machine data base (eg bluewaters in my case) it it still creates only a {{{[default]}}} section in defs.local.ini which means that the account information and possibly non-default sourcebasedir are not used for bluewaters leading to hard to understand error messages later on. I would thus like to suggest to change sim setup such that instead (or in addition to) a "[default]" section it creates a section for the detected machine if it already knows this machine. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1946> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #2050: cctk_startupxxx is a valid group
by Einstein Toolkit 23 Feb '18

23 Feb '18

#2050: cctk_startupxxx is a valid group ---------------------+------------------------------------------------------ Reporter: sbrandt | Owner: sbrandt Type: defect | Status: new Priority: unset | Milestone: Component: Other | Version: development version Keywords: | ---------------------+------------------------------------------------------ Currently, the "at" keyword in the schedule.ccl file is supposed to report an error if one is scheduling in a group that is not present at startup. It detects this with a regexp, but the regexp does not include boundaries. As such cctk_startupxxx is considered valid. In addition, the new parser is failing to report a CST error for this violation regardless of group name. The attached patch to the schedule parser fixes both defects. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2050> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 24

[Einstein Toolkit] #1911: Hydro_InitExcision sphere_pugh_ppm test fails
by Einstein Toolkit 31 Jan '18

31 Jan '18

#1911: Hydro_InitExcision sphere_pugh_ppm test fails ---------------------------+------------------------------------------------ Reporter: barry.wardell | Owner: Type: defect | Status: new Priority: unset | Milestone: Component: Other | Version: development version Keywords: | ---------------------------+------------------------------------------------ The Hydro_InitExcision sphere_pugh_ppm test fails for me when run on 1 process on an Ubuntu 16.04 machine. The diffs are attached. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1911> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 16

[Einstein Toolkit] #2027: testsuite page is not avaiable on website
by Einstein Toolkit 29 Jan '18

29 Jan '18

#2027: testsuite page is not avaiable on website -------------------------------------+-------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit website | Version: development version Keywords: | -------------------------------------+-------------------------------------- The testsuite overview page http://einsteintoolkit.org/release-info/parse_testsuite_results.php does not currently work (since the website changed). -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2027> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1995: McLachlan constraint tests fail
by Einstein Toolkit 26 Jan '18

26 Jan '18

#1995: McLachlan constraint tests fail ---------------------------------------------------------------+------------ Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2016_11 Component: EinsteinToolkit thorn | Version: development version Keywords: McLachlan constraints tests compiler optimization | ---------------------------------------------------------------+------------ Several tests fail on several machines, and the cause seems to be the constraints calculated by McLachlan. Peter is looking into this. We see test failures in the thorns Dissipation and RotatingSymmetry90/180. Indications are that most failures happen with Intel 15, but some are apparently also seen with Intel 16, while others with Intel 16 seem to work fine. Optimization -O1 instead of -O2 seems to prevent the problem, but is not a viable workaround. A simple 'print' statement in the affected (auto-generated) code also makes the problem disappear. Running using one MPI process and one openMP thread reproduces the problem. valgrind does not find anything obvious pointing to memory mess-up. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1995> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 48

[Einstein Toolkit] #2029: GW150914 example should be updated to work with the Einstein Toolkit thornlist
by Einstein Toolkit 25 Jan '18

25 Jan '18

#2029: GW150914 example should be updated to work with the Einstein Toolkit thornlist -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: optional | Milestone: Component: Other | Version: development version Keywords: gallery | -------------------------+-------------------------------------------------- The GW150914 example currently uses its own thornlist, because Llama was not part of the ET when it was created. Llama has now been added to the ET. The GW150914 thornlist uses WaveExtractCPM and ADMConstraints. These can probably be removed, for the sake of having a parameter file which works with the ET thornlist. ADMConstraints can be replaced with ML_ADMConstraints. WaveExtractCPM is an "in-development" code which has not been extensively tested. It gives the GW strain directly from Schwarzschild perturbation theory, without needing to go via fixed- frequency integration of Psi4, so is good for quick plots. However, it seems to give worse results than Psi4 for the ringdown, and possibly has bugs in some of the l > 2 modes, so I don't think it is ready for inclusion in the toolkit just yet. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/2029> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

[Einstein Toolkit] #1725: Disable Fortran 77 support in Cactus
by Einstein Toolkit 24 Jan '18

24 Jan '18

#1725: Disable Fortran 77 support in Cactus -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: unset | Milestone: Component: Other | Version: development version Keywords: | -------------------------+-------------------------------------------------- There are no "Fortran 77" compilers any more. Cactus currently distinguishes between FCODE and F90CODE (pure Fortran 77, and Fortran 90). The pure Fortran 77 code has less argument checking etc. and is less safe, and is not needed any more. It should be removed, both from the makefile system as well as from the CST that auto-generates code. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1725> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 6

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac June 2017