#350: Autogenerating cctk_Loop.h
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
I wrote a perl script to auto-generate the Cactus header file
Cactus/src/include/cctk_Loop.h.The script writes the code to stdout. I
attach it to this ticket, as well as the output it generates.
I suggest to keep this perl script next to its output in the include
directory, and to run it manually whenever required.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/350>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#215: Driscoll&Healy integration for Multipole
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: |
-------------------------+--------------------------------------------------
The attached patch implements a more accurate integration over the sphere,
using an algorithm by Driscoll & Healy. This algorithm uses Gaussian
integration weights, leading (almost) to exponential convergence.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/215>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#429: Parallelising AEILocalInterp
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
The enclosed patch parallelises AEILocalInterp via OpenMP.
This leads to a slight change in behaviour. Currently, AEILocalInterp
traverses the list of points sequentially, and aborts when the first error
is encountered. After parallelisation, there is no fixed order in which
the points are traversed, and if several errors are encountered, any one
of the errors may be returned, not necessarily the first. I am not aware
of any thorn that would or should rely on such an ordering.
This patch also adds "restrict" and "const" statements that may improve
performance as it gives the compiler more information about dependencies
between pointers.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/429>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#262: make error messages in ReflectionSymmetry more informative
--------------------------------------------+-------------------------------
Reporter: roland.haas@… | Type: enhancement
Status: new | Priority: minor
Milestone: | Component: Cactus
Version: | Keywords:
--------------------------------------------+-------------------------------
this small patch includes the value of ierr in ReflectionSymmetries error
messages
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/262>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#339: ExternalLibraries/OpenSSL does not compile in 64-bit mode on Mac OS
---------------------------------------+------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version:
Keywords: ExternalLibraries/OpenSSL |
---------------------------------------+------------------------------------
Compiling OpenSSL using ExternalLibraries leads to the following warning,
followed by a build failure:
+ cd openssl-1.0.0d
+ ./config
--prefix=/Users/ian/Cactus/et/configs/fink/scratch/external/OpenSSL
Operating system: i686-apple-darwinDarwin Kernel Version 10.6.0: Wed Nov
10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386
WARNING! If you wish to build 64-bit library, then you have to
invoke './Configure darwin64-x86_64-cc' *manually*.
You have about 5 seconds to press Ctrl-C to abort.
Configuring for darwin-i386-cc
I don't know how to detect that the compiler is building in 64-bit mode in
order to add the corresponding flag to the Configure line.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/339>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#430: Convert all parameter files, examples, and test cases to EOS_Omni
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
Now that EOS_Omni is standard, we should convert all parameter files.
At the moment, these parameter files still reference EOS_Base:
EinsteinInitialData/TOVSolver/test/test_one_boost_max/test_one_boost_max.par
EinsteinInitialData/TOVSolver/test/test_one_static_max/test_one_static_max.par
EinsteinInitialData/TOVSolver/test/test_tov_carpet/test_tov_carpet.par
EinsteinInitialData/TOVSolver/test/test_two_av/test_two_av.par
EinsteinInitialData/TOVSolver/test/test_two_max/test_two_max.par
LSUDevelopment/Refluxing/par/GRHydro_Carpet_Shocktube_base_works_with_gitCarpet.par
The Refluxing parameter file is for reference only and should be remove
now that hg Carpet is the default.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/430>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#358: FAQ entry
----------------------------+-----------------------------------------------
Reporter: knarf | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus website | Version:
Keywords: |
----------------------------+-----------------------------------------------
For a new FAQ:
Q: I get errors like "/usr/include/H5Dpublic.h:145: error: too many
arguments to function ‘hid_t H5Dopen1(hid_t, const char*)’"
A: The HDF5 library you use is either version 1.6 or defaults to it. If it
is version 1.6.x, update to 1.8.x. If it is 1.8.x and it defaults to the
1.6 API version, you might be out of luck, especially on Debian Squeeze
systems, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537414. What
you can then do is to remove (comment) out the macro H5_USE_16_API_DEFAULT
in /usr/include/H5pubconf.h. This isn't pretty, but is really a bug in the
package and has to be fixed there. There is no way to switch to the new
API on those systems, other than specifying the API version of each symbol
separately, which would be even messier.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/358>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#221: Simfactory should complain about unused arguments
------------------------+---------------------------------------------------
Reporter: eschnett | Owner: mthomas
Type: defect | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
------------------------+---------------------------------------------------
When more arguments are given to simfactory that it uses, it should
complain with an error message.
For example, "sim stop sim1 sim2" stops simulation sim1 and ignores the
argument sim2. Instead, it should output an error message if the argument
sim2 is ignored.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/221>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#120: Improve built-in help system
-------------------------+--------------------------------------------------
Reporter: hinder | Owner: mthomas
Type: enhancement | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
-------------------------+--------------------------------------------------
SimFactory currently provides a single help screen when you type "sim
help". I would like to be able to do "sim help <command>" and get help
which is relevant for that command. This help should say briefly what the
command does, and give a comprehensive list of the options specific to
that command. The top-level "sim help" command should then give a list of
the commands, and a list of the simfactory options which apply to all
commands. This first help page should be kept as brief as possible so
that it is easy to see at a glance what commands are available. The most
common commands should be listed first, and maybe separated from the less
common commands.
I think this is important as it is the first port-of-call when someone
wants to know how to use a particular feature, especially when the syntax
is similar but not quite the same as in SimFactory 1.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/120>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit