Trac June 2014

trac@lists.einsteintoolkit.org

1 participants
124 discussions

[Einstein Toolkit] #1555: Simfactory: intel optionlists with rdynamic option
by Einstein Toolkit 10 Nov '14

10 Nov '14

#1555: Simfactory: intel optionlists with rdynamic option -------------------------+-------------------------------------------------- Reporter: bmundim | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: ET_2014_05 Component: SimFactory | Version: development version Keywords: | -------------------------+-------------------------------------------------- Hi, While reviewing some options in my config file I noticed that the -rdynamic gcc option for the linker is applied also to the intel compiler option lists in symfactory. However there seems to have no such an option when using icc or icpc. Wouldn't be better then to pass this option as --export-dynamic directly to the linker ld instead? Maybe as follows: LDFLAGS = -Wl,--export-dynamic -Wl,-rpath,/path/to/whatever instead of LDFLAGS = -rdynamic -Wl,-rpath,/path/to/whatever Thanks, Bruno. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1555> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1490: ExternalLibraries/PAPI contains testsuite, but no data
by Einstein Toolkit 10 Nov '14

10 Nov '14

#1490: ExternalLibraries/PAPI contains testsuite, but no data -----------------------------------+---------------------------------------- Reporter: knarf | Owner: Type: defect | Status: new Priority: minor | Milestone: ET_2014_05 Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- ExternalLibraries/PAPI contains testsuite, but no data. This means the testsuite mechanism (currently) will count it always as succeeding, which is not helpful. Also, it contains a README file which only says that this directory is empty - which is not only not helpful, but also wrong, given that there is this README inside.. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1490> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[Einstein Toolkit] #1481: Hidden hard-coded limits on max_l_modes and max_vars in Multipole
by Einstein Toolkit 10 Nov '14

10 Nov '14

#1481: Hidden hard-coded limits on max_l_modes and max_vars in Multipole --------------------------------------+------------------------------------- Reporter: bernard.j.kelly@… | Owner: Type: defect | Status: new Priority: major | Milestone: ET_2013_11 Component: EinsteinToolkit thorn | Version: ET_2013_05 Keywords: Multipole | --------------------------------------+------------------------------------- The EinsteinAnalysis/Multipole thorn has hard-coded limits (in src/multipole.cc) on the number of grid functions that can be decomposed (max_vars) and how high in polar quantum number this decomposition can go (max_l_modes). However, these are not reflected in the thorn's param.ccl. In fact, param.ccl contains a parameter "l_max", allowing it to be *any* positive value, and doesn't test this against max_l_modes until execution of this source. Wouldn't it make more sense to impose max_l_modes immediately at PARAMCHECK? To make the actual limit on interpolated functions explicit, a number of desired interpolants could be set in param.ccl (like "n_variables") --- limited if necessary to a hard-coded number that appears as a limit in the range. If the user tries to set n_variables too high, it gets caught at PARAMCHECK; if (s)he accidentally includes too many entries in the "variables" parameter, the extra ones would just be silently ignored. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1481> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1360: TAT/TATPETSc has no (ET-only) testsuite
by Einstein Toolkit 10 Nov '14

10 Nov '14

#1360: TAT/TATPETSc has no (ET-only) testsuite -----------------------------------+---------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: minor | Milestone: ET_2013_11 Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- It would be nice if TATPETSc, being part of the ET, would have at least one testsuite that can actually run using the ET only. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1360> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 3

[Einstein Toolkit] #1317: GRHydro should provide _one_ mechanism to set a GP to atmosphere
by Einstein Toolkit 10 Nov '14

10 Nov '14

#1317: GRHydro should provide _one_ mechanism to set a GP to atmosphere -----------------------------------+---------------------------------------- Reporter: knarf | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: | -----------------------------------+---------------------------------------- GRHydro should provide _one_ mechanism to set a GP to atmosphere which should then be used whenever that should be the case. Right now, this is copied in several places. -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1317> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 4

[Einstein Toolkit] #1598: ExternalLibraries/MPI does not auto-detect openmpi on Debian/testing
by Einstein Toolkit 01 Nov '14

01 Nov '14

#1598: ExternalLibraries/MPI does not auto-detect openmpi on Debian/testing -----------------------------------+---------------------------------------- Reporter: rhaas | Owner: Type: defect | Status: new Priority: minor | Milestone: Component: EinsteinToolkit thorn | Version: development version Keywords: MPI | -----------------------------------+---------------------------------------- configure.sh expects to find libmpi.a in $MPI_DIR/lib however Debian no longer delivers a static libmpi.a but only libmpi.so so the tests fails. The fix is likely similar to what HDF5 already does (ie accept any of .a .so .dylib as extensions for libraries). The fix is a bit complex though, so (given that Debian/stable is still fine) this is a reminder for after the release. Explictly specifying MPI_DIR, MPI_INC_DIRS, MPI_LIB_DIRS and MPI_LIBS allows this to be worked around in the current release. For reference, the fragment from HDF5 looks like this: {{{ # We look in these directories DIRS="/usr /usr/local /usr/local/hdf5 /usr/local/packages/hdf5 /usr/local/apps/hdf5 /opt/local ${HOME} ${HOME}/hdf5 c:/packages/hdf5" # look into each directory for dir in $DIRS; do # libraries might have different file extensions for libext in a so dylib; do # libraries can be in /lib or /lib64 for libdir in lib64 lib; do # These files must exist FILES="include/hdf5.h $(for lib in ${HDF5_CXX_LIBS} ${HDF5_FORTRAN_LIBS} ${HDF5_C_LIBS}; do echo ${libdir}/lib${lib}.${libext}; done)" # assume this is the one and check all needed files HDF5_DIR="$dir" for file in $FILES; do # discard this directory if one file was not found if [ ! -r "$dir/$file" ]; then unset HDF5_DIR break fi done # don't look further if all files have been found if [ -n "$HDF5_DIR" ]; then break fi done # don't look further if all files have been found if [ -n "$HDF5_DIR" ]; then break fi done # don't look further if all files have been found if [ -n "$HDF5_DIR" ]; then break fi done }}} -- Ticket URL: <https://trac.einsteintoolkit.org/ticket/1598> Einstein Toolkit <http://einsteintoolkit.org> The Einstein Toolkit

1 2

[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] #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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Trac June 2014