#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
#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
#1855: BitBucket pull requests for ET components should go to the tickets mailing
list
-----------------------------------+----------------------------------------
Reporter: hinder | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: Server Infrastructure | Version: development version
Keywords: |
-----------------------------------+----------------------------------------
If someone creates a pull request in an repository hosting ET thorns, then
there should be an email notification to the ET tickets mailing list,
otherwise nobody will know that it has been made unless they are
explicitly watching that repository. And there are a lot of repositories.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1855>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit