View Issue Details

IDProjectCategoryView StatusLast Update
0003311OpenFOAMBugpublic2019-07-22 12:04
ReporterdeOliveira-R Assigned Tohenry  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
PlatformGNU/LinuxOSUbuntuOS Version15.04
Fixed in Versiondev 
Summary0003311: h field BC crashes reconstructPar and ParaView
DescriptionI was running a heat transfer problem and trying to see if I was extracting heat in an unintended place. To that end, I used the writeObjects function object to output the enthalpy field h.
The field is written correctly, however the boundary conditions of the written field are

type gradientEnergy;
gradient uniform 0;

and this causes reconstructPar and ParaView to crash with:

--> FOAM FATAL IO ERROR:
Essential entry 'value' missing

file: /home/deoliveira_r/OpenFOAM/deoliveira_r-6/run/tutorials/heatTransfer/buoyantPimpleFoam/hotRoom/2000/h.boundaryField.fixedWalls from line 4444 to line 4445.

    From function Foam::fvPatchField<Type>::fvPatchField(const Foam::fvPatch&, const Foam::DimensionedField<Type, Foam::volMesh>&, const Foam::dictionary&, bool) [with Type = double]
    in file /home/deoliveira_r/OpenFOAM/OpenFOAM-6/src/finiteVolume/lnInclude/fvPatchField.C at line 131.

FOAM exiting

I believe this should be handled transparently by both reconstructPar, ParaView and any other field reader.
Steps To ReproduceUse the "writeObject" function object to output the h field of a heat transfer solver (buoyantPimpleFoam for example).
Run the simulation on hotRoom tutorial.

reconstructPar should fail with FOAM FATAL IO ERROR: Essential entry 'value' missing.
If not run in parallel, there is no need for reconstructPar but ParaView will crash instead with the same error.
TagsNo tags attached.

Activities

henry

2019-07-22 12:04

manager   ~0010633

Resolved by commit b5f471585a8b9a7197646a6b74b80d72942b83cd

Issue History

Date Modified Username Field Change
2019-07-22 10:14 deOliveira-R New Issue
2019-07-22 12:04 henry Assigned To => henry
2019-07-22 12:04 henry Status new => resolved
2019-07-22 12:04 henry Resolution open => fixed
2019-07-22 12:04 henry Fixed in Version => dev
2019-07-22 12:04 henry Note Added: 0010633