Sebastian Wolf

I created a coarse symmetric mesh and then moved one node by 20m (element size ~200m in that region) and I could reproduce a faulty behaviour :/

Top: Almost symmetric mesh, with one node moved, Bottom: symmetric mesh. Note the different scales for top and bottom.  Edit: t = 0.5s

You can find the meshes here: https://syncandshare.lrz.de/getlink/fiKLV98vp9x3J7BpSYiFDv/TPV5-issue-546

@mariusbohn, thanks for your changes and the effort! Indeed, the dynamic parameter is hard to implement. (Not necessarily hard, but you need to know, where to look at ;-))

I suppose, @Thomas-Ulrich's answer solved the issue. If not, please reopen.

Indeed strange, thanks for reporting!

Intel compilers "Debug" mode still uses some optimizations. See also #298 for that matter. Or you could try gcc, which doesn't optimize that aggresively in "Debug" mode.

Hi, it is actually `LIKWID_MARKER_CLOSE` in the main file. This just flipped in, as I was simplifying the code ;-) When I remove the threadinit, nothing changes.

Interestingly, thread 1 collects some data, and thread 0 reports a unhalted runtime of 1.4e10 seconds, but I did not wait 443 years for this result :D ``` +----------------------+---------------------+------------+------------+------------+------------+------------+------------+------------+ |...

Thanks for the recomendation. I tried the current master (39acba747ae3f6549d11659df1f612b87951d385) and the fix from #476. Current master gives me the same problem as before and with 185b4df6915ed65c27365981e0692213599c4025, I get the...