Blog Posts

Defaults For Coupling

First: A HUGE thanks to Cody for doing a lot of the C++ voodoo to make all of this work!

No Comm World

We do our best to insulate our users from needing to think about parallel issues in their applications. However, even with our best efforts there are still times when you need to perform your own MPI communication... but even in those cases we provide helper functions.


Preconditioning multiphysics problems is a complicated issue... but I'll try to shed some light. For further reading there is a fairly lengthy explanation of all of this in the MOOSE Workshop Manual which you can snag here:

Default Output Naming Scheme

I updated the default naming scheme for the [Outputs] block:

Time For libMesh Update

It's that time: we have updated the version of libMesh that MOOSE is relying on so you need to take action. This comes in two steps:

R&D 100

Recent Blog Posts

Using our new clang-format Style

2 years, 2 months ago

Steady State Algorithm Change

2 years, 11 months ago

Making an App inherit from an App

2 years, 12 months ago

Changing a published API (Deprecation)

3 years ago

DiscreteMaterial Objects

3 years, 2 months ago

Recent Posts






RSS / Atom