#1976: CarpetIOHDF5: add option to have one output file per process
-------------------------+--------------------------------------------------
Reporter: rhaas | Owner: eschnett
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Carpet | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
This is useful when running on systems where many files slow down file
access (ie lustre file systems) and where there are many hdf5 output files
per MPI rank.
The code combines all output into a file $parfile.h5 which is currently
hard-coded.
https://bitbucket.org/eschnett/carpet/pull-requests/14/carpetiohdf5-add-
option-to-have-one-output/diff
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1976>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1996: Formaline can deadlock
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: critical | Milestone: ET_2016_11
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
I found that Formaline recently started to deadlock when creating git
repositories. The problem was that {{{cat}}} was called without arguments.
This patch corrects the problem:
Change line 382 from
{{{
cat $(filter-out '$(TARBALL_DIR)/config-Cactus.files', $?)
&& \
}}}
to
{{{
cat /dev/null $(filter-out '$(TARBALL_DIR)/config-
Cactus.files', $?) && \
}}}
i.e. add a {{{/dev/null}}} there.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1996>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1998: Typo on ET website
--------------------------------------+-------------------------------------
Reporter: figura.antonio@… | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit website | Version: development version
Keywords: |
--------------------------------------+-------------------------------------
The last paragraph in https://einsteintoolkit.org/ reports that the
fourteenth release of the Einstein Toolkit has been issued on June 2016,
instead of November 2016.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1998>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1959: Rename Root Directory "EinsteinToolkit"
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner:
Type: enhancement | Status: new
Priority: unset | Milestone:
Component: Other | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
Upon downloading a fresh ET, I was reminded once again that there remain
some vestiges of the past: the root directory is still named "Cactus".
Although most of the code within the ET currently depends on the Cactus
infrastructure, I think we should have a mindset more inclusive to other
infrastructures moving forward. There is no "one size fits all" in NR,
after all.
To this end, I propose to rename the root directory "EinsteinToolkit".
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1959>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#394: Testsuite log file should contain more information
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: testsuites |
-------------------------+--------------------------------------------------
It is useful to look at the testsuite log file for information about how
the tests were run. For example, which compiler was used, and with what
compiler options. We need to balance this against providing information
which will always change, making diffs hard to read.
The most extreme case would be to output all make variables. Maybe better
would be to output CC, CFLAGS, CXX, etc. Another option would be to parse
these and say "intel compiler", "gcc", "pgi" etc.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/394>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1991: IllinoisGRMHD's magnetizedTOV.par test uses too much memory
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: IllinoisGRMHD |
-----------------------------------+----------------------------------------
It requests ~1GB of memory which is too much for a test case I think.
Simple changes to reduce memory consumption is setting
{{{
CoordBase::dx = 1.5
CoordBase::dy = 1.5
CoordBase::dz = 1.5
CarpetRegrid2::num_levels_1 = 2
}}}
down from
{{{
CoordBase::dx = 1.0
CoordBase::dy = 1.0
CoordBase::dz = 1.0
CarpetRegrid2::num_levels_1 = 4
}}}
which should bring memory consumption down to ~150MB which is much better
eg on the Jenkins test slaves.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1991>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1981: Configuration files for MARCONI.
-------------------------+--------------------------------------------------
Reporter: bentivegna | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
I have made the simfactory configuration files for the Marconi system:
http://www.hpc.cineca.it/hardware/marconi
available via this pull request:
https://bitbucket.org/simfactory/simfactory2/pull-requests/13
/configuration-files-for-cinecas-marconi/diff
Any comment or contribution is welcome.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1981>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1970: perl >= 5.26 dropping "." from @INC
----------------------+-----------------------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version: development version
Keywords: backport |
----------------------+-----------------------------------------------------
New version of perl will no longer include "." from {{{@INC}}} by default.
This causes out perl code that uses "require 'lib/sbin/XXX.pl'" to fail.
Since this will affect the release version a patch needs to be backported.
See https://lists.debian.org/debian-devel-announce/2016/08/msg00013.html
Note that this is not Debian specific but affects all Perl packages.
I will prepare a patch.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1970>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1967: qc0_mclachlan.par example in 2016_05 produces outdated parameter warnings
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
Running qc0_mclachlan.par from the par directory of a 2016_05 checkout I
get:
{{{
WARNING level 1 from host 127.0.0.1 process 0
while executing schedule bin CCTK_PARAMCHECK, routine
ML_BSSN_Helper::ML_BSSN_ParamCheck
in thorn ML_BSSN_Helper, file
configs/sim/build/ML_BSSN_Helper/Parameters.c:157:
-> Parameter ML_BSSN::my_initial_boundary_condition is outdated; please
update the parameter file. Do not use this parameter, and set up initial
boundary conditions as usual.
}}}
Since qc0_machlan.par is a typical "beginner's file" and our tutorial
mentions it, we should update so that it does not produce warnings when
run anymore. We should also I believe update the paramwarn message to be
more helpful since likely the user did not know what the "usual way to set
up initial boundary conditions" is, otherwise they'd have done so :-).
Major as this should be be fixed for the next release.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1967>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1717: hwloc: lnuma & lltdl *really* required?
-----------------------------------+----------------------------------------
Reporter: zachetie@… | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
I downloaded the ET devel version (ca. Nov 26) on my (ubuntu) laptop and
compiled it, using gcc.
I compiled to the linker stage, and the linker complained:
ld: cannot find -lnuma
ld: cannot find -lltdl
I found references to these libraries in:
configs/[buildname]/bindings/Configuration/Capabilities/make.HWLOC.defn
After removing these references, the code compiled and seemed (on the
surface) to run okay. Are these libraries really necessary?
I ask because every time I need to install ET on a new machine, it would
be more convenient if the step "apt-get install libnuma-dev libltdl-dev"
were left out, particularly since reliable Internet access may not exist
at that time.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1717>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit