Closed thelfer closed 2 years ago
The origin of the error lies down in the implementation of the computeResultantForceOnBoundary
post-processing which only considered the contributions of the elements with one face in common with the considered boundary. For triangles, one should also consider the contributions of elements which has a node in common with the considered behaviour.
Things are quite strange. The error is exactly a factor 2 using linear triangles but it completly depends on the order used. This is not the case with quadrangles which always give the correct result.