CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Running, Solving & CFD

When i run my case...crashhh

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   April 25, 2013, 04:43
Default When i run my case...crashhh
  #1
Member
 
ynos
Join Date: Jan 2011
Posts: 39
Rep Power: 15
ynos is on a distinguished road
Dear Foamers,
I am doing an air jet simulation , my geometry is OK according to checkMesh. I ran my case and after moving about the start way of my simulation, the running had some high and crazy results, I do not why? .. can any body helps me please because I tried with differents fvSolutions and fvSchemes files but not got good results .
I tried differents ways, first only without rig, then without stayl and asimsails but crash too
If somebody can i help me...
Thanks in advanced
Simón

/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2.1.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 2.1.1-221db2718bbb
Exec : checkMesh
Date : Apr 25 2013
Time : 10:05:46
Host : "simon-simon"
PID : 3591
Case : /home/simon/Escritorio/POINTWISEmallas/ejemplovelaspointwise
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create polyMesh for time = 0

Time = 0

Mesh stats
points: 313652
faces: 3374127
internal faces: 3239593
cells: 1649842
boundary patches: 12
point zones: 0
face zones: 0
cell zones: 0

Overall number of cells of each type:
hexahedra: 0
prisms: 0
wedges: 0
pyramids: 14352
tet wedges: 0
tetrahedra: 1635490
polyhedra: 0

Checking topology...
Boundary definition OK.
Cell to face addressing OK.
Point usage OK.
Upper triangular ordering OK.
Face vertices OK.
Number of regions: 1 (OK).

Checking patch topology for multiply connected surfaces ...
Patch Faces Points Surface topology
asim 44386 22195 ok (closed singly connected)
deck 3441 1832 ok (non-closed singly connected)
hull 4934 2680 ok (non-closed singly connected)
main 6970 3487 ok (closed singly connected)
rig 14956 14656 ok (closed singly connected)
stayl 6954 3479 ok (closed singly connected)
xmax 9948 5148 ok (non-closed singly connected)
xmin 9906 5127 ok (non-closed singly connected)
ymax 7222 3761 ok (non-closed singly connected)
ymin 17795 9149 ok (non-closed singly connected)
zmax 4030 2140 ok (non-closed singly connected)
zmin 3992 2121 ok (non-closed singly connected)

Checking geometry...
Overall domain bounding box (-64.5 -0.000207407 -75) (85.5 60 75)
Mesh (non-empty, non-wedge) directions (1 1 1)
Mesh (non-empty) directions (1 1 1)
Boundary openness (4.36547e-16 2.02156e-15 -1.58891e-16) OK.
Max cell openness = 4.21878e-16 OK.
Max aspect ratio = 44.4492 OK.
Minumum face area = 1.73905e-05. Maximum face area = 13.2876. Face area magnitudes OK.
Min volume = 4.89894e-08. Max volume = 15.3649. Total volume = 1.34994e+06. Cell volumes OK.
Mesh non-orthogonality Max: 84.6841 average: 22.4909
*Number of severely non-orthogonal faces: 1495.
Non-orthogonality check OK.
<<Writing 1495 non-orthogonal faces to set nonOrthoFaces
Face pyramids OK.
Max skewness = 2.81383 OK.
Coupled point location match (average 0) OK.

Mesh OK.

End
files.tar.gz

1.jpg

2.jpg

3.jpg

4.jpg
ynos is offline   Reply With Quote

Old   April 25, 2013, 04:58
Default
  #2
Member
 
Ignacio
Join Date: Jan 2013
Posts: 33
Rep Power: 13
ignacio is on a distinguished road
Hello,

CheckMesh seems to be fine, but look at this

Mesh non-orthogonality Max: 84.6841 average: 22.4909
*Number of severely non-orthogonal faces: 1495.
Non-orthogonality check OK.
<<Writing 1495 non-orthogonal faces to set nonOrthoFaces

You should check the location of these cells in paraFoam (select include sets), if they are in a boundary layer 84 degress can cause some problems.
Can you also put the log file from the solver to see how it crashes?
ignacio is offline   Reply With Quote

Old   April 25, 2013, 05:32
Default
  #3
Member
 
ynos
Join Date: Jan 2011
Posts: 39
Rep Power: 15
ynos is on a distinguished road
Thanks Ignacio
Attached the file forces.dat ,you will look that the pressure results growing very fast around Time 100, really dont crash the case but the results are not good.
Attached non-orthogonal file...about that how is possible get better this??? maybe in fvSolution:

SIMPLE
{
nNonOrthogonalCorrectors 4????????????????????????????????????????????????;
pRefCell 0;
pRefValue 0;
}

Thanks a lot.


Simón

Last edited by ynos; April 25, 2013 at 05:47.
ynos is offline   Reply With Quote

Old   April 25, 2013, 05:42
Default
  #4
Member
 
Ignacio
Join Date: Jan 2013
Posts: 33
Rep Power: 13
ignacio is on a distinguished road
Hola Simon,

Hablo Espanol, pero te respondo en ingles para que sea mas facil para los demas ayudarte.

In paraFoam do: Properties tree > Select Include Sets > A new icon will appear in Mesh Parts box, select it > Apply.

I guess 4 non-orthogonal correctors is fine. But you can always increase it till.. lets say 15. The simulation will stop when the variable reaches the tolerance that you define, so it wont increase a lot the computational time.

What did you use to create the mesh? ICEM? snappyHexMesh?
if you used ICEM you can use the option of improving orthogonality automatically.
ignacio is offline   Reply With Quote

Old   April 25, 2013, 06:00
Default
  #5
Member
 
ynos
Join Date: Jan 2011
Posts: 39
Rep Power: 15
ynos is on a distinguished road
Thanks Ignacio
Now i can check nonortogonal faces
I try run the case with nNonOrthogonalCorrectors 4 or more and then I will tell you the results
I did the mesh with Pointwise, I will try getting better the mesh in Pointwise and I will run the case with nNonOrthogonalCorrectors 4 or more and then I will tell you the results.
Tnaks for everything
Simón
ynos is offline   Reply With Quote

Old   April 29, 2013, 17:10
Default running potentialfoam
  #6
New Member
 
sid
Join Date: Apr 2013
Posts: 6
Rep Power: 12
sidmajor is on a distinguished road
Hello everybody, it's my first time and i really need help to run potentialfoam with cylinder i've always got this following error:

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time



--> FOAM FATAL IO ERROR:
"ill defined primitiveEntry starting at keyword 'const' on line 52 and ending at line 137"

file: /home/sid-major/OpenFOAM/root-2.2.0/run/tutorials/basic/potentialFoam/cylinder/system/controlDict at line 137.

From function primitiveEntry::readEntry(const dictionary&, Istream&)
in file lnInclude/IOerror.C at line 132.

FOAM exiting


can someone help me please?
sidmajor is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Case running in serial, but Parallel run gives error atmcfd OpenFOAM Running, Solving & CFD 18 March 26, 2016 12:40
Case created in one machine does not run in another comedy_tigers88 OpenFOAM Running, Solving & CFD 0 May 8, 2012 04:02
How obtain a Mach number value from a case run with Xifoam solver?? lfgmarc OpenFOAM Programming & Development 0 June 15, 2011 03:00
MPI PROBLEMS gtg627e OpenFOAM Running, Solving & CFD 20 October 5, 2007 04:02
Free surface boudary conditions with SOLA-VOF Fan Main CFD Forum 10 September 9, 2006 12:24


All times are GMT -4. The time now is 14:30.