Blog Posts

Writing to the Console output object

Each MooseObject now has a member variable (_console) which is essentially an output stream connecting to the Console output object(s). It allows messages to be passed through the Moose output system, thus properly handled when parameters such as 'output_initial' or 'interval' are being utilized. This message will also be included in the Console file output, if enabled.

July MOOSE Workshop!

We're happy to announce the dates of the next MOOSE workshop! It will be held here, in Idaho Falls, ID on July 8th, 9th and 10th. This course is offered at no cost to you... and is intended for anyone that wants to come up to speed on how to use MOOSE to create multiphysics applications.

Removing [AuxBCs] block

The [AuxBCs] block is being removed from MOOSE. All AuxKernels should be added via the [AuxKernels] block. Setting the 'block' parameter will cause the AuxKernel to operate on elements and setting the 'boundary' parameter will cause it to operate on boundaries.

We're Hiring!

We're hiring on the MOOSE Framework team! Come join a high-intensity computational science team that is devoted to open source and innovative development methods!

Automatic Material Property Output

It is now possible to quickly enable outputting of material properties directly from the Materials sub-blocks, simply set the outputs parameter to any output names defined in the [Outputs] block (or set it to all for the properties to come out on all Outputs), following the same syntax as in Postprocessors. You can restrict this to just outputting certain properties by employing the output_properties parameter:

R&D 100

Recent Blog Posts

Using our new clang-format Style

6 months, 2 weeks ago

Steady State Algorithm Change

1 year, 3 months ago

Making an App inherit from an App

1 year, 3 months ago

Changing a published API (Deprecation)

1 year, 4 months ago

DiscreteMaterial Objects

1 year, 6 months ago

Recent Posts

Archive

2017
2016
2015
2014

Tags

Authors

Feeds

RSS / Atom