#1869: output active regions for IOHDF5
--------------------------------------------+-------------------------------
Reporter: jonah.maxwell.miller@… | Owner: eschnett
Type: defect | Status: new
Priority: minor | Milestone:
Component: Carpet | Version: development version
Keywords: HDF5 |
--------------------------------------------+-------------------------------
When generating *.h5 files (i.e., using IOHDF5::out_every and
IOHDF5::out_vars), Carpet outputs some metadata describing the active
region for each grid. However, when generating files that end with
*.xyz.h5 (i.e., IOHDF5::out3D_every), this metadata is not generated. It
would be nice if this metadata were generated.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1869>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1838: CactusUtils/WatchDog: is part of ET or not?
-----------------------------------+----------------------------------------
Reporter: bmundim | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: WatchDog |
-----------------------------------+----------------------------------------
if yes, then:
{{{
https://bitbucket.org/einsteintoolkit/manifest/pull-requests/6/add-
cactusutils-watchdog-to-the-thornlist/diff
}}}
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1838>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1840: ExternalLibraris/pthreads does not provide CCTK_PTHREADS define
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner: rhaas
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit thorn | Version: development version
Keywords: pthreads |
-----------------------------------+----------------------------------------
This means it is not a drop in replacement for the old mechanism and eg
HTTPD complains at runtime with:
{{{
WARNING level 1 from host comet-ln3.sdsc.edu process 0
while executing schedule bin HTTP_Startup, routine
HTTPD::HTTP_StartServer
in thorn HTTPD, file
/home/rhaas/cactus/ET_trunk/arrangements/CactusConnect/HTTPD/src/Startup.c:97:
-> Parameter 'HTTPD::use_pthreads' is set to "yes" but you didn't
configure with PTHREADS. Setting will be ignored.
}}}
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1840>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1867: Refluxing crashes when reducing the number of active refinement levels
---------------------------------+------------------------------------------
Reporter: dradice@… | Owner: eschnett
Type: defect | Status: new
Priority: major | Milestone:
Component: Carpet | Version: development version
Keywords: |
---------------------------------+------------------------------------------
Refluxing fails when the number of active refinement levels is decreased
with the following error message:
{{{
Refluxing/src/correct.cc:549: void flux_register_coarse_reset(const cGH*
): Assertion `size == levels' failed.
}}}
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1867>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1863: Carpet feature request
-------------------------+--------------------------------------------------
Reporter: sbrandt | Owner: eschnett
Type: enhancement | Status: new
Priority: optional | Milestone:
Component: Carpet | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
I frequently find myself editing CallFunction.cc to put some special pre
call and post call functions in place. Sometimes, I just want to see a
message when I exit and exit a function, so I have context for any other
print messages I see in the log. Another use I have is to provide
automatic checks to see when a function modifies a variable (by doing
checksums before and after), and so on. I have a few more.
What I'd like to have is the ability to register a function to run before
a call and/or after a call. In principle, Accelerator_PreCall/PostCall
could then use this mechanism rather than having carpet call them
explicitly. The attached patch implements this functionality. I assume
that there are lots of things about my implementation that people won't
like, but I attach it anyway as a prototype.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1863>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1854: Very large global grid points leading termination
-------------------------------------------+--------------------------------
Reporter: himanshukharkwal765@… | Owner: himanshukharkwal765@…
Type: defect | Status: new
Priority: major | Milestone: ET_2015_11
Component: Cactus | Version: development version
Keywords: grid global terminate |
-------------------------------------------+--------------------------------
In WaveMol/gaussian.par whenever we increase our global grid points to
more than 350 the program terminates abruptly.
I am attaching gaussian.par file and hn1.lnmiit.ac.in.ini
(simfactory/mdb/machines/hn1.lnmiit.ac.in.ini).
HPC Details-
Node: 6
Processor: http://ark.intel.com/products/75277/Intel-Xeon-
Processor-E5-2680-v2-25M-Cache-2_80-GHz
Q1. Is there anything wrong inside .par or .ini file?
Q2. Should i use Carpet instead of PUGH?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1854>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1860: handle symbolic links more gracefully in simfactory
------------------------+---------------------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version: development version
Keywords: |
------------------------+---------------------------------------------------
The pull request is here:
https://bitbucket.org/simfactory/simfactory2/pull-requests/8/rhaas-
symbolic_links_in_simlib/diff
Before having simfactory's sourcebasedir be a symbolic link interacted
badly with using $PWD to get the current directory and to properly remove
the sourcebasedir path prefix from strings. This set of commits fixes
this.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1860>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1859: use OPENSSL_DIR variable instead of SSL_DR
------------------------+---------------------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: SimFactory | Version: development version
Keywords: |
------------------------+---------------------------------------------------
This is pull request
https://bitbucket.org/simfactory/simfactory2/pull-requests/2/use-
openssl_dir-rather-than-ssl_dir/diff
for simfactory. The ExternalLibrary only looks at OPENSSL_DIR and not
SSL_DIR. Currently the simfactory files only contain comments commenting
on the fact that SSL_DIR will likely be ignored. Since we know it will be
ignored it seems better to use the correct OPENSSL_DIR variable.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1859>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1857: TAT/Slab error running BBHLowRes
---------------------------------+------------------------------------------
Reporter: msahrling@… | Owner: Mikael Sahrling
Type: defect | Status: new
Priority: major | Milestone:
Component: Cactus | Version: ET_2015_05
Keywords: |
---------------------------------+------------------------------------------
Hi,
I see the following error when running
'/repos/einsteinexamples/par/arXiv-1111.3344/bbh/BBHLowRes.par':
WARNING level 0 from host mars process 0
while executing schedule bin BoundaryConditions, routine
RotatingSymmetry180::Rot180_ApplyBC
in thorn RotatingSymmetry180, file
/home/mikael/Astronomy/GeneralRelativity/ET/Cactus/configs/sim/build/RotatingSymmetry180/rotatingsymmetry180.c:447:
-> TAT/Slab can only be used if there is a single local component per
MPI process
What to do? Something in the .par file that can be adjusted?
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1857>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1856: Improve stack backtraces
-------------------------+--------------------------------------------------
Reporter: eschnett | Owner: eschnett
Type: enhancement | Status: new
Priority: optional | Milestone:
Component: Carpet | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
I found <https://stackoverflow.com/questions/77005/how-to-generate-a
-stacktrace-when-my-gcc-c-app-crashes>. We should go through the example
here, and compare to our code to see whether we can improve it.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1856>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit