#331: SimFactory does not abort if it has been given a nonexistent optionlist
------------------------+---------------------------------------------------
Reporter: hinder | Owner: mthomas
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
If I specify a nonexistent optionlist in a machine's .ini file, I get the
warning
Info: optionlist is: None
Warning: no option list specified, using blank option list
This is incorrect. I have specified an optionlist, but it has not been
found, which indicates an error. In this case I would expect a fatal
error.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/331>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#228: Make it easier for users to create accounts on TRAC
----------------------------------+-----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit trac | Version:
Keywords: |
----------------------------------+-----------------------------------------
Currently, in order to interact fully with TRAC, it is necessary to have a
CCT account. I would prefer that all potential users of the ET/Cactus
TRAC could create accounts. This way, it would be possible for all bug
reporters to be notified of changes to the tickets they create, and makes
it more likely that they will respond to requests for further information
and confirmations of fixes.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/228>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#270: Need web instructions for building on a new machine
-------------------------------------+--------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version:
Keywords: |
-------------------------------------+--------------------------------------
We should have instructions on the web that explain how to build the
Einstein Toolkit on a new machine, i.e. a machine for which we don't have
a SimFactory entry already. This seems to be a fairly common case for new
users, who rather want to build on their own machine instead of on Queen
Bee.
This should probably concentrate on configuring Cactus first, i.e. on
configuring SimFactory for building a configuration. Job submission etc.
should come later.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/270>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1201: Incorrect dtshift in Exact with shift_add_{x,y,z} parameters
-----------------------------------+----------------------------------------
Reporter: barry.wardell | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
The Exact thorn has shift_add_{x,y,z} parameters for adding a constant to
the shift. Considering these as a coordinate transformation using a vector
v^i = [shift_add_x, shift_add_y, shift_add_z], such a transformation
should affect both the shift and its time derivative. This is because the
time derivative in the new coordinates differs from the time derivative in
the old coordinates by a term v^j d(beta^i)/dx^j. This is correctly
implemented as a 4D coordinate transformation in the EinsteinExact thorns
and I have verified that the difference relative to the Exact thorn is
given by this missing term.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1201>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1097: Describe Tmunu in GRHydro
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
Describe in GRHydro's documentation how Tmunu is defined
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1097>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#660: Make MHD multipatch-aware
-----------------------------------+----------------------------------------
Reporter: tbode | Owner: tbode
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
At least the Con2PrimM routines need to be multipatch-aware.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/660>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#502: SimFactory user-guide should be available and updated automatically
-------------------------+--------------------------------------------------
Reporter: hinder | Owner: knarf
Type: enhancement | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
-------------------------+--------------------------------------------------
SimFactory has an incomplete user guide in the doc/userguide directory.
This is developed using Sphinx, which is a Python framework for writing
documentation. You need to install sphinx to generate this documentation.
This can be done using something similar to the following:
export PYTHONPATH=/home/ianhin/software/python
export PATH=/home/ianhin/software/python/:$PATH
hash -r
easy_install --install-dir ~/software/python sphinx
Then go into the simfactory/doc/userguide directory and type:
./autogen
make html
to generate HTML documentation (type just "make" to see the other possible
targets like PDF etc).
This should be regenerated on any commit to the SimFactory/doc/userguide
directory and copied to a web-accessible location for inclusion on
simfactory.org.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/502>
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
#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