#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
#1352: ExternalLibraries/Lua requires readline-headers
--------------------+-------------------------------------------------------
Reporter: knarf | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Other | Version:
Keywords: |
--------------------+-------------------------------------------------------
ExternalLibraries/Lua requires readline-headers, but there is no check for
it. We could provide a thorn containing it (or forget about the lua thorn
- I don't know of any user right now).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1352>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1363: Crash on startup in Piraha
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: blocker | Milestone: ET_2013_05
Component: Other | Version:
Keywords: |
----------------------+-----------------------------------------------------
I built a Cactus configuration with fewer thorns than usual, and with
assertions disabled (-DNDEBUG. This configuration does not start; it
crashes on startup with a backtrace
{{{
#0 std::_Rb_tree<void*, void*, std::_Identity<void*>, std::less<void*>,
std::allocator<void*> >::_M_insert_unique<void* const&> (this=0x0,
__v=@0x7fff5fbfd228) at locale_facets.h:1078
#1 0x000000010072e6f2 in smart_ptr<piraha::Grammar>::smart_ptr
(this=0x104b9d0d0, ptr=0x10570a5a0, array_=<value temporarily unavailable,
due to optimizations>) at stl_set.h:415
#2 0x0000000100721542 in piraha::AutoGrammar::reparserGenerator () at
AutoGrammar.cc:6
#3 0x0000000100c2ada6 in _GLOBAL__sub_I_Grammar.cc () at smart_ptr.hpp:53
#4 0x00007fff5fc13762 in
__dyld__ZN16ImageLoaderMachO16doInitializationERKN11ImageLoader11LinkContextE
()
}}}
This indicates that the failure oocurs during initialisation of a global
variable during startup. _Rb_tree points to a set or a map. This may be
caused by
{{{
extern smart_ptr<Grammar> pegGrammar;
}}}
I also see that Piraha has some code in smart_ptr.hpp that is only added
when DNEBUG is defined, and contains assert calls (!). Given that NDEBUG
disables assert, this looks like an error.
It is considered bad style to use C++ constructors to initialise global
variables; this is fragile and breaks often. I suggest instead to change
these global variables to pointers, to initialise them to NULL, and to
allocate to respective objects explicitly at run time. This is safer, as
it ensures that things are allocated in the right order.
I also just see that there is a global variables called "ptrs" in Piraha.
This is not good; please use a cctki_ prefix for all globally visible
variables and functions (or move them into a namespace).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1363>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1291: Boundary does not check for storage
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
I accidentally selected a variable for a flat boundary condition (with
thorn Boundary) without storage. This led to a segfault. Instead, thorn
Boundary should output an error message or a warning.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1291>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1369: Error link doesn't work on Mac
---------------------+------------------------------------------------------
Reporter: sbrandt | Owner: sbrandt
Type: defect | Status: new
Priority: major | Milestone: Cactus_4.3.0
Component: Mojave | Version:
Keywords: |
---------------------+------------------------------------------------------
Error link doesn't work on Mac
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1369>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1266: Featue request for Parity Symmetry thorn
---------------------------------+------------------------------------------
Reporter: yosef@… | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version:
Keywords: |
---------------------------------+------------------------------------------
I started looking at runs with parity symmetry, that is the only
symmetry is the simultaneous reflection about x, y, and z. I think
I was able to "implement" this symmetry by changing just a handful of
lines in Rotating180 and I'm a little less sure about my changes to
carpetregrid2. I was wondering, would there be any interest in adding
this symmetry to ET?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1266>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#995: used shared memory on a node to share EOS table
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: EOS_Omni |
-----------------------------------+----------------------------------------
the attached patch has processes on the same node share the memory to
store the EOS table. It required a patch to the flesh to detect the shared
memory support functions in the OS.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/995>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1357: import CartesianCoordiantes into ET
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: optional | Milestone:
Component: Other | Version:
Keywords: |
-------------------------+--------------------------------------------------
CartesianCoordinates provides a minimal Llama Coordiantes interface
providing only Cartesian coordinates. Useful to run thorns that require
Llama when Llama is not available.
The thorn is currently in incoming.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1357>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit