#1699: Don't disable NoExcision on Hydra any more
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Other | Version: development version
Keywords: |
----------------------+-----------------------------------------------------
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1699>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1695: Kranc-generated thorns should be regenerated before the ET_2014_11 release
--------------------+-------------------------------------------------------
Reporter: hinder | Owner:
Type: task | Status: new
Priority: major | Milestone: ET_2014_11
Component: Other | Version: development version
Keywords: |
--------------------+-------------------------------------------------------
Kranc-generated thorns should be regenerated with the current version of
Kranc before the ET_2014_11 release.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1695>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#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
#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
#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
#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
#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
#1692: change paths in manifest/einsteintoolkit.th to be able to use GetComponents
to restore missing symbolic links
---------------------------+------------------------------------------------
Reporter: rhaas | Owner: eric9
Type: defect | Status: new
Priority: minor | Milestone:
Component: GetComponents | Version: development version
Keywords: |
---------------------------+------------------------------------------------
This patch changes the CHECKOUT path description of the git repos that are
checked out whole into directories (manifest, utils, CoreDoc among them).
Most likely due to way GetComponents decides if a component is already
checked out, the previous version would not succeed in actually restoring
a missing "manifest" symbolic link when it was deleted manually and
GetComponents used to restore it. Ie.
GetComponents
https://bitbucket.org/einsteintoolkit/manifest/raw/master/einsteintoolkit.th
cd Cactus
rm manifest
bin/GetComponents repos/manifest/einsteintoolkit.th
will not restore manifest.
Pull request is here: https://bitbucket.org/einsteintoolkit/manifest/pull-
request/3/einsteintoolkitth-change-checkout-so-that/diff
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1692>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1685: Access of freed memory in CarpetIOHDF5 during 1-Proc test of recoverML-
EE.par
---------------------+------------------------------------------------------
Reporter: sbrandt | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version: development version
Keywords: |
---------------------+------------------------------------------------------
I originally found the problem with clang, but have verified it with
valgrind. A parameter is being freed by CCTK_SetString() in Misc.c, but is
reused by CarpetIOHDF5. To reproduce, I build with clang, after commenting
out the papi and hwloc thorns. Commenting out the call to free in
CCTK_SetString() reveals alignment errors in LoopControl. I'm attaching
the cfg file I used to build with clang.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1685>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit