#1158: ExternalLibraries/HDF5 should change the defaults for HDF5_ENABLE_CXX and
HDF5_ENABLE_FORTRAN to "no".
-----------------------------------+----------------------------------------
Reporter: knarf | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
ExternalLibraries/HDF5 should change the defaults for HDF5_ENABLE_CXX and
HDF5_ENABLE_FORTRAN to "no". Nothing within the toolkit or Cactus still
uses these interfaces and system wide installed libraries might not come
with it, leading to link failures.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1158>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1388: New thorn MemSpeed
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
I have written a thorn MemSpeed, available at
<https://svn.einsteintoolkit.org/incoming/MemSpeed>. This thorn is useful
for performance tuning. I propose to add it to CactusUtils.
From the README:
Determine the speed of the CPU, as well as latencies and bandwidths of
caches and main memory. These provides ideal, but real-world values
against which the performance of other routines can be compared.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1388>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1517: Make Simfactory tell you what it's doing
-------------------------+--------------------------------------------------
Reporter: sbrandt | Owner: eschnett
Type: enhancement | Status: new
Priority: optional | Milestone: Cactus_4.3.0
Component: SimFactory | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
Sometimes I'd like to know what shell commands Simfactory is running. This
patch causes Simfactory to print out messages of the form "COMMAND: ...."
when the --verbose flag is set.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1517>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1483: speed up reading metadata of HDF5 files in visit
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version: development version
Keywords: CarpetHDF5 |
-------------------------+--------------------------------------------------
The attached patch tries to extract as much information about a dataset
from the dataset name as possible. Since accessing attributes is slow but
the dataset name comes for free this speeds up opening HDF5 files in VisIt
drastically (I had a factor of 6 when I measured it quite a while ago).
This is certainly not the nicest way of parsing the string, one could
think of sequentially looking for "name=value" constructs in the string
and acting based on the name rather than just matching against all
possible options.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1483>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#499: Prolongation fails with vectorisation enabled
--------------------+-------------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
The development version of Carpet uses vectorisation to speed-up
prolongation. This fails with various errors, including corruption of the
malloc heap.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/499>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#445: Make Carpet timers hierarchical
-------------------------+--------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Carpet | Version:
Keywords: |
-------------------------+--------------------------------------------------
With the current flat structure of timers in Carpet, it is difficult to
identify which timers are contained in which other timers, and hence to
avoid double-counting when adding up the times.
This series of patches modifies the timer infrastructure in Carpet to
generate a tree of timers where the hierarchy reflects the call-graph of
the program. This makes it much easier to interpret the timer output than
with the previous flat structure, where it was not possible to see which
timers "contained" which others. More implementation details are given at
the top of TimerNode.hh.
Note that the Timer source and header files have been renamed as
CactusTimer and a new Timer file and object has been created. This is
because the Timer object now only provides a wrapper around the Cactus
timer mechanism which was contained in the old Timer object.
New parameters output_initialise_timer_tree and output_timer_tree_every
control output of a new "timer tree diagram" to standard output for the
Initialise and Evolve timer trees respectively. These diagrams indicate:
1. the value of each timer;
2. the percentage of the given tree taken by each timer;
3. which timers are contained in which other timers;
4. any untimed code
for any timer which takes more than 1% of the tree time.
Making the timers hierarchical means that the ad-hoc methods used before
to identify the hierarchy (such as naming the timer Evolve::Sync, for
example, to indicate that the Sync timer was a child of the Evolve timer)
are no longer necessary and have been removed. Additionally, the
construction of timers in a "dynamic" manner is now handled automatically
for all timers, so special-case code is no longer needed and has been
removed.
Additionally some previously-untimed parts of the code are now timed, and
timer names have been made more consistent in some places.
There is code in the patches to output the entire timer tree as an XML
file, but it is not enabled.
Ideally the timer tree printed to standard output would contain reductions
across processes, but at the moment it contains only the timer from the
current process.
The attached "tree-example.txt" file shows an example of the timer tree
that is printed for a simulation using the qc0-mclachlan parameter file
from the Einstein Toolkit.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/445>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1409: cleanup Avec in HydroBase
-----------------------------------+----------------------------------------
Reporter: knarf | Owner:
Type: task | Status: new
Priority: major | Milestone: ET_2013_11
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
As discussed at the dev-workshop in summer 2013, Avec shouldn't be defined
in HydroBase, but move to the evolution thorn. In particular, the current
dev-version of HydroBase contains (will in a few hours) contain two
different versions of it, depending on where it is defined.
The needs to be cleaned up before the next release.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1409>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1210: CarpetIOASCII should not write column names info each iteration
--------------------+-------------------------------------------------------
Reporter: knarf | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
Currently, CarpetIOASCII writes the column names header each iteration,
leading to bloated output - easily double the size of what should suffice.
Once after file creation would be much better.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1210>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1399: add evolution method "stationary" to ADMBase
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: ADMBase |
-----------------------------------+----------------------------------------
This method is similar to "static" in that it can be used for Cowling
runs, it differs from "static" in that it schedules the initial data
routine after any grid changes and does not apply boundary conditions or
SYNC calls. It can thus be used if one can compute the required
metric/shift/lapse easily in a pointwise manner and would like to have
exact (non-prolongated) data in the buffer zones.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1399>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1302: Reduce time spent in deciding not to do output.
--------------------------------------+-------------------------------------
Reporter: diener | Owner: eschnett
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Carpet | Version: development version
Keywords: performance optimization |
--------------------------------------+-------------------------------------
I noticed, during some scaling tests, that for my code a significant
amount of time was spent by CarpetIOASCII, even though I only had it
activated and didn't actually request any output. The reason is that in
order to figure out whether to do output or not, there is a loop over all
grid variables and a routine (TimeToOutput) is called. In this
routine there is a check if the out_dir and out_vars parameters have been
steered and if so update some internal data structures. It should be
sufficient to do this before entering the loop over grid variables. The
same issue is present in CarpetIOScalar and CarpetIOHDF5. The attached
patches for CarpetIOASCII, CarpetIOScalar and CarpetIOHDF5 moves this
check outside of the loop over grid variables and in addition bypasses the
loop completely if the out_vars parameter string is the empty string. Note
that the code where I noticed this problem uses large vectors of 1D grid
arrays, and it turns out that Cactus counts each vector element as a
distinct grid variables and the length of the loop over grid variables in
my case was close to 100.000, which might explain why nobody has noticed
this before.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1302>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit