Trac September 2014

trac@lists.einsteintoolkit.org

1 participants
133 discussions

[Einstein Toolkit] #1641: Switch Slab default from "alltoall" to "irecv/isend"
by Einstein Toolkit 21 Oct '14

21 Oct '14

#1641: Switch Slab default from "alltoall" to "irecv/isend" -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2014_11 Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- The "alltoall" algorithm in Slab does not scale well. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1641> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #1075: Test cases with specific number of processes
by Einstein Toolkit 20 Oct '14

20 Oct '14

#1075: Test cases with specific number of processes -------------------------+-------------------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: Cactus | Version: Keywords: | -------------------------+-------------------------------------------------- Some test cases require a specific number of processes. Instead not running, they should run on that number of processes. This would ensure that all tests execute all the time. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1075> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 40

[Einstein Toolkit] #1158: ExternalLibraries/HDF5 should change the defaults for HDF5_ENABLE_CXX and HDF5_ENABLE_FORTRAN to "no".
by Einstein Toolkit 13 Oct '14

13 Oct '14

#1158: ExternalLibraries/HDF5 should change the defaults for HDF5_ENABLE_CXX and HDF5_ENABLE_FORTRAN to "no". -----------------------------------+---------------------------------------- Reporter: knarf | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- ExternalLibraries/HDF5 should change the defaults for HDF5_ENABLE_CXX and HDF5_ENABLE_FORTRAN to "no". Nothing within the toolkit or Cactus still uses these interfaces and system wide installed libraries might not come with it, leading to link failures. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1158> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 30

[Einstein Toolkit] #1660: Incomplete support for 64 bit architectures in ET build system
by Einstein Toolkit 06 Oct '14

06 Oct '14

#1660: Incomplete support for 64 bit architectures in ET build system ----------------------------------------+----------------------------------- Reporter: joachim.frieben@… | Owner: Type: defect | Status: new Priority: minor | Milestone: ET_2014_05 Component: Cactus | Version: Keywords: | ----------------------------------------+----------------------------------- I am currently trying out the latest ET release and I have stumbled over a minor flaw in the build system: it appears that most of the Cactus/lib/make/extra/*/setup.sh scripts (most of them are really ancient being more than 10 years old) are not 64-bit safe in the sense that the default library directories which are searched for the respective libraries are the 32-bit ones, namely '*/lib/' whereas '*/lib64/' is missing in most cases. In my case of an EL6 clone, not even the system LAPACK package (lapack-(devel)-3.2.1-4.el6.x86_64) is detected correctly. Now that almost everybody is using 64 bit operating systems by default, it would be helpful to extend these files accordingly. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1660> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 9

[Einstein Toolkit] #1388: New thorn MemSpeed
by Einstein Toolkit 02 Oct '14

02 Oct '14

#1388: New thorn MemSpeed -----------------------------------+---------------------------------------- Reporter: eschnett | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- I have written a thorn MemSpeed, available at <https://svn.einsteintoolkit.org/incoming/MemSpeed>. This thorn is useful for performance tuning. I propose to add it to CactusUtils. From the README: Determine the speed of the CPU, as well as latencies and bandwidths of caches and main memory. These provides ideal, but real-world values against which the performance of other routines can be compared. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1388> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 7

[Einstein Toolkit] #1517: Make Simfactory tell you what it's doing
by Einstein Toolkit 29 Sep '14

29 Sep '14

#1517: Make Simfactory tell you what it's doing -------------------------+-------------------------------------------------- Reporter: sbrandt | Owner: eschnett Type: enhancement | Status: new Priority: optional | Milestone: Cactus_4.3.0 Component: SimFactory | Version: development version Keywords: | -------------------------+-------------------------------------------------- Sometimes I'd like to know what shell commands Simfactory is running. This patch causes Simfactory to print out messages of the form "COMMAND: ...." when the --verbose flag is set. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1517> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 20

[Einstein Toolkit] #1659: TestPar/expressions test is failing
by Einstein Toolkit 24 Sep '14

24 Sep '14

