CFD Online Discussion Forums - Bug? Helyx-OS 1.0.3 for OpenFOAM-2.2.1 ?

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)

- OpenFOAM Pre-Processing (https://www.cfd-online.com/Forums/openfoam-pre-processing/)

- - Bug? Helyx-OS 1.0.3 for OpenFOAM-2.2.1 ? (https://www.cfd-online.com/Forums/openfoam-pre-processing/123693-bug-helyx-os-1-0-3-openfoam-2-2-1-a.html)

Bug? Helyx-OS 1.0.3 for OpenFOAM-2.2.1 ?

Hi,

I tried creating a buoyantBoussinesqPimpleFoam test case using HelyxOS-1.0.3 for an OpenFOAM-2.2.1 installation and got the following problem:

Code:

--> FOAM FATAL IO ERROR: 

cannot find file



file: /home/admin1/Engys/HelyxOS/run/testCylinder/0/alphat at line 0.



    From function regIOobject::readStream()

    in file db/regIOobject/regIOobjectRead.C at line 73.



FOAM exiting

I checked the 0 directory and the alphat file, and it seems HelyxOS is not creating it either. Has this happened to anybody?. HelyxOS-1.0.2 did not create it, but it seems it wasn't required by OpenFOAM-2.2.0 whereas OpenFOAM-2.2.1 does require it.

JR22,

yep, this is a change that was made in standard OpenFOAM and is being updated in HELYX-OS. I can walk you through these changes that will be made and also give you a workaround that will get things working again.

Go into the HELYX-OS/v1.0.3/ directory and find

Code:

caseSetupDict.fields

and make a copy for good measure (and keep it in a safe place) and then do a find and replace of kappat with alphat
Go to the same directory and find

Code:

caseSetupDict.stateData.buoyantBousinesqSimpleFoam

make a copy for good measure (and keep it in a safe place) and find and replace kappat to alphat
Next, restart HELYX-OS to get these new defaults and then go to "edit script" and add

Code:

rm $CASE/constant/radiationProperties

before the mpirun. This is because a radiation model will need to be specified if the radiationProperties file is present...so lets delete it for now.

That should do it for now but the fix will be out soon to get this taken care of correctly/officially :D More thorough testing should also be done to make sure this does not affect other solver, so if you find any issues then report back here. Thanks for pointing that out, because this is how the tool improves!