Benedict
Benedict
See also https://github.com/JuliaCon/proceedings-review/issues/138#issuecomment-1796282098
We are seeing the same error for libtrixi, see https://github.com/trixi-framework/libtrixi/pull/156#issuecomment-1881100318
True! I realized this in the meantime as well, but have not finished the MPI syncing of element counts.
# Summary ## Global number of elements and dofs `nodofsglobal` and `nelementsglobal` are now used in the `Base.show` output of semidiscretizations and meshes, and of the AnalysisCallback. For `DG`, `nodofsglobal`...
Woohoo! Thanks for the hint. I had no idea how much stuff had already been around.
Sure! But to clarify: Show global numbers *instead* of local ones? OR Show global *and* local numbers?
Finally! t8code's latest patch release v3.0.1 contains @jmark's long desired fix for the cubed sphere. This is now ready to be reviewed and merged!
Thanks for your help @JoshuaLampert . I would be fine with reducing the runtime. The only argument I can think of is that we would like to reproduce the corresponding...
I added this test case for `StructuredMesh` and then copied it for `TreeMesh` to test the different flux implementations. I was not aware of the quad restriction in the first...
I just came across this error when trying to run Trixi on a Grace Hopper node. In my case it was caused by the MPI reductions for stepsize computation: https://github.com/trixi-framework/Trixi.jl/blob/20ab97bea82fbd4c286f8fc4cebad6ee12a1e465/src/callbacks_step/stepsize_dg3d.jl#L133...