Gwyneth
Can you produce a stack backtrace? Or can you show more output, in particular while setting Carpet::veryverbose = yes?
I don't think this error is related to the bboxset class, so disabling bboxset2 is unlikely to help.
-erik
Disclaimer - University of Cape Town This e-mail is subject to UCT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/--
On Tue, Mar 21, 2017 at 4:32 PM, Gwyneth Allwright <allgwy001@myuct.ac.za> wrote:
Hi Erik, Ian, Frank:
Thankfully, I managed to get Open MPI working on my laptop and can now run things again!
I tried running the parameter file that produces the error on the HPC. Previously, the error did not appear on my laptop, but now it does (when running on two processes). I don't think there's an issue with a very small domain and a very large number of MPI processes here.
I get:
Assertion failed: (all(stride == other.stride)), function binary_operator, file /Users/gwynethallwright/Cactus/arrangements/Carpet/CarpetLib /src/bboxset2.hh, line 261.
The simulation seems to abort immediately after TwoPunctures finishes setting up the initial data and the actual evolution begins.
Should I try compiling with -DCARPET_DISABLE_BBOXSET2 on my laptop?
Gwyneth
On Mon, Mar 13, 2017 at 2:49 PM, Ian Hinder <ian.hinder@aei.mpg.de> wrote:
On 13 Mar 2017, at 13:14, Gwyneth Allwright <allgwy001@myuct.ac.za> wrote:
> Hi Ian, Frank, Erik,
>
> Thanks for the comments!
>
> Ian, I'm using my full cluster core allocation for simulations at the moment, but should be able to get back to you about adjusting CPPFLAGS in a few days' time. The same goes for changing the number of MPI processes (I was indeed using a much higher number of processes when running on the cluster).
Does the problem appear immediately? Can you run on your laptop with the same number of MPI processes as you were using on the cluster when you saw the error?
> Frank, I haven't been able to find a (direct and obvious) indication of which bboxset implementation is used in the output. But I've attached it to the ticket, so you're welcome to have a look. (Erik did say that it was bboxset2.)
The error indicates that it is definitely using bboxset2 on the cluster. The question is what is used on your laptop. The logic that decides which implementation to use is in
arrangements/Carpet/CarpetLib/src/defs.hh:
// Disable bboxset2 if C++11 is not supported
#if !defined(HAVE_CCTK_CXX_AUTO_SPECIFIER) || \
!defined(HAVE_CCTK_CXX_LAMBDA) || !defined(HAVE_CCTK_CXX_RANGE_BASED_FOR)
#ifndef CARPET_DISABLE_BBOXSET2
#define CARPET_WARN_DISABLE_BBOXSET2
#endif
#undef CARPET_DISABLE_BBOXSET2
#define CARPET_DISABLE_BBOXSET2
#endif
#ifndef CARPET_DISABLE_BBOXSET2
#define CARPET_ENABLE_BBOXSET2
#define CARPET_USE_BBOXSET2
#endif
Assuming that you are using gcc on your laptop, you could add compile-time output which will tell you which is being used:
// Disable bboxset2 if C++11 is not supported
#if !defined(HAVE_CCTK_CXX_AUTO_SPECIFIER) || \
!defined(HAVE_CCTK_CXX_LAMBDA) || !defined(HAVE_CCTK_CXX_RANGE_BASED_FOR)
#ifndef CARPET_DISABLE_BBOXSET2
#define CARPET_WARN_DISABLE_BBOXSET2
#endif
#undef CARPET_DISABLE_BBOXSET2
#define CARPET_DISABLE_BBOXSET2
#pragma message "bboxset2 disabled"
#endif
#ifndef CARPET_DISABLE_BBOXSET2
#define CARPET_ENABLE_BBOXSET2
#define CARPET_USE_BBOXSET2
#pragma message "bboxset2 enabled"
#pragma message "bboxset2 used"
#endif
(the only changes are to add the pragma lines).
On my laptop, this gives
COMPILING arrangements/Carpet/CarpetLib/src/bboxset1.cc
In file included from /Users/ian/Cactus/EinsteinToolkitGit/arrangements/Carpet/Car petLib/src/bboxset1.cc:9:0:
/Users/ian/Cactus/EinsteinToolkitGit/arrangements/Carpet/Car petLib/src/defs.hh:34:17: note: #pragma message: bboxset2 enabled
#pragma message "bboxset2 enabled"
^
/Users/ian/Cactus/EinsteinToolkitGit/arrangements/Carpet/Car petLib/src/defs.hh:35:17: note: #pragma message: bboxset2 used
#pragma message "bboxset2 used"
Disclaimer - University of Cape Town This e-mail is subject to UCT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 9111. If this e-mail is not related to the business of UCT, it is sent by the sender in an individual capacity. Please report security incidents or abuse via csirt@uct.ac.za
policies/emaildisclaimer/ or obtainable from +27 21 650 9111. If this e-mail is not related to the business of UCT, it is sent by the sender in an individual capacity. Please report security incidents or abuse via csirt@uct.ac.za