#380: AHFinderDirect failure with qc0-mclachlan.par
--------------------+-------------------------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone: ET_2011_05
Component: Other | Version:
Keywords: |
--------------------+-------------------------------------------------------
Trying to run the par/qc0-mclachlan.par in the ET trunk gives the
following error:
INFO (AHFinderDirect): proc 0: searching for horizons 1,5/6
WARNING level 0 in thorn CarpetInterp processor 0 host kop193.datura.admin
(line 1683 of
/home/ianhin/Cactus/etrelease/arrangements/Carpet/CarpetInterp/src/interp.cc):
-> Grid function "AHFINDERDIRECT::ahmask" has only 1 active time levels
on refinement level 1; this is not en
ough for time interpolation
See also #373, which might be related.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/380>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#488: Reduce space taken by Formaline tarballs
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version:
Keywords: Formaline |
-------------------------+--------------------------------------------------
When syncing lightweight data of simulations from a cluster, much of the
time and disk space on the local system is taken with Formaline tarballs.
It would be good to reduce this.
I propose opportunistically replacing the generated tarballs with hard-
links to existing tarballs on the same filesystem after Formaline has
written them to the new output directory if the files compare equal.
These could be from previous restarts of the same simulation when using
simfactory. Then, if an entire simulation is rsynced with the appropriate
options, hard-links will be transferred as hard-links, and the overall
transfer time and disk space used will be significantly reduced.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/488>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#177: EXC_BAD_ACCESS in CarpetIOASCII
--------------------+-------------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version:
Keywords: |
--------------------+-------------------------------------------------------
I am trying to run a minimal parameter file for testing purposes
(attached). Cactus gets as far as printing the iteration 0 info line and
then appears to hang. When I run in a debugger, it reports:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0x0000000000000000
0x0000000100b858b7 in CarpetIOASCII::WriteASCII<0> (os=@0x7fff5fbfc5e0,
gfdatas={<std::_Vector_base<const gdata *, std::allocator<const gdata *>
>> = {_M_impl = {<allocator<const gdata *>> =
{<__gnu_cxx::new_allocator<const gdata *>> = {<No data fields>}, <No data
fields>}, _M_start = 0x109f0ea10, _M_finish = 0x109f0eab8,
_M_end_of_storage = 0x109f0eab8}}, <No data fields>},
gfext=@0x7fff5fbfc960, vi=0, time=0, org=@0x7fff5fbfcafc,
dirs=@0x7fff5fbfd150, rl=0, ml=0, m=0, c=0, tl=0, coord_time=0,
coord_lower=@0x7fff5fbfc9d8, coord_upper=@0x7fff5fbfc9f0) at
ioascii.cc:1378
1378 switch (vartype) {
(gdb) bt
#0 0x0000000100b858b7 in CarpetIOASCII::WriteASCII<0>
(os=@0x7fff5fbfc5e0, gfdatas={<std::_Vector_base<const gdata *,
std::allocator<const gdata *> >> = {_M_impl = {<allocator<const gdata *>>
= {<__gnu_cxx::new_allocator<const gdata *>> = {<No data fields>}, <No
data fields>}, _M_start = 0x109f0ea10, _M_finish = 0x109f0eab8,
_M_end_of_storage = 0x109f0eab8}}, <No data fields>},
gfext=@0x7fff5fbfc960, vi=0, time=0, org=@0x7fff5fbfcafc,
dirs=@0x7fff5fbfd150, rl=0, ml=0, m=0, c=0, tl=0, coord_time=0,
coord_lower=@0x7fff5fbfc9d8, coord_upper=@0x7fff5fbfc9f0) at
ioascii.cc:1378
#1 0x0000000100b5b7ee in CarpetIOASCII::IOASCII<0>::OutputDirection
(cctkGH=0x109f073f0, vindex=0, alias={_M_dataplus = {<allocator<char>> =
{<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>},
_M_p = 0x10a06c1c8 "carpet::timing"}}, basefilename={_M_dataplus =
{<allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data
fields>}, <No data fields>}, _M_p = 0x10a06ba68
"minimal/carpet::timing"}}, dirs=@0x7fff5fbfd150, is_new_file=true,
truncate_file=true) at ioascii.cc:610
#2 0x0000000100b554c4 in CarpetIOASCII::IOASCII<0>::OutputVarAs
(cctkGH=0x109f073f0, varname=0x10a06c170 "CARPET::physical_time_per_hour",
alias=0x10a06be00 "carpet::timing") at ioascii.cc:480
#3 0x0000000100b57370 in CarpetIOASCII::IOASCII<0>::TriggerOutput
(cctkGH=0x109f073f0, vindex=0) at ioascii.cc:359
#4 0x0000000100b542b7 in CarpetIOASCII::IOASCII<0>::OutputGH
(cctkGH=0x109f073f0) at ioascii.cc:239
#5 0x000000010329a006 in Carpet::OutputGH (cctkGH=0x109f073f0) at
OutputGH.cc:55
#6 0x0000000103293b25 in Carpet::OutputGH (where=0x104c70f3c
"Initialise::CallAnalysis", cctkGH=0x109f073f0) at Initialise.cc:1382
#7 0x000000010328d432 in Carpet::CallAnalysis (cctkGH=0x109f073f0) at
Initialise.cc:530
#8 0x00000001032892d4 in Carpet::Initialise (fc=0x7fff5fbfe2b0) at
Initialise.cc:118
#9 0x000000010005806a in main (argc=4, argv=0x7fff5fbfe318) at
flesh.cc:80
I do not see how this line "switch(vartype)" where vartype is declared on
the stack, could lead to this error. This configuration has been rebuilt
with -O0 (Intel compiler) and debugging enabled.
This is with the current production (Git) version of Carpet running on Mac
OS 10.6.5. The code is compiled as 64 bit. This parameter file has
worked in the past, though with 32 bit on Mac OS 10.5.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/177>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#465: Hydro_InitExcision test cases take a long time
-----------------------------------+----------------------------------------
Reporter: eschnett | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: |
-----------------------------------+----------------------------------------
I am just running all test cases with an executable without optimisation,
and I find that Hydro_InitExcision takes a long time. While most other
test cases finish in a few minutes, Hydro_InitExcision takes two hours to
run. The test cases should be reduced in number, size, or duration.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/465>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#550: CarpetIOHDF5 too verbose while reading from checkpoint
-------------------------+--------------------------------------------------
Reporter: knarf | Owner: eschnett
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Carpet | Version:
Keywords: |
-------------------------+--------------------------------------------------
It is not that uncommon that I recover using a different number of
processors. Every time I do this I see the error file cluttered with
messages like
WARNING level 1 in thorn CarpetIOHDF5 processor 21 host
c312-313.ls4.tacc.utexas.edu
(line 640 of
/work/00920/tg459479/Cactus/arrangements/Carpet/CarpetIOHDF5/src/Input.cc):
-> Variable AHFINDERDIRECT::ahmask on rl 0 and tl 0 not read completely.
Will have to look for it in other files
I expect this, this is not an error and not really something to warn
about. I acknowledge that this might have been introduced when recovering
using the same number of processors was a problem and caused reading all
files, but I don't think this is an issue anymore.
I propose to change the warnlevel for this message to CCTK_WARN_DEBUG(4).
In addition it would be good to have _one_ separate message with level
CCTK_WARN_PICKY(3) if any variable/reflevel/timelevel could not be read
completely (but not one for each of these), ideally only once for all
processors. This would not clutter the output of the default simfactory
runs (-L 3) too much, but would indicate that this happened - and in case
this is a problem it's easy to enable -L 4.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/550>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#634: Riemann1D fails to compile on Kraken
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: GRHydro |
-----------------------------------+----------------------------------------
I'm unable to compile the Riemann1D utility on Kraken. It gives the
following error message.
{{{
Creating Riemann1d in /nics/d/home/hinder/Cactus/EinsteinToolkit/exe/sim
from
/nics/d/home/hinder/Cactus/EinsteinToolkit/configs/sim/build/GRHydro/Riemann1d.o
/nics/d/home/hinder/Cactus/EinsteinToolkit/configs/sim/build/GRHydro/Riemann1d.o:
In function `riemann1d':
/nics/d/home/hinder/Cactus/EinsteinToolkit/arrangements/EinsteinEvolve/GRHydro/src/util/Riemann1d.f90:10:
undefined reference to `__kmpc_begin'
/nics/d/home/hinder/Cactus/EinsteinToolkit/arrangements/EinsteinEvolve/GRHydro/src/util/Riemann1d.f90:374:
undefined reference to `__kmpc_end'
/usr/bin/ld: link errors found, deleting executable
`/nics/d/home/hinder/Cactus/EinsteinToolkit/exe/sim/Riemann1d'
make[1]: ***
[/nics/d/home/hinder/Cactus/EinsteinToolkit/exe/sim/Riemann1d] Error 1
make: *** [sim-utils] Error 2
}}}
I think that this needs an Intel library to be linked in, but I'm not sure
which one or how to add it.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/634>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#625: CapretIOHDF5 sliced output does not output symmetry points unless it also
outputs buffer points
--------------------------+-------------------------------------------------
Reporter: hinder | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version:
Keywords: CarpetIOHDF5 |
--------------------------+-------------------------------------------------
The parameter CarpetIOHDF5::output_symmetry_points = yes does not work
when CarpetIOHDF5::output_buffer_points = no (the default). This is
probably due to the line
if (not output_buffer_points) {
exts &= allactive;
}
near line 1071 in OutputSlice.cc. I suspect that allactive does not
include the symmetry points. The attached parameter file should be run on
one processor. You can then use
h5dump -d '/GRID::x it=0 tl=0 rl=0' output_symmetry/x.x.h5
Near the top you will see
DATASET "/GRID::x it=0 tl=0 rl=0" {
DATATYPE H5T_IEEE_F64LE
DATASPACE SIMPLE { ( 5 ) / ( 5 ) }
DATA {
(0): 0, 0.1, 0.2, 0.3, 0.4
}
i.e. the first point output is x = 0. For this parameter file, there
should be a symmetry point at x = -0.1. If you modify the parameter file
to use CarpetIOHDF5::output_buffer_points = yes, then the symmetry point
appears in the output.
The workaround is to always use
CarpetIOHDF5::output_buffer_points = yes
if you want to output symmetry points.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/625>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#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