catching fails with bad input (fluxSummary)
As raised on EP1510, using errors
handling in fluxSummary does not work.
With an empty or missing surface, it still tries a lookupObject
for the phi field. Within objectRegistry this lookup failure triggers an abort(FatalError)
, which cannot be caught.
Possible fixes:
- downgrade abort() to exit()? ... maybe not good
- check for field iff the surface actually has faces
- use cfind instead of lookup within fluxSummary
- a second template parameter on lookupObject:
template <class Type, bool Abort=true> lookupObject( ... )
Related to #1779 (closed)