#147: Write transition guide for EOS_Omni
-------------------------------------+--------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
The Einstein Toolkit pages need a wiki tutorial for switching to EOS_Omni.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/147>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#162: Document CCTK_GFINDEX3D and friends in reference manual
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
----------------------+-----------------------------------------------------
I believe the reference manual does not describe any of the CCTK_GFINDEX*
and CCTK_VECTGFINDEX* functions.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/162>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#367: When a repo URL changes, GetComponents should offer more help
---------------------------+------------------------------------------------
Reporter: eschnett | Owner: eric9
Type: enhancement | Status: new
Priority: major | Milestone:
Component: GetComponents | Version:
Keywords: |
---------------------------+------------------------------------------------
When a repo URL changes, GetComponents currently suggests to check out the
repo from scratch (and presumably delete/ignore the old repo). This is
very inflexible, in particular when the user has changes in the old
repository, which often happens during development.
SVN (and presumably all other VC software) offer commands to update the
URL, so that one can keep the current checkout. Of course, this makes only
sense if this is the same repository that only moved to a new URL, but
this seems to happen often enough.
GetComponents should at least output instructions for updating the URL.
It would be even better if GetComponents detected that new and old repo
are the same, and then update the repo URL by itself.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/367>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#494: CarpetReduce tests nonstaggered and staggered fail with development version
of Carpet
--------------------+-------------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
The CarpetReduce tests nonstaggered and staggered fail with the
development version of Carpet and pass with the stable version. The
failure is reported as:
weight.d.asc: substantial differences
did not reproduce 3 NaNs from old weight.d.asc
significant differences on 3 (out of 9) lines
Were the NaNs wrong before, and somehow got into the test output
incorrectly? Or are the NaNs supposed to be there?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/494>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#414: --parallel option not documented in GetComponents
---------------------------+------------------------------------------------
Reporter: bmundim | Owner: eric9
Type: defect | Status: new
Priority: minor | Milestone:
Component: GetComponents | Version:
Keywords: |
---------------------------+------------------------------------------------
The --parallel option is not documented in both versions of GetComponents,
the released and development ones.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/414>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#219: ExternalLibraries method should be documented
---------------------------+------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: documentation |
---------------------------+------------------------------------------------
The Cactus documentation
http://einsteintoolkit.org/info/documentation/UsersGuide/UsersGuidech6.html…
(scroll down to Compiling with Extra Packages)
currently tells people to use the "extras" method for enabling access to
external libraries such as HDF5, MPI etc. As I understand it, this method
is deprecated in favour of the ExternalLibraries method, and both should
not be used at the same time for the same library.
The documentation should be updated to describe the ExternalLibraries
method, and the old method description should be moved to an appendix with
a clear warning that this is deprecated.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/219>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#481: Tests should be converted to use new symmetry thorns
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
It was decided
(http://cactuscode.org/pipermail/developers/2010-September/006087.html)
that the built-in CartGrid3D symmetries are deprecated and will not work
with the Mercurial version of Carpet. Any test cases that use
Grid::domain != "full" should be modified to use ReflectionSymmetry
instead.
In general, this should be possible without regenerating the test output.
However, for the case of AHFinderDirect, the horizon finder actually uses
a different internal multipatch grid structure if it detects that a
CartGrid3D symmetry is being used. This means that the horizon shapes and
quantities are different at the level of numerical error with
ReflectionSymmetry. I propose to convert the tests to use
ReflectionSymmetry and regenerate the test data (the grid function phi is
the same with the new symmetry thorn, it's only the horizons which are
different). The failing tests are related to checkpoint and recovery, and
are not designed to test the symmetry mechanism.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/481>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#395: Thorns providing interpolator routines should provide testcases for them
-------------------------+--------------------------------------------------
Reporter: knarf | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: ET_2011_11
Component: Other | Version:
Keywords: |
-------------------------+--------------------------------------------------
Errors in the interpolator often show up in the output of other thorns,
depending on those interpolating routines. Figuring out that this is
caused by problem while interpolating can take quite a bit of time, which
could be saved if the interpolating thorns would include testsuites
themselves.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/395>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit