Error: Index exceeds the number of array elements

CONTENTS DELETED

CONTENTS DELETED

Thank you for reporting the issue and workaround. This type of error is generally due to failing trying to match new meshed boundaries with the old mesh, which will hopefully be improved in the future. I'm not sure yet why exporting and reimporting from FEniCS xml mesh format helps though.

That said, I'm not quite sure if your workflow is optimal here. The issue is that importing a mesh, and then re-meshing it will generally cause some degeneration in quality, as the original geometry/boundary information is not preserved in mesh formats and lost (curved surfaces are approximated by polygons etc). So I would generally recommend trying one of the following workflows:

1) Create your finished geometry and mesh entirely in gmsh, and then import the final mesh into FEATool (no remeshing in FEATool).

2) Create your geometry in gmsh (or another CAD program), and export it as a BREP or STEP CAD file. Then import the geometry into FEATool and mesh it there.

3) Create both geometry and mesh entirely in FEATool (as both gmsh and FEATool uses the same geometry engine/kernel, OpenCASCADE, technically the created geometries should be equivalent).

CONTENTS DELETED

CONTENTS DELETED

Thank you for submitting the issue details. There should be an update available next week addressing some of these issues as spaces in file names. I'm not sure about why your second case doesn't work though, as I haven't been able to reproduce it yet.

CONTENTS DELETED

ebryant wrote

I have reimaged my Windows Installation and no longer have a space in my username. Things are working much better. Thanks for the quick work on the update. Let me know when it comes out if you want me to re-test.

There is now a bug-fix FEATool update available (version 1.15.4) which should address some of the issues you have found.

Furthermore, looking at the "Grid Statistics..." in the "Grid" menu for the gmsh mesh ("index_test_case.msh"); the minimum quality of grid cells seem to be 0.00619636, which is likely you get a warning about a singular matrix when solving. Distorted mesh elements (<< 0.1 quality) can lead to poor approximation and solving, and should be avoided if possible. So when meshing (whether using gmsh or other mesh generators) it is good to take care that a high quality mesh is generated.

Also, "index_test_case" mesh here consists of three disconnected subdomains, that is the two cylinders are not connected to the base plate (even if they touch). Typically one would want domains to be connected in a simulation (so the physics interact). If this is the case you might need to apply a join/union operation to the geometry object before meshing.

CONTENTS DELETED

CONTENTS DELETED