#1540: Use clang for automated testing
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
We should use Clang for automated testing, maybe in addition to GCC. Clang
is known for having better diagnostics than GCC. Point in case: Clang
discovered the C/C++ incompatibility for complex numbers that GCC ignored.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1540>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1534: Bug in complex numbers
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: critical | Milestone:
Component: Cactus | Version: development version
Keywords: |
----------------------+-----------------------------------------------------
I hear that C++ "complex<double>" and C "complex double" may have
different ABI properties. This means that we need to correct Cactus's
complex number implementation, probably using C's "complex double".
I hear that this makes Cactus complex numbers unusable on 32-bit Intel
systems (untested).
See <http://llvm.org/bugs/show_bug.cgi?id=18756> for details.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1534>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1539: Simfactory: update loewe entries
-------------------------+--------------------------------------------------
Reporter: bmundim | Owner: eschnett
Type: enhancement | Status: new
Priority: major | Milestone:
Component: SimFactory | Version: development version
Keywords: loewe |
-------------------------+--------------------------------------------------
The attached patch applies cleanly both to trunk and Noether release.
* It updates the loewe machine database entries.
* Avoid Boost and MPI compilation.
* Fix chaining jobs in its submit script.
Is it ok to apply to both repos?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1539>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1512: LoopControl slows down with time when exloring new tilings
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version: development version
Keywords: LoopControl |
-------------------------+--------------------------------------------------
the attached parfile does nothing but apply the periodic boundary
condition over and over again. The run slows down with time, and spends
more and more time in Slab's apply routine (Periodic just uses lots of
calls to Slab). Digging further this caused by LoopControl and in
particular setting
{{{
LoopControl::settle_after_iteration = 0
}}}
restores the expected behaviour, namely that the runtime in Pariodic/apply
increases linearly with the number of timesteps rather than superlinearly.
I blind guess for the culprit is the std::map inside of loopcontrol. I
have done no further digging into the code though.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1512>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1532: simfactories enabled-thorns does not check if a to be enabled thorn is
actually present
------------------------+---------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version: development version
Keywords: |
------------------------+---------------------------------------------------
if one uses the default ET thornlist for download then transfers the
cechkout to eg bluewaters then tries to build there then the build fails
since thorns are not found:
{{{
------------------------------------------------------
Warnings were generated during execution of the CST
------------------------------------------------------
CST error 1:
-> Missing thorn CactusExamples/WaveToyOpenCL
CST error 2:
-> Missing thorn CactusUtils/Accelerator
CST error 3:
-> Missing thorn CactusUtils/OpenCLRunTime
CST error 4:
-> Missing thorn ExternalLibraries/OpenCL
CST error 5:
-> Missing thorn McLachlan/ML_WaveToy_CL
}}}
Reading the resolution to #919 it seesm as if enabled-thorns should have
been removed from the mdb but seems to not have been.
I think enabled-thorns should be either removed and/or simfactory should
check before activating (uncommenting) a thorn in the thornlist that the
activated thorn actually exists.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1532>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1530: GRHydro updates
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Other | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
A large number of GRHydro updates have accumulated. Attached please find
them all as well as a required update to EOS_Omni.
Patches to follow in a bit.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1530>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1529: Included clickable link to archived posting in users list emails
-------------------------------------+--------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: optional | Milestone:
Component: EinsteinToolkit website | Version: development version
Keywords: |
-------------------------------------+--------------------------------------
I find myself often wanting to cite an email on the user's list in eg
track tickets and usually want to provide a url to the email in the
mailing list archive for this. Right now this requires me to manually
navigate to the mailman archive
(http://lists.einsteintoolkit.org/pipermail/users/) click on the relevant
year and month and find the posting in question based on its subject line
and author.
It would be very nice is the emails were tagged with a unique identifier
that could then be used to retrieve it from the mailing list archive (and
if this tag showed up eg in the footer that already contains the url of
the listinfo page). One such identifier that may be available would be the
message number (eg 003400 for
http://lists.einsteintoolkit.org/pipermail/users/2014-January/003400.html).
I have no idea how hard providing this would be though.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1529>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1117: Wrong CarpetIOASCII headers for complex 2D output.
----------------------------------------+-----------------------------------
Reporter: reisswig@… | Type: defect
Status: new | Priority: minor
Milestone: | Component: Other
Version: | Keywords:
----------------------------------------+-----------------------------------
I am outputting a 2d _complex_ array (called "extracted_vars") using 2d
CarpetIOASCII output.
Using the standard output format, the data starts at column 13.
So the first array element "extracted_vars[0]" is at column 13.
Now, since I have a complex array, the second element,
"extracted_vars[1]", must be at column 15 (column 14 contains the
imaginary part of element [0]). In older versions of Carpet, this was
reported correctly in the header. In the current version, it is incorrect.
The second element, "extracted_vars[1]" is reported to be in column 14
instead of 15.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1117>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#542: Remove thorn CactusArchive/ADM from thorn list
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: task | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
Remove thorn CactusArchive/ADM from thorn list. This thorn is outdated,
and we should updated out test cases instead. It also takes a long time
and a lot of memory to compile.
If we want an ADM formulation (which is doubtful since we don't use it
ourselves), we should implement one via Kranc.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/542>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#114: per-variable tolerances for Cactus testsuites
-------------------------+--------------------------------------------------
Reporter: knarf | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: ET_2011_06
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
It would be nice to be able to specify per-variable testsuite tolerances
in Cactus (per regexp for the name in the ideal case).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/114>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit