#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
#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
#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
#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
#2021: compiling Carpet fails with intel 17 and optimisation
-----------------------------------------+----------------------------------
Reporter: wolfgang.kastaun@… | Owner: eschnett
Type: defect | Status: new
Priority: unset | Milestone:
Component: Carpet | Version:
Keywords: |
-----------------------------------------+----------------------------------
Compiling carpet with intel 17.0.1 and -O2 or -O3 triggers an internal
compiler error ("internal error: 0_76"). It only affects the file bbox.cc.
Happened on two different clusters. ET version is Payne.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2021>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2072: Carpet: Disable OpenMP parallelization of transport operators
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner: eschnett
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Carpet | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
This disables the OpenMP parallelization of Carpet's transport operators.
I have observed that this leads to a significant speedup when many threads
are used.
The likely reason is that the regions which are parallelized are typically
small. A typical reason would e.g. be the lower x-boundary of one
component of one grid variable. The OpenMP thread startup overhead and the
cache misses caused by parallelizing this are then larger than any
benefit.
See <https://bitbucket.org/eschnett/carpet/pull-requests/18/carpet-
disable-openmp-parallelization-of/diff>.
In a next step (not proposed here), we can parallelize transport operators
again, but at a much higher level, e.g. at the level of the loop over all
variables that need to be prolongated. However, Carpet currently (and
quite unfortunately) uses static variables to hold pointers to timers, and
these are not thread-safe. (Neither the static variables nor the timer
implementation itself are.) This needs to be either corrected or disabled,
which will be the topic of a further pull request.
At this time, I ask some of those who are interested in performance in
trying this pull request on a few iterations of a production simulation
that uses many OpenMP threads and report back here.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2072>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1784: osx-homebrew.cfg does not work out of the box on Yosemite
------------------------+---------------------------------------------------
Reporter: anonymous | Owner:
Type: task | Status: new
Priority: optional | Milestone:
Component: SimFactory | Version: ET_2015_05
Keywords: |
------------------------+---------------------------------------------------
When installing ET anew on Yosemite with the instructions in
osx-homebrew.cfg, the build fails because homebrew gets the latest version
of gcc (5.1), which is currently not the one then specified in the cactus
compilation options (4.9).
This problem was encountered by a student who approached ET for the first
time.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1784>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1757: Stampede needs to be updated
----------------------+-----------------------------------------------------
Reporter: hinder | Owner:
Type: task | Status: new
Priority: critical | Milestone:
Component: Other | Version: development version
Keywords: backport |
----------------------+-----------------------------------------------------
The SimFactory definition for Stampede currently uses the intel/13.1.1.163
compiler. This compiler will be removed next Tuesday (see
https://portal.tacc.utexas.edu/user-guides/stampede/intel15). According
to TACC, the current default is the older intel/13.0.2.146, and this is
the recommended and default compiler, and will remain so. Both compilers
have the "restrict" keyword blacklisted in Cactus (#1276). They will
install intel/15.0.1 at the end of April. There is also intel/14.0.1.106
available, but it is labeled as "limited software stack". It is not clear
why they are removing a newer compiler, or why they chose to do this a
month before installing an even newer one.
Our options are:
1. Upgrade to intel/14.0.1.106, which is labeled as "limited software
stack"
2. Downgrade to intel/13.0.2.146, which is the default and will remain so
for a while
This should be done both for the trunk and the release branch. I suggest
that option 2 is the most conservative, and probably the easiest, as there
might be libraries which are not compiled for intel/14.0.1.106.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1757>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2007: MoL fails to build with Intel compiler
---------------------+------------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: blocker | Milestone:
Component: Cactus | Version: development version
Keywords: |
---------------------+------------------------------------------------------
Compiling MoL gives this error:
{{{
/home/ianhin/Cactus/EinsteinToolkitGit/arrangements/CactusNumerical/MoL/src/RK4-RK2.c(60):
error: unrecognized OpenMP #pragma
#pragma omp /*parallel for*/
^
compilation aborted for
/home/ianhin/Cactus/EinsteinToolkitGit/configs/sim/build/MoL/RK4-RK2.c
(code 2)
}}}
This code was introduced in
https://bitbucket.org/cactuscode/cactusnumerical/commits/09a209266daa281a3e….
Removing the commented portion doesn't help. Replacing it with
{{{
#pragma omp parallel
}}}
allows the code to compile.
This is on Minerva, with icc (ICC) 16.0.1 20151021.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2007>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1458: intel 13 2013.1.117 miss-compiles asserts in TwoPunctures tp_utils.c
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: TwoPunctures |
-----------------------------------+----------------------------------------
this continues the thread in #1429 in particular
https://trac.einsteintoolkit.org/ticket/1429#comment:14.
Currently we need to determine which versions are affected.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1458>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit