Elmer Discussion Forum

Hi Juris,

What if you increase the size at line 4602. E.g. to
CALL CheckBuffer( 8*TotalL + ParEnv % NumOfNeighbours*(1+MPI_BSEND_OVERHEAD) )

-Peter

Hi Eric,

What is the size of your variable?

Are you sure that your case is an UDF rather than a Solver. If you have transient history then the Solver provides some services to advance a variable forward when doing timestepping. So what would the UDF do? The answer depends on your goal.

-Peter

Hi It seems that the flags "Discontinuous Bodies" + "Save Boundaries Only" are incompatible. Probably not done used much together. If the fields are discontinous then the value on the boundary is not uniquely defined. Which side to take? Then it may actually be better to use flag...

The 27 node quad is rather seldomly used that maybe there is some inconsistency in the treatment of the boundary indexes. Should not happen. You might upload the files & procedure as a bug report here in the forum / or github issue.

-Peter

Hi

And if you say:

ElmerGrid 14 2 gmsh.msh -autoclean -partdual -metiskway 16

-Peter

Hi,

Does it work for linear elements? It tries to identify the parent of the boundary element and obviously fails. The parent is found by matching indexes.

Which code has written the initial mesh.* files?

-Peter

Hi

This is not a warning: You just have the code rather verbose and it tells you that "variable 2" was given type based on the keyword "variable 1" that is named in the keyword database. We could make this even lower priority.

-Peter

Hi Sorry, I was reading hastily. So if you want to really solve the displacements also you should apply the nodal forces directly for the elasticity solver. Here conforming mesh is assumed. For example see, https://github.com/ElmerCSC/elmer-elmag/blob/main/CoilOnIronCore/case.sif The key lines are D...

Hi The way to proceed is indeed to 1) Use AVSolver to solver for electric/magnetic fields 2) Use CalcFields solver to compute nodal forces 3) Some up nodal forces and moments for each piece. Now 1) and 2) are shown in many test cases (as that of Kevin in force.sif). The step 3) is a minor technicali...

Hi Kevin,

The HelmholtzStructure cases are hierarchical: structure -> acoustics. The FsiShoebox* cases are strongle coupled: structure <-> acoustics.

-Peter