Elmer Discussion Forum

I did this, in addition to the previous change, I could not find any additional changes required. The converted already supported 827

int facenodes = degree * faceedges;
if (code == 827) facenodes = 9;

Correlation to theory will be dependent on mesh quality. Element type is critical, first order (linear) triangles and tetrahedrons are unacceptable for ElasticSolver or StressSover. 2nd order is a must for those element times and a reasonably fine mesh. Quads and hexa are much better, and 2nd order ...

I believe the intention was to use the wave solver for the time domain solution Model 14 Wave Equation Module name: WaveSolver Module subroutines: WaveSolver Module authors: Juha Ruokolainen, Peter R˚aback, Mika Malinen Document authors: Mika Malinen 14.1 Introduction This module can be used to solv...

A change to the ElmerGUI code allows ElmerGUI to load the H27 with the 409 boundary the change was in meshutils.cpp starting at line 1717 There was surface information for orientation of the 408 element but nothing for the 409 element adding the 409 resolved the issue, which I believe was only a dis...

With the H27, changing the boundary element from 409 to 408, allows the mesh to load into ElmerGUI.

Mesh.SecondOrderIncomplete=1

did create 820 from gmsh which loaded fine into Elmer.

gmsh, salome can support H8, H20, H27 all will work with ElmerSolver

H27 will not load into ElmerGUI with the boundary element 409. If there are no boundary elements then the solid elements will.

They often call utility programs for common functions across all solvers.
I clone the source files to my hard drive which allows me to search inside the files for text.

https://github.com/ElmerCSC/elmerfem/tr ... rc/modules

scroll down to Helmholtz

For the difference in 2D and 3D I suspect that the two were developed at different times by different programmers and where just not made consistent.