When running a Hippo app, you generally do not need a Variable or Kernel to solve, Hippo is just running OpenFOAM and copying the boundary temperatures into an AuxVariable. Apparently, MOOSE will still calculate the residual of the (non-aux) variables, even if there aren't any, resulting in a division by 0 and a SIGFPE signal.
In the cases I've tested, MOOSE will ignore these and carry on, which is fine. However, OpenFOAM (at least my version), will trap the SIGFPE and abort by default.
There are two solutions/workarounds I've found:
Add a dummy variable to your MOOSE input file. As I've done in some tests.
Run unset FOAM_SIGFPE && unset FOAM_SETNAN before running the app.
Outputs
Find a clean way to avoid the SIGFPE signals aborting the program, or document how to work around them.
Description
When running a Hippo app, you generally do not need a Variable or Kernel to solve, Hippo is just running OpenFOAM and copying the boundary temperatures into an AuxVariable. Apparently, MOOSE will still calculate the residual of the (non-aux) variables, even if there aren't any, resulting in a division by 0 and a SIGFPE signal.
In the cases I've tested, MOOSE will ignore these and carry on, which is fine. However, OpenFOAM (at least my version), will trap the SIGFPE and abort by default.
There are two solutions/workarounds I've found:
unset FOAM_SIGFPE && unset FOAM_SETNANbefore running the app.Outputs