Changes in mesh recipe and solver settings will invariable result in different CFD solutions. Consequently, it is important to ensure consistency over the lifetime of a project, especially if it is long running or has a number of involved engineers.
Thankfully, bramble has been developed to help enforce consistent CFD settings and flag when discrepancies are detected.
Template Cases and Locking
Users in bramble create template cases. These are all the CFD settings required to run a simulation, such as mesh recipe and boundary conditions, contained within a single input deck.
When a simulation is created, users simply select which template case they want to use. The idea being that an experienced CFD engineer can define a template case that is then provided to other users.
Once a template case has been used in a simulation it is locked, which is to say that no further changes can be made to this template, nor can it be deleted. This ensures that, as long as this template is used, it will produce a consistent CFD setup.
Spot Changes Easily
Of course, a user may select the wrong template case or create a new template case with an updated recipe. Thankfully, bramble will flag this change making it it clear to users that, firstly, the template case is different to the baseline and also flagging what has changed in the mesh recipe. The former is highlighted in the CFD Setup tab, and the latter will cause a failure in the pre-check stage of the lifecycle.
