Actually I have checked the returned element, and it seems that it is not when
executing point_value that the error came out. How can I debug this error?
const Elem *e = (*_locator)(p);
if (e == NULL || e->processor_id() != this->processor_id()) return;
v[0] = _asys->point_value(_Vx_var, p);
v[1
Definitely! Always check that the element returned from a point locator is
owned by the local processor before trying to do anything with it.
If you run in debug mode it should tell you you're trying to access out of
bounds.
Derek
On Fri, Jul 1, 2016 at 5:29 PM 张江 wrote:
> The configuration o
The configuration of the machine is
4X Intel Xeon E7-4820 v2 @ 2.00GHz CPUs
1.5TB DDR3 1600Mhz Memory (96x16GB Modules)
which can run at most 64 processes. The operating system is 64 bit.
After initialization of mesh, equation system, system and point locator, my
program use point_locator(point
How much memory do you have on your machine? Do you have more than 48GB?
Are you using a 32bit or 64bit operating system?
Derek
On Fri, Jul 1, 2016 at 2:34 PM 张江 wrote:
> Hi,
>
> I am trying to read a large data (11.7GB) with libmesh and use it for my
> application. The program runs well when
On Fri, Jul 1, 2016 at 12:34 PM, 张江 wrote:
> Hi,
>
> I am trying to read a large data (11.7GB) with libmesh and use it for my
> application. The program runs well when using just one process.
> But in parallel (mpirun -n 4), after executing a while, some errors came
> out:
>
> [0]PETSC ERROR:
> -
Hi,
I am trying to read a large data (11.7GB) with libmesh and use it for my
application. The program runs well when using just one process.
But in parallel (mpirun -n 4), after executing a while, some errors came out:
[0]PETSC ERROR:
---
