Guillaume Giudicelli
Guillaume Giudicelli
I guess I owe an update here. I m delayed on the review, we have some publications and reports to take care off until mid-next week, and this is too...
@loganharbour your review has been addressed
Cant you pre-position skip_coordinate_collapsing as an unused parameter with allow_unused = true for those tests? It should go all the way to master in the particular app that way?
I'm thinking the RC loop is not captured by the perf graph. I m sure if Alex or Peter see this ticket they will immediately know.
yeah possibly we just need to add a perf graph section to ```INSFVRhieChowInterpolator::execute()```
If MOOSE does not know how to update the properties you should write your own auxkernel to output the property, that has the custom call that you need
Functors can do faces, in many different ways and discretizations. A Functor currently may not access a material property, but may retrieve as many other functors of any type you...
Functor material properties have caching as well, so you could leverage previously computed values. It s not necessarily going to be as efficient as computing them at the same time
Transfinite2DMeshGenerator ? I m referring to the object name, the one in the input file
they do have to correspond. so registerMooseObject("MooseApp", Transfinite2DMeshGenerator) but since you generate meshes from 4 points, maybe '2D' is still too general