problem creating function space

Issue #30 resolved
Former user created an issue

this used to work and only recently started giving the following error.

ubuntu@ip-172-31-23-251:~$ python Python 2.7.6 (default, Jun 22 2015, 17:58:13) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or "license" for more information.

import mshr from dolfin import * domain=mshr.Rectangle(Point(0.,0.),Point(8.,8.)) domain.set_subdomain(1,mshr.Circle(Point(4.,4.),1)) t4=mshr.generate_mesh(domain,45) V0 = FunctionSpace(t4, 'DG', 0) Warning: Mesh is empty, unable to create entities of dimension 2. Warning: Mesh is empty, unable to create entities of dimension 2. Warning: Mesh is empty, unable to create entities of dimension 2. Warning: Mesh is empty, unable to create entities of dimension 2. Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/dist-packages/dolfin/functions/functionspace.py", line 468, in init FunctionSpaceBase.init(self, mesh, element, constrained_domain) File "/usr/lib/python2.7/dist-packages/dolfin/functions/functionspace.py", line 168, in init dolfin_dofmap = cpp.DofMap(ufc_dofmap, mesh) File "/usr/lib/python2.7/dist-packages/dolfin/cpp/fem.py", line 660, in init _fem.DofMap_swiginit(self,_fem.new_DofMap(*args)) RuntimeError:

------------------------------------------------------------------------- DOLFIN encountered an error. If you are not able to resolve this issue *** using the information listed below, you can ask for help at


*** fenics@fenicsproject.org


Remember to include the error message listed below and, if possible, include a minimal running example to reproduce the error.


------------------------------------------------------------------------- Error: Unable to create mesh entity. Reason: Mesh entity index 0 out of range [0, 0] for entity of dimension 2. Where: This error was encountered inside MeshEntity.cpp. *** Process: 0


DOLFIN version: 1.6.0 Git changeset: unknown *** -------------------------------------------------------------------------

Comments (1)

  1. Benjamin Dam Kehlet

    The bug introduced when upgrading to CGAL 4.6 (a patch to CGAL was not applied correctly). I have reimplemented this to avoid using the problematic CGAL package.

  2. Log in to comment