Fenics has error with mesh when solving

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Fenics has error with mesh when solving

aidan123
I am trying to solve a concentric cylinder model with fenics however every time I try to place one geometry within another and try to solve with fenics it gives me an error. There are 2 cylinders one with radius 1 and one with radius 3. The outer cylinder boundary has potential of 100V and the inner cylinder boundary has potential of 0V. I just used the geometry button in FEATool to create one cylinder inside the other. WHen I try to solve with fenics I get the error below, but when I try to solve with the general solver it works. Any help would be great thanks!




Calling FEniCS Solver.
featool-fenics 21-Jul-2021 17:13:13 : START
 
Traceback (most recent call last):
  File "featool-fenics.py", line 22, in <module>
    f.read(bdr, "/boundary")
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-support@googlegroups.com
***
*** Remember to include the error message listed below and, if possible,
*** include a *minimal* running example to reproduce the error.
***
*** -------------------------------------------------------------------------
*** Error:   Unable to read meshfunction topology.
*** Reason:  Mesh dimension mismatch.
*** Where:   This error was encountered inside HDF5File.cpp.
*** Process: 0
***
*** DOLFIN version: 2019.2.0.dev0
*** Git changeset:  unknown
*** -------------------------------------------------------------------------
 
 
featool-fenics 21-Jul-2021 17:13:13 : STOP
 
 
Importing FEniCS solution.
 
Deleting FEniCS data and log files.
Reply | Threaded
Open this post in threaded view
|

Re: Fenics has error with mesh when solving

Precise Simulation
Administrator
This post was updated on .
Thanks for the issue report. This seems to be an issue with FEniCS mesh specification for 3D geometries with >= 2 sub-domains. There will be an update 1.14.2 with a fix next available week sometime.