#773: McLachlan dissipation should be disabled by default
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Other | Version:
Keywords: |
-------------------------+--------------------------------------------------
In the current version of McLachlan, the parameter apply_dissipation is
set to "always" by default. The corresponding "epsdiss" is set to 0 by
default. The dissipation calculation in McLachlan is expensive due to the
way that it iterates over variables. Use of the Dissipation thorn or
similar is usually much faster. I had not realised that apply_dissipation
was "always" by default. I think it should be "never".
OK to change? (with announcement to the mailing list)
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/773>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1130: Cactus tutorial on cactus website
------------------------------+---------------------------------------------
Reporter: jtao@… | Type: defect
Status: new | Priority: major
Milestone: | Component: Other
Version: | Keywords:
------------------------------+---------------------------------------------
Following the instructions on the Cactus website will not lead
to a successful run due to the introduction to ash. This frustrates
new Cactus users.
I would suggest to add
!BRANCH = Cactus_4.0.0
to the thorn list to make it work at least.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1130>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1128: Require C99 for Cactus C thorns
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
According to Erik, all systems that we need to support have good support
for C99. Many thorns use some features of C99, and it is a common error
to try to compile these without using the C99 options to a compiler. The
resulting error messages can be confusing.
In order to provide a common language platform for Cactus thorn writers,
we should state that Cactus expects the compiler to have C99 enabled. We
should test this during the configure stage and abort with a good error
message if it is not the case. Thorn writers can then assume the standard
features of C99 will always be available.
The automatically-configured compiler options in known_architectures
should be modified to enable C99 mode if it is not enabled by default for
all the recognised compilers.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1128>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#535: Add autoconf macro to test C99 style variable declarations
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
Many compilers don't support C99 style variable declarations in their
default settings. We should test this, add certain flags automatically if
we can, or abort with a clear error message otherwise.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/535>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1121: gcc 4.6+ compiler bug for isnan
---------------------+------------------------------------------------------
Reporter: sbrandt | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone: ET_2012_11
Component: Carpet | Version: development version
Keywords: |
---------------------+------------------------------------------------------
It seems that gcc 4.6 and up has a problem with compiling the isnan
function.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48891
I find that simply referring to the namespace explicitly solves it.
I had to make similar changes in Carpet/CarpetLib/src/defs.hh, but there I
had to fix isinf as well. Probably the isnormal, copysign, etc. functions
should get std:: for consistency.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1121>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#632: Changegroup hook failed when pushing to Carpet repository
--------------------+-------------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
When I push to the Carpet repository, I get the following message:
{{{
remote: error: changegroup.cia hook failed: http://cia.vc returned an
error: queued.
}}}
The push succeeds. What is the cause of this error?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/632>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#412: Split Appendices
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
Currently, the appendices of the users' guide are repeated into the
reference manual. This is somewhat confusing, and causes problems because
the appendices cannot easily reference other sections (e.g. "see page 15"
doesn't make sense since one doesn't know in which document this will be
read). I suggest to split the appendices and have some of them in the
users' guide while moving others into the reference manual, so that each
appendix is included in only one document
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/412>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#982: Abort with an error if the argument of --root= is not a directory
-----------------------------+----------------------------------------------
Reporter: anonymous | Owner: eric9
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: GetComponents | Version: development version
Keywords: error detection |
-----------------------------+----------------------------------------------
Currently, when GetComponnents is invoked as
GetComponents --root=<dir>
and <dir> does not exist, Getcomponents just ignores the option. I would
be better if GetComponents aborted with an error if the argument of
--root= is not a valid directory.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/982>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit