#181: AEILocalInterp should not off-centre the interpolation stencil by default
----------------------------+-----------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: AEILocalInterp |
----------------------------+-----------------------------------------------
AEILocalInterp by default will off-centre the interpolation stencil if
there are insufficient points to perform the interpolation. In a parallel
setting, this could happen due to there being insufficient ghost points
for the interpolator chosen. The off-centering leads to an interpolation
error which is of the correct order but larger than for a centered
stencil. More importantly, it leads to different results on different
numbers of processes. This violates a basic design principle of Cactus,
and the expectation of users, that changing the number of processors
should not change the results of a simulation.
I propose that instead of silently off-centering the stencil,
AEILocalInterp should abort with an error indicating that there are
insufficient ghost-zones. The interpolator options corresponding to this
are:
boundary_off_centering_tolerance={0.0 0.0 0.0 0.0 0.0 0.0}
boundary_extrapolation_tolerance={0.0 0.0 0.0 0.0 0.0 0.0}
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/181>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#778: Compiling PittNullCode is slow
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
Compiling PittNullCode is very slow on some systems (e.g. with gcc). I
believe this is because files such as NullConstr_R00.F90 contain many
whole-array operations that the compiler has to analyse.
I suggest to rewrite these routines, using e.g. forall or do loops. If we
want to keep the elegant, index-free notation, then I suggest to add an
elemental subroutine for the actual calculations and calling it with whole
arrays.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/778>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1181: Parameter file parsing error message is hidden
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
----------------------+-----------------------------------------------------
Parse errors in parameter files are hidden among other output, and are
thus difficult to spot. This example shows this:
{{{
cactus::cctk_itlast = 3 ;
ActiveThorns = "HDF5"
}}}
The problem is that the error message is output among the activation
messages. If the parameter file is long and the syntax error is in the
beginning, then several hundred lines may be output after the error
message, which makes it very difficult to spot it.
The parsing errors should be output in the same way as other parameter
errors, which are prefixed by WARNING etc.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1181>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1100: Correct backtrace generation in Carpet
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version:
Keywords: |
----------------------+-----------------------------------------------------
The file backtrace.cc in CarpetLib does not #include <cctk.h>; hence all
HAVE_BACKTRACE* macros are undefined, and only basic backtraces are
generated.
Correcting this is non-trivial, since the backtrace code is arcane, is
written in C, probably expects glibc, contains (I'm fairly certain) memory
allocation errors, and doesn't build e.g. on Mac OSX. The code also spends
an inordinate amount of time allocating and freeing string buffers, which
should be replaced by simply using C++ streams.
The backtrace code also probably requires a few more autoconf tests, so
that it can be disabled where it does not work.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1100>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#914: Don't use fork()
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
It seems that it is in many cases not safe to call fork() in MPI
applications. This page <http://www.open-mpi.de/faq/?category=openfabrics
#ofa-fork> has some information. The upshot seems to be:
- In many (most) cases, one can call system() or popen() to execute
external processes while waiting for them.
- It is generally not safe to call fork() to execute a certain task in the
background. However, it should be possible to use threads in this case.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/914>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#260: produce map of ET users
-------------------------------------+--------------------------------------
Reporter: knarf | Owner:
Type: enhancement | Status: new
Priority: optional | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
It would be nice to produce an (autmatically generated) map of the
locations of ET users
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/260>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#980: Remove support for the flesh-based MPI mechanism
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
The flesh-based MPI mechanism has just been deprecated in favour of
ExternalLibraries/MPI. Even though the latter is new, it is probably a
good idea to completely disable the old mechanism since having any mixture
of thorns/optionlists using the old and new mechanisms is completely
untested and will likely lead to problems and confusion. It's better to
give a useful fatal error message if someone still specifies "MPI = " in
their optionlist than to have things break in other weird and wonderful
ways.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/980>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#64: Refactory/redesign archiving
------------------------+---------------------------------------------------
Reporter: mthomas | Owner: mthomas
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
Implement archiving using archive machines with an iomethod key. Provide
another key like rsync-excludes for people to exclude files from being
archived. Provide a lightweight archive-like method for copying a
simulation from one machine to another machine.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/64>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#984: SimFactory should store the optionlist used when building in the simulation
directory
------------------------+---------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
SimFactory should store the optionlist used in the simulation directory
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/984>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#583: PITTNullCode lacks test case outputs
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
The PITTNullCode arrangement has several test parameter files without
associated output.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/583>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit