Hi Cody,
Yes, I'm able to compile and run a simple MPI program which prints rank and
size of MPI_COMM_WORLD. I used the same environment as my LibMesh
environment:
-bash-4.1$ icc -v
icc version 15.0.3 (gcc version 4.4.7 compatibility)
-bash-4.1$ mpiicc -v
mpiicc for the Intel(R) MPI Library 5.0 U
Can you successfully compile and run a simple MPI hello world program and
get the right rank size and messages out? If you your environment is not
sane (different at runtime than it was during compile) you might have
problems with MPI in general.
Cody
On Wed, Mar 9, 2016 at 2:10 PM Harshad Sahasr
Hi John,
I tried compiling my simple test code (pasted) with -DNDEBUG flag. I don't
get the error due to ghosted vector. The problem is
libmesh_init.comm().size() is always 1 irrespective of how many processes I
run it with. I also tried initializing MPI before libmesh and passing the
communicator
>
> Forgot to mention, this probably indicates that something is very wrong
> with your build, i.e. you are linking against a out-of-date debug version
> of the library by accident, or something else equally weird. I would
> definitely try to fix this issue before worrying about other issues.
It
Hi John,
>
>
> Forgot to mention, this probably indicates that something is very wrong
> with your build, i.e. you are linking against a out-of-date debug version
> of the library by accident, or something else equally weird. I would
> definitely try to fix this issue before worrying about other i
On Tue, Mar 8, 2016 at 12:12 PM, Harshad Sahasrabudhe
wrote:
> Hi John,
>
> I assume you mean "opt" mode, otherwise that doesn't make sense because
>> the error you are referring to above is an assert, which is only active in
>> debug mode.
>
>
> Yes, this doesn't make sense to me either. I'm run
On Tue, Mar 8, 2016 at 12:12 PM, Harshad Sahasrabudhe
wrote:
> Hi John,
>
> I assume you mean "opt" mode, otherwise that doesn't make sense because
>> the error you are referring to above is an assert, which is only active in
>> debug mode.
>
>
> Yes, this doesn't make sense to me either. I'm run
This is the error message generated by the above code:
#0 0x0031ee0ac69d in waitpid () from /lib64/libc.so.6
#1 0x0031ee03e609 in do_system () from /lib64/libc.so.6
#2 0x0031ee03e940 in system () from /lib64/libc.so.6
#3 0x2af721f1b1bf in (anonymous
namespace)::gdb_backtrace(st
Hi John,
I assume you mean "opt" mode, otherwise that doesn't make sense because the
> error you are referring to above is an assert, which is only active in
> debug mode.
Yes, this doesn't make sense to me either. I'm running in "opt" mode, but
this assert still gets triggered.
I have pasted a
On Tue, Mar 8, 2016 at 11:35 AM, Harshad Sahasrabudhe
wrote:
> Hi,
>
> I'm running into a problem with ghost vectors created with PetscVector in
> LibMesh 0.9.5 PETSc 3.5.4. When I call the operator(), the call fails at
> the assert local_index < _local_size (petsc_vector.h:1214). The _local_size
Hi,
I'm running into a problem with ghost vectors created with PetscVector in
LibMesh 0.9.5 PETSc 3.5.4. When I call the operator(), the call fails at
the assert local_index < _local_size (petsc_vector.h:1214). The _local_size
variable in PetscVector is 0 (after _get_array is called) even if the *
11 matches
Mail list logo