#1659: TestPar/expressions test is failing --------------------+------------------------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: development version Keywords: test | --------------------+------------------------------------------------------- The test TestPar/expressions is failing. Details at https://build.barrywardell.net/job/EinsteinToolkitGit/12/testReport/(root)/…. The error is {{{ WARNING level 0 in thorn TestPar processor 0 host caltechcactusjenkins.spdns.org (line 23 of expressions.par): -> Write after read: TestPar::real1[2] }}} The error is correct; the parameter expressions use values from all over the file. I don't know if this was intentional. The ordering is very mixed up. I still don't see the reason for this restriction, but this test parameter file will need to be corrected to follow it. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1659> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #1655: Cannot compile on Mac OS
by Einstein Toolkit 23 Sep '14

23 Sep '14

#1655: Cannot compile on Mac OS ----------------------+----------------------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: critical | Milestone: ET_2014_11 Component: Cactus | Version: development version Keywords: MPI | ----------------------+----------------------------------------------------- I tried to compile the ET on Mac OS using a fresh checkout from yesterday, and got linker errors. {{{ Undefined symbols for architecture x86_64: "_MPI_Abort", referenced from: _CactusDefaultAbort in libthorn_Cactus.a(CactusDefaultComm.c.o) MPI::Comm::Abort(int) in libthorn_PeriodicCarpet.a(periodic.cc.o) MPI::Comm::Abort(int) in libthorn_Carpet.a(helpers.cc.o) MPI::Comm::Abort(int) in libthorn_CarpetEvolutionMask.a(evolution_mask.cc.o) MPI::Comm::Abort(int) in libthorn_CarpetIOASCII.a(ioascii.cc.o) MPI::Comm::Abort(int) in libthorn_CarpetIOBasic.a(iobasic.cc.o) MPI::Comm::Abort(int) in libthorn_CarpetIOHDF5.a(Input.cc.o) }}} This used to work before the recent rewrite of the MPI configure script. I am using the simfactory optionlist osx-mountain-lion-macports-gcc.cfg and OpenMPI from MacPorts. The auto-detection logic in the MPI thorn won't work, as MacPorts uses nonstandard names for the compilation wrappers (mpicc-openmpi-mp mpicxx-openmpi-mp mpiexec-openmpi-mp mpif77-openmpi-mp mpif90-openmpi-mp). However, the optionlist specifies the library locations explicitly, and for some reason this is not working: MPI_DIR = NO_BUILD MPI_INC_DIRS = /opt/local/include/openmpi-mp MPI_LIB_DIRS = /opt/local/lib/openmpi-mp While it would be good for the script to be updated to find the configuration scripts that OpenMPI in MacPorts provides, we should also fix whatever is stopping the explicit settings from working. It should always be possible to configure using the explicit settings; this is more important than having the auto-detection working. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1655> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1652: thorn MPI parses library names wrong if they contain dash
by Einstein Toolkit 18 Sep '14

18 Sep '14

#1652: thorn MPI parses library names wrong if they contain dash --------------------+------------------------------------------------------- Reporter: knarf | Owner: sbrandt Type: defect | Status: new Priority: major | Milestone: ET_2014_11 Component: Cactus | Version: development version Keywords: | --------------------+------------------------------------------------------- mpicc --showme returns on my system: {{{ gcc -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi -pthread -L/usr/lib/openmpi/lib -lmpi -lopen-rte -lopen-pal -ldl -Wl,--export- dynamic -lnsl -lutil -lm -ldl }}} which MPI parses to be {{{ MPI_LIBS = mpi open open dl nsl util m dl }}} (note the missing part after the "open" in two libraries... -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1652> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 1

[Einstein Toolkit] #1651: Problems with expansions in parameter files
by Einstein Toolkit 16 Sep '14

16 Sep '14

#1651: Problems with expansions in parameter files --------------------+------------------------------------------------------- Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: development version Keywords: | --------------------+------------------------------------------------------- If I have a parameter file containing {{{ CoordBase::ymin = -CoordBase::dy * 2 CoordBase::dy = 0.1 }}} it looks like Cactus silently ignores the CoordBase::dy in CoordBase::ymin, and tries to set ymin = 2, presumably because dy has not been set "yet". This raises two points: 1. The parser should raise a fatal error if it does not have a value for a parameter it is expanding; 2. The order of parameters listed in the parameter file should not matter. I think that parameter files should be declarative rather than imperative; i.e. you should think of them as a static mapping from parameter names to values rather than as a program which sets (and resets?) variables in the sequence written in the parameter file. A simple way to transform the current "set each parameter in sequence" implementation would be to sort the assignments so that parameters are set before they are used, and to raise a fatal error if a parameter is set twice. Would it be possible to implement this? -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1651> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 19

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac September 2014