ManuGraiph

Thanks a lot Marco!

> I also experience the same problem. > > The only workaround I found is to disable commit message editors: > > ```json > "git.useEditorAsCommitInput": false > ``` This is...

The Fenics project is totally abandoned. The examples in the tutorial have like insanely long-time outdated libraries & methods upstream.

I wrote a reproductible example: ``` m1v = np.array([[17903.93947473, 11418.12995419, 2572.68075251],[17889.43531656, 11423.09300945, 2546.89320749],[17913.65204344, 11446.51421055, 2572.68075251],[17899.14788527, 11451.47726581, 2546.89320749]]) m2v = np.array([[17897.68174692, 11454.30365475, 2573.22453367],[17917.8546173 , 11442.45883457, 2554.44274633],[17882.4917027 , 11428.43354543, 2573.22453367],[17902.66457308, 11416.58872525, 2554.44274633]])...

Adding that when creating the mesh did the trick, now it didn't crash, but i think it's just that with that subdivide the verts just don't fall into whatever is...

If instead of the subdivide i just apply a `m1.shift(dx=0.01,dy=0,dz=0)` it also works, it's something 100% related to the node specific positions. The thing is, i can't fix it programatically,...

What version of `vtk` and python are you using @marcomusy ?

Can't find the 9.0.3 version of vtk anywhere, not on pip, conda, or even the wheel. I'm sure the issue is in vtk.

Yeah, basically anything that you do to alter those specific points (subdivide, a shift, rounding the verts, etc) make it work. Could you please elaborate a bit on the equations...

Well, yeah, the intersection between two infinite planes is an easy to implement solution, but i'm not so sure if it will be so easy with finite planes, that's why...