Elmer Discussion Forum

An update added by juharu has fixed the bug. There was an uninitialised parameter being used in part of the Mortar Boundary code. To be precise, this line: https://github.com/ElmerCSC/elmerfem/commit/fa05cacb836366f8b4322ad239bba42aaadf0f84 Now when I update to the latest version (latest git or late...

Hi kevinarden, Thank you for having a look. My reason for calling this a bug is that different builds of Elmer do not experience any crashing. I have a friend with an older version of the ppa installation ( https://launchpad.net/~elmer-csc-ubuntu/+archive/ubuntu/elmer-csc-ppa ) which has not crashed...

I've recently been playing with a particular mechanical simulation problem and found a surprisingly broad spectrum of behaviours. I've run the attached example 8 times this morning and had: - 5 successful executions - two overflow/underflow errors with the message "Norm of solution appears to b...

I have been playing with some contact mechanics in Elmer but feeling like there is something I'm missing. My experience so far has been that results often look a bit suspicious and can be quite fragile with lots of failed simulations for one reason or another. I'm hoping someone on this forum might ...

For completeness, here is a set of test cases which I think demonstrates the full behaviour: test.zip A quick summary, the physical setup is that there is a disk inside an annulus where the inner boundary of the annulus exactly matches the boundary of the disk. The sif file attaches an outwards forc...

Thank you both for helping clarify what's happening. From a user perspective it feels buggy because it's not documented and not consistent. In the three geometries I've tried: - all of the boundaries are preserved from gmsh version 2 - ElmerGrid fails with a message of unsupported features in versio...

Cross-posting from github issue I have a gmsh file which specifies 28 "PhysicalNames" but unfortunately the resulting "mesh.names" file only contains 14 of them. Please see the original post for more details, but feel free to interact on either platform. The problem appears to be...