[Rophys]

Hi Everybody,

I've seen that some tutorial cases is not running correctly in the OpenFoam, so this new thread open a space for the CDF online members discuss and learn how to solve this problems.

Let's start:

* I am using the solver rhoCentralFoam to solve the biconic25-55Run35 case and I followed the this steps:
1-blockMesh (ok)
2-checkMesh (ok)
3-setFields
Gave me the following error:
--> FOAM FATAL ERROR:
Cannot find file "points" in directory "polyMesh" in times 0 down to constant

From function Time::findInstance(const fileName&, const word&, const IOobject::readOption)
in file db/Time/findInstance.C at line 175.
4-rhoCentralFoam
The same output of the step 3

So, anybody know how to run this case ?

Thanks a lot

[akidess]

Look at the Allrun file in the parent directory (tutorials/compressible/rhoCentralFoam/Allrun). There's quite a few extra steps to take for this tutorial to work.

[Rophys]

Thanks for this Akidess, but for me is not so clear how to do this.

In the Allrun file we have:

if [ "$case" = "biconic25-55Run35" ] ; then
cd $case

wmake datToFoam
runApplication datToFoam grid256.dat

CONST="constant"
cat $CONST/pointsHeader $CONST/points.tmp > $CONST/polyMesh/points
runApplication collapseEdges "2e-07" 5
moveTimeMeshToConstant

echo "Changing patch type to wedge type in boundary file"
mv $CONST/polyMesh/boundary $CONST/polyMesh/boundary.bak
sed -f $CONST/wedgeScr $CONST/polyMesh/boundary.bak > $CONST/polyMesh/boundary
rm $CONST/polyMesh/boundary.bak

For me is not clear how to do this steps...if you explain me...I will really appreciate. Many thanks

[akidess]

If you just want to look at the results, just execute ./Allrun and the script will do everything for you automatically.

All the steps are done because the mesh is specified as a .dat file in this case instead of a standard blockMeshDict, and that's why the additional steps are required.

[Rophys]

That's perfect. Thanks again.

One more question. The command ./Allrun run all the cases in the folder right ?

If I want to run only the biconic case, how can I procedure for this ?

[akidess]

That's right. In the top part of the Allrun file you can find a list of the cases to run. Just make a copy of the Allrun file, and shorten that list to only contain the biconic case, and then run the modified Allrun file. Possibly you will have to make it executable by running "chmod +x AllrunCopy" once before you attempt to run the script.

[Rophys]

Hi Anton,

Thanks for the tips.

I already ran the biconic case using the script Allrun and everything looks ok and another question arose for me. I want to do by my own the same tutorial case as a manner to understand, step by step, how it works. Using the script Allrun is not clear enough for me the sequence of commands that I should use to run my biconic case. Could you explain me ?

Thanks

[davidvzq]

Good day,
I realize it's been some time since this post was made, however I have been recently working with this case and wanted to know the reason for the U, p, and T, files having a series of numbers before the conditions for the boundaries are actually set. I don't see this in the forwardStep case.

I can only deduce that it is giving the internal field a set of fixed values.

The reason I want to know is because I want to apply a different mesh but with the same conditions the tutorial case has (speed, temp, pressure, molWeight, etc.)

Would it be okay to simply delete these seemingly random numbers and set my own internal field? Or would this cause problems?

If anyone replies to this, I will be pleasantly surprised.

DVA.