#892: correct column headers hen both one_file_per_group and
all_reductions_in_one_file are active
--------------------+-------------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
the column labels were sorted the wrong way if both options were active
(nesting of loops was wrong). The attached patches correct this and add
test cases for all 4 combinations of one_file_per_group and
all_reductions_in_one_file.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/892>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#729: RotatingSymmetry90 as applied to pseudo vectors fail
-----------------------------------+----------------------------------------
Reporter: bmundim | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: RotatingSymmetry90 |
-----------------------------------+----------------------------------------
Hi,
doing some tests today with RotatingSymmetry90 today I noticed the
symmetry conditions were not applied correctly for Bvec as defined by
hydrobase:
CCTK_REAL Bvec[3] type = GF Timelevels = 3
tags='ProlongationParameter="HydroBase::prolongation_type"
tensortypealias="U" tensorparity=-1 interpolator="matter"' "Magnetic field
components B^i"
The parity settings used to work until recently. Does anyone know what
could be causing this problem?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/729>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#525: Clean up CCTK_GFINDEX definitions
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
The way in which CCTK_GFINDEX is defined is a bit complex, probably
unnecessarily so. The file cctk.h distinguishes between compilers which
support inlining and compilers which don't. This is probably useless these
days since every compiler supports inlining, and if not, we don't really
expect it to be fast.
If the compiler supports inlining, we define static inline functions,
which may or may not check array indices. If the compiler does not support
inlining, and if CCTK_DEBUG is defined, then we use regular functions
defined in DebugDefines.c, otherwise (i.e. without CCTK_DEBUG) we use
macros.
Overall, the indexing functions are defined three times, including once as
macros. I suggest to simplify this, based on the assumption that every
fast compiler supports inlining. I assume so because (a) the ubiquity of
C++, which relies heavily on inlining, and (b) C99 officially introduced
inlining 12 years ago.
The new setup would have "static inline" definitions (without index
checking) in cctk.h, and would have regular functions (with index
checking) in DebugDefines.c, and would choose between these two
implementations via CCTK_DEBUG.
This would eliminate the macros, and would eliminate the case distinction
based on whether the compiler supports inlining.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/525>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#879: CCZ4 variant of McLachlan should be documented
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: ET_2012_05
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
The CCZ4 variant of McLachlan should be documented. The McLachlan
documentation currently consists of the file
Cactus/arrangements/McLachlan/doc/mclachlan.tex.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/879>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#867: Add parameter to poison periodic boundaries
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
Add a parameter to poison periodic boundaries before the periodicity
condition is applied. This allows detecting errors in the periodicity
boundary condition, which does not work if there are multiple local
components per process.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/867>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#870: Support real*16 (and real*4) in GRHydro
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
Support using precisions other than real*8 in GRHydro by removing all
explicit references to double precision functions and constants, and
using type-generic functions and constants instead.
In particular, use "one" and "half" as constants in some places, and
use "abs", "max" etc. instead of "dabs", "dmax" etc.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/870>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#890: Fix to ePPM reconstruction
----------------------+-----------------------------------------------------
Reporter: reisswig | Type: defect
Status: new | Priority: major
Milestone: | Component: EinsteinToolkit thorn
Version: | Keywords: GRHydro, ePPM
----------------------+-----------------------------------------------------
This is a bug fix to the ePPM scheme.
The velocity components were reconstructed from the plus face values!
This is clearly incorrect.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/890>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#871: Use SQLite as Formaline back-end
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
Use SQLite as Formaline back-end instead of storing the information in
ASCII files.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/871>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit