#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
#1263: Multipole does not handle variable names correctly
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: Multipole |
-----------------------------------+----------------------------------------
When you specify variables for Multipole to decompose, you have the option
of giving it a "name" for the variable to be used in the output filename.
This is useful if you are decomposing Psi4r, with imaginary part Psi4i,
and want the file to just be named "Psi4". If you don't specify a name,
it is supposed to use the original variable name. However, at the moment,
this last part seems to be broken.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1263>
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
#1523: Use Piraha to Parse all CCL files
-------------------------+--------------------------------------------------
Reporter: sbrandt | Owner:
Type: enhancement | Status: new
Priority: optional | Milestone: Cactus_4.3.0
Component: Cactus | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
Piraha should be used to parse all the CCL files. This would give us a
well-defined grammar and the ability to let other tools use the CCL files
in a reliable way.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1523>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1658: ExternalLibraries/pciutils does not compile on Mac OS
--------------------+-------------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version: development version
Keywords: |
--------------------+-------------------------------------------------------
When I try to compile ExternalLibraries/pciutils on Mac OS, I get
{{{
lspci.c:919:29: error: expected ')'
puts("lspci version " PCIUTILS_VERSION);
^
./pciutils.h:18:26: note: expanded from macro 'PCIUTILS_VERSION'
#define PCIUTILS_VERSION PCILIB_VERSION
^
lspci.c:919:11: note: to match this '('
puts("lspci version " PCIUTILS_VERSION);
}}}
This is with the osx-mountain-lion-macports-gcc.cfg optionlist, and "gcc-
mp-4.6 (MacPorts gcc46 4.6.4_3) 4.6.4".
I have to disable this thorn in my thornlist (or machine definition file)
to compile the ET. This means that the ET will not compile out of the box
on Mac OS.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1658>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit