This is a read only copy of the old FEniCS QA forum. Please visit the new QA forum to ask questions

Problem with unstructured meshes and mshr

0 votes

Hi all,
I noticed that when I run this code:

from dolfin import*
from mshr import *
import pylab as plt
import numpy as np

# LOAD MESH AND SUBDOMAINS

refine = 30
smoothing = 100

q = Rectangle(Point(0.0, 0.0), Point(1., 1.))
mesh0 = generate_mesh(q, refine)
mesh0.smooth(smoothing)

mesh = Mesh(mesh0)

FI = FunctionSpace(mesh0, "Lagrange", 2)
FInew = FunctionSpace(mesh, "Lagrange", 2)

I get the following error:

[0]PETSC ERROR: ------------------------------------------------------------------------
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, probably memory access out of range
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[0]PETSC ERROR: or see http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind[0]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory corruption errors
[0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and run 
[0]PETSC ERROR: to get more information on the crash.
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD 
with errorcode 59.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------

while running this code:

from dolfin import*
from mshr import *
import pylab as plt
import numpy as np

# LOAD MESH AND SUBDOMAINS


mesh0 = UnitSquareMesh(32, 32, 'crossed')
mesh = Mesh(mesh0)

FI = FunctionSpace(mesh0, "Lagrange", 2)
FInew = FunctionSpace(mesh, "Lagrange", 2)

everything goes well.
How can I fix this?

Thank you in advance for your advice,
Lisa

asked Dec 19, 2014 by lisa_grementieri FEniCS Novice (240 points)

Same error for me. Except that, sometimes it crashes with this error but sometimes it just runs fine.

...