#720: check at runtime that all REQUIREd and OPTIONAL thorns and capabilities are
active
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
This is an offshot of a discussion on the Cactus developers mailing list:
http://cactuscode.org/pipermail/developers/2011-November/006258.html
On 6 Jan 2012 12:54:13 -0500 eschnett said:
> What is currently missing is the mechanism that checks that all thorns
> providing required capabilities are activated. If they are not, code
> in inactive thorns is called -- this is fine as long as no Cactus
> infrastructure is used (parameters, scheduled routines, grid
> functions, etc.).
>
> Yes, we should implement the respective checks; yes, we should
> automatically activate thorns required for capabilities (and maybe
> some others as well?); yes, we should then output this thorn list to
> the screen (done anyway) and into a file.
>
> By the way, Cactus already determines which thorns need to be
> activated automatically as a service to the user in the error message
> that complains about missing thorns.
The idea seems to be to document all thorns whose code is executed in the
parameter file.
Ian's original need might be served by an "OPTIONAL" statement in
configuration.ccl
(http://einsteintoolkit.org/documentation/UsersGuide/UsersGuidech12.html#x17…)
and some #ifdefs, maybe.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/720>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#929: GRHydro_test_tov_ppm_ML fails intermittently
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: GRHydro |
-----------------------------------+----------------------------------------
The test GRHydro_test_tov_ppm_ML sometimes fails on Datura. This seems to
be nondeterministic. The most recent occurrence of this
(http://git.barrywardell.net/EinsteinToolkitTestResults.git/blob/0fed62edfcc…)
is due to differences in the constraints and vel[0]_norm1.xg very close to
the tolerance. This does not happen every time.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/929>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#988: testsuite can't find MPI when CACTUS_CONFIGS_DIR is set
---------------------+------------------------------------------------------
Reporter: sbrandt | Owner:
Type: defect | Status: new
Priority: minor | Milestone: Cactus_4.1.0
Component: Cactus | Version: development version
Keywords: |
---------------------+------------------------------------------------------
testsuite can't find MPI when CACTUS_CONFIGS_DIR is set, a patch
correcting this problem is attached
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/988>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1037: Update Fortran API for CCTK_LOOP macros
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
----------------------+-----------------------------------------------------
The enclosed patch updates the Fortran API to be equivalent to the C API.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1037>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1098: Carpet does not set up the initial time properly
--------------------+-------------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
Carpet's Intialize.cc contains a typo that causes it to not properly set
the times member of the intial time levels. Instead it stays the C++
default value of 0.
The attached (trivial) patch fixes this.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1098>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1052: use grid::x,x,y in CarpetIOASCII for x,y,z columns
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
-------------------------+--------------------------------------------------
right now CarpetIOASCII computes the "local" coordinates from the lower
boundary coordinate of each patch and CCTK_DELTA_SPACE. This does not work
(as expected) for multipatch.
It would be good to add an option to use grid::x etc instead. Ideally as
both a parameter and an option in the '{}' to choose at runtime and per
variable what to do (eg. to keep the r coordinate around for spherical
patches).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1052>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#762: support git-svn repositories
---------------------------+------------------------------------------------
Reporter: rhaas | Owner: eric9
Type: enhancement | Status: new
Priority: optional | Milestone:
Component: GetComponents | Version:
Keywords: |
---------------------------+------------------------------------------------
I have a number of svn repositories that are each wrapped within a git-svn
checkout (to more easily handle local modifications). It would be nice to
have GetComponents handle these for me in the same way it already handles
svn and git repositories.
With git-svn checkouts are {{{git svn clone URL DIR}}}, updates are {{{git
svn rebase}}}, diff is {{{git diff remotes/git-svn}}} and local changes
have to be stashed the way they are with git.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/762>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1067: Do not interpolate from buffer zones
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version:
Keywords: |
----------------------+-----------------------------------------------------
When interpolating, Carpet currently results results using information
from buffer points. This should not be the case.
To remedy this, in gh.cc::locate_position, after searching the
superregions, check with dh.hh:level_dboxes::active whether the point is
within a buffer region, and if so, use the next coarser grid instead.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1067>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1073: point_classification should not have storage and be removed
--------------------+-------------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: task | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
ClassifyPoints and point_class should be removed from Carpet since right
now they always set the class to 1.
There is interest in having the functionality that the routine and grid
function provide, namely to know at which MoL substep we need to have
valid data at a given point (eg. for con2prim and con2prim failures as
well as possibly skipping computations in buffer regions that are no
longer valid). This could be added to CarpetEvolutionMask quite
straightforwardly, but might require some redefinition of the mask values,
eg. 0 for valid in all MoL substeps, 1 valid until and incl substep 1,
..., MoL_Num_Intermediate_Steps-1 valid only during the first substep,
MoL_Num_Intermediate_Steps for restricted points. This would mean eg an
analysis routine can ignore anything >0 while an evolution routine would
have to check with MoL.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1073>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1082: Enforce that arrangement names can only contain letters, numbers, or
underscores
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
----------------------+-----------------------------------------------------
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1082>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit