We wasted some ARCHER time with a channel simulation that defined the <flowextension> XML element for the inlet but not for the outlet. In this scenario, RBCs are not removed when they reach the end of the computational domain and all kind of things can go wrong.
<flowextension> needs to be kept optional in the inlet/outlet XML definition in case the user wants to run homogeneous fluid simulations (Newtonian or generalised-Newtonian). However, if the <redbloodcells> element is defined we should error if the user didn't provide a <flowextension> definition for all inlets/outlets.
We wasted some ARCHER time with a channel simulation that defined the
<flowextension>
XML element for the inlet but not for the outlet. In this scenario, RBCs are not removed when they reach the end of the computational domain and all kind of things can go wrong.<flowextension>
needs to be kept optional in the inlet/outlet XML definition in case the user wants to run homogeneous fluid simulations (Newtonian or generalised-Newtonian). However, if the<redbloodcells>
element is defined we should error if the user didn't provide a<flowextension>
definition for all inlets/outlets.