#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
#832: ExternalLibraries/zlib gives bad error message if "patch" is not available
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
The PATCH variable is used in the zlib configuration script but there is
no check that it has been set. It is also not declared in the
configuration.ccl as being used. Should all environment variables used in
the script be declared? PATCH is usually set by autoconf, unless it is
unavailable, in which case it is not set.
Replacing $PATCH with ${PATCH?} would be enough to give a sensible error
message. I don't know if there are versions of bash that would not
understand this.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/832>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1096: parallelize LocalInterp using OpenMP
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: LocalInterp |
-----------------------------------+----------------------------------------
the attached patch parallelizes the interpolation loop in
CactusNumerical/LocalInterp (which provides "uniform cartesian"
interpolation) using OpenMP.
A test using it is InterpToArray's wavetoy test which still passes.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1096>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1091: use efficient RK4 in multirate RK4 RK2 scheme
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: MoL |
-------------------------+--------------------------------------------------
This patch cleans up the code, improves performance of the MoL loops since
it combines several loops into one, and reduces the required scratch
space.
Code originally by Erik, the imported into Zelmani by Christian Reisswig.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1091>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit