#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
#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
#895: PITTNullCode does not work with Devel AEILocalInterp
---------------------------------+------------------------------------------
Reporter: yosef@… | Type: defect
Status: new | Priority: major
Milestone: | Component: EinsteinToolkit thorn
Version: | Keywords: CCE complex interpolation
---------------------------------+------------------------------------------
The CCE testsuite fails in the development version of ET.
The interpolation calls in NullNews fail with the error
WARNING[L1,P0] (AEILocalInterp):
CCTK_InterpLocalUniform(): input datatype 111 not supported!
(0-origin) input #in=0
The interpolation call is for a variable of type CCTK_VARIABLE_COMPLEX.
The call works with the Maxwell version of AEILocalInterp
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/895>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#745: the flesh allows two implemantion of the same interface to have different
default values for restricted parameters
--------------------+-------------------------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
--------------------+-------------------------------------------------------
since the flesh creates paramters for all compiled in (rather than
activated) thorns initially, this affects the default value that a thorn
sees. Thorns seem to be initialized (and thus their parameter structures
being created) in alphabetical order, which means that the thorn
alphabetically '''last''' (How, I have no idea, the parameter handling
logic seems a bit of a mess) will determine the default parameter value.
Attached is a parameter file to demonstrate this with Carpet and PUGH who
both declare parameters periodic and periodic_[xyz] but differ in their
defaults.
To demonstrate, create an executable with only Carpet compiled in and run
the parameter file. Then look at the paramters in the checkpoint it
creates eg.
{{{
h5dump -r -d /Parameters\ and\ Global\ Attributes/All\ Parameters
output/checkpoint.chkpt.it_0.h5 | grep periodic
}}}
Do the same with an executable that contains both PUGH and Carpet. Notice
that parameter values are now PUGH's defaults.
This can actually cause a runs to abort when recovering from a checkpoint
when one switches from an executable with PUGH compiled in to one that
does not. (Beyond the fact that some thorn might actually use it's
parameters rather than the Carpet/PUGH pair where happily Carpet ignores
these parameters and PUGH who actually used them gets to set the default).
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/745>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#669: Rewrite users of deprecated HDF5 C++ API
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: Other | Version:
Keywords: |
----------------------+-----------------------------------------------------
The C++ API for HDF5 is decprecated. We should examine which code uses it,
and rewrite it to use the C API instead. This would allow us to use more
system-provided HDF5 installations.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/669>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#788: Produce movie about history of Einstein Toolkit
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: task | Status: new
Priority: optional | Milestone:
Component: Other | Version:
Keywords: |
----------------------+-----------------------------------------------------
Do this <https://www.youtube.com/watch?v=ZEAlhVOZ8qQ> for the Einstein
Toolkit.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/788>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#934: Cannot check out ET release
---------------------------+------------------------------------------------
Reporter: eschnett | Owner: eric9
Type: defect | Status: new
Priority: blocker | Milestone:
Component: GetComponents | Version:
Keywords: |
---------------------------+------------------------------------------------
When I try to check out the release branch of the ET, GetComponents fails
for all git repositories, and only for these. It appears that these
repositories are checked out, but are on their master branch, and
GetComponents cannot switch to the release branch. These repositories are
then renamed, e.g. to "CRL.branch.failed".
The error messages (taken from crl.log) are:
{{{
May 29 11:05:08 2012: Could not checkout EinsteinExact/doc, unable to
switch to branch ET_2012_05. Any existing symlinks to EinsteinExact/doc
will be broken
May 29 11:08:05 2012: Could not checkout KrancNumericalTools/GenericFD,
unable to switch to branch ET_2012_05. Any existing symlinks to
KrancNumericalTools/GenericFD will be broken
May 29 11:08:11 2012: Could not checkout McLachlan/doc, unable to switch
to branch ET_2012_05. Any existing symlinks to McLachlan/doc will be
broken
May 29 11:09:47 2012: Could not checkout GetComponents, unable to switch
to branch ET_2012_05. Any existing symlinks to GetComponents will be
broken
May 29 11:09:47 2012: 4 errors occurred during update from thornlist(s):
http://svn.einsteintoolkit.org/manifest/branches/ET_2012_05/einsteintoolkit…
}}}
This is on Mac OSX. I am using git version 1.7.10.2. I obtain
GetComponents via
{{{
wget --no-check-certificate
https://github.com/gridaphobe/CRL/raw/ET_2012_05/GetComponents
}}}
and run it as
{{{
./GetComponents -a
http://svn.einsteintoolkit.org/manifest/branches/ET_2012_05/einsteintoolkit…
}}}
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/934>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#531: Problem with adding/removing configuration.ccl files
----------------------+-----------------------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
----------------------+-----------------------------------------------------
Cactus doesn't handle well adding or removing configuration.ccl files.
When a new configuration.ccl file is added, Cactus ignores it until the
next "rebuild" (i.e. until another ccl file changes, until the thorn list
changes, or until the user calls *-rebuild explicitly). When a
configuration.ccl file is removed, make aborts with an error message, and
a rebuild is forced.
One way to remedy this would be to have (empty) configuration.ccl file in
all thorns. After all, param.ccl and schedule.ccl files also need to be
present even if they are empty. This would also remove a bit of complex
logic from the Cactus make system.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/531>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#628: Configuring on Kraken leads to warnings
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
Using current simfactory to build on Kraken leads to the following warning
during configuration:
{{{
This is probably a Cray XT4 series system.
Using known-architectures xt4-cray-linux
This is an Cray XT4: you always need MPI!
Forcing MPI to NATIVE.
Unknown Linux f90 compiler.
Please add appropriate information to
/nics/d/home/hinder/Cactus/EinsteinToolkit/lib/make/known-
architectures/linux
and send the updated file to CactusMaint
We will try anyway ...
}}}
Cactus should learn about this system.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/628>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit