#1698: The ET tickets should be tidied up
----------------------------------+-----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit trac | Version: development version
Keywords: |
----------------------------------+-----------------------------------------
Many of the ET tickets have not seen much attention recently or at all.
We should have a session where we run though all the tickets and make sure
that their priorities/state etc are correct. Once we have done this, we
should come up with a strategy for keeping the tickets under control. In
the process, we should decide what is meant by the different ticket
priorities, and whether we need to add additional priorities or states to
allow us to more effectively manage the tickets.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1698>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#719: Mailing lists could have a link to the archived version of the message
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version:
Keywords: |
-------------------------+--------------------------------------------------
It would be useful for the footer of a mailing list posting to contain a
URL to the archived version of the message so that it is easy to point
people to the message in an email. This would apply to both the Cactus
and the ET lists.
It appears that this is not straightforward in MailMan 2, but is expected
in version 3: http://mail.python.org/pipermail/mailman-
users/2011-October/072378.html.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/719>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1471: Cactus should auto-detect newer versions of GCC from MacPorts
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
Currently, during Cactus configuration without an optionlist on Mac OS, I
get
{{{
checking for gcc-mp-4.4... no
checking for gcc-mp-4.3... no
checking for gcc-mp-4.2... no
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
}}}
I have gcc-mp-4.6, and 4.7 and 4.8 are also available in macports. The
configure script should be updated to detect these versions.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1471>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1170: ExtrenalLibraries handle XXX_DIR XXX_INC_DIRS and XXX_LIB_DIRS
incosistently
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: ExternalLibraries |
-----------------------------------+----------------------------------------
This is a companion ticket to #1006.
Different thorns (eg. MPI and HDF5 and LAPACK) handle XXX_DIR and
XXX_INC_DIRS etc differently. MPI for example sets the include path to
$MPI_DIR/include if MPI_INC_DIRS is not explicitly set and to MPI_INC_DIRS
if it is set. HDF5 has no HDF5_INC_DIRS option and always sets the include
path to HDF5_DIR/include. LAPACK has not INC_DIRS option and sets the
linker path to LAPACK_DIR while the other two thorns set it to XXX_DIR/lib
(unless overridden by MPI_LIB_DIRS in the case of MPI).
I would be good to present a uniform set of option for all these thorns.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1170>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1769: External libraries: moving towards multiarch library directory structure
----------------------------------------------+-----------------------------
Reporter: bmundim | Owner:
Type: defect | Status: new
Priority: major | Milestone: ET_2015_05
Component: EinsteinToolkit thorn | Version: development version
Keywords: ExternalLibraries HDF5 Multiarch |
----------------------------------------------+-----------------------------
Several Linux distributions have already started to move their libraries
to a new directory structure that reflects the target architecture and
allows the installation of packages from multiple architectures in the
same system. The following links provide more details of this change:
{{{
https://wiki.debian.org/Multiarch/TheCaseForMultiarchhttps://wiki.ubuntu.com/MultiarchSpec
}}}
This change potentially affects several of external library scripts
shipped with ET. For example the HDF5/src/detect.sh script is not able to
detect the hdf5 libraries installed in the directory /usr/lib/x86_64
-linux-gnu for Ubuntu 14.04.2 LTS.
I have attached a simple patch to remedy this issue and open a discussion
on the best way to proceed here. This patch does depend on the
availability of gcc on the system. It currently works fine for me, but we
might need a better solution for systems without gcc.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1769>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1474: compile ExternalLibraries with other thorns rather than when CST runs
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
Compiling external libraries takes a long time by now. Currently this
happens very early in the compilation phase, before the other thorns are
compiled.
It would be better if the compilation happened at the same time as that of
other thorns.
This will entail splitting the configuration ie. detecting whether to
build the included source or use a system wide copy from the compilation,
most likely either using Cactus makefile variables or temporary files to
transfer the decisions from the configuration stage to the build stage.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1474>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1946: sim setup should create a section for the current machine
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
When calling sim setup on a machine in the machine data base (eg
bluewaters in my case) it it still creates only a {{{[default]}}} section
in defs.local.ini which means that the account information and possibly
non-default sourcebasedir are not used for bluewaters leading to hard to
understand error messages later on.
I would thus like to suggest to change sim setup such that instead (or in
addition to) a "[default]" section it creates a section for the detected
machine if it already knows this machine.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1946>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2050: cctk_startupxxx is a valid group
---------------------+------------------------------------------------------
Reporter: sbrandt | Owner: sbrandt
Type: defect | Status: new
Priority: unset | Milestone:
Component: Other | Version: development version
Keywords: |
---------------------+------------------------------------------------------
Currently, the "at" keyword in the schedule.ccl file is supposed to report
an error if one is scheduling in a group that is not present at startup.
It detects this with a regexp, but the regexp does not include boundaries.
As such cctk_startupxxx is considered valid.
In addition, the new parser is failing to report a CST error for this
violation regardless of group name.
The attached patch to the schedule parser fixes both defects.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2050>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2077: include RNSID in ET
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: Hydro_RNSID |
-----------------------------------+----------------------------------------
Pull request is here:
https://bitbucket.org/einsteintoolkit/einsteininitialdata/pull-requests/3
/new-initial-data-thorn-for-grhydro/diff
It generate ID for rotating star either with uniform rotational
profile or describe by differentialy rotating j-law.
testsuite par file provided and tested
example of usage parfile in par subdirectory as perl script that
generate par file with resolution dx=0.75 suited for workstation tests.
Hydro_RNSID/par/speed.rpar generate par file usefull to peform
speed test
two stand alone utility are generate at compile time to [RNS]
generate initial models (to be imported in Cactus) amd to read [RNS_read]
the generated initial model
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2077>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit