Problem - simulation crashes by changing flow velocity
Hi foamers,
I've modified the icoFsiFoam tutorial so that I have two beams one after the other. I want to investigate how the second one affects the flow field. The original flow velocity at the inlet was 4 m/s but I have to change it to 1.5 m/s because the simulation crashes - too high Courant numbers. What do I have to change to make the simulation possible to run with 4 m/s or even higher inlet velocities? I've already adjusted the time step dynamically with adjustableRunTime and set the maximal Courant number to be 0.5. Thanks in advance! Harak |
Hi,
What is a value of your initial time step? |
Hi alexeym,
Thanks for the quick reply. This is how my controlDict looks like: Code:
application icoFoam; |
Hi,
OK. Now find minimum cell size of your mesh, take your initial time step and calculate Co. |
Hi again,
Do you mean I have to look for my smallest cell size of my mesh? http://s12.postimg.org/sap3c48u5/Mesh.png In this case it is 0.00636324. |
Well, I meant that you need to calculate Courant number using your inlet velocity, initial time step and minimum mesh cell size (in fact min(Vi/Ai)).
So questions: 1. What happens if you reduce deltaT (let's say 1e-5) instead of inlet velocity? 2. Though mesh seems to be fine, can you post checkMesh output? 3. Can you post actual error message? 4. Your initial and boundary conditions? |
I really appreciate your help!
What does min(Vi/Ai) mean? Is it the smallest cell size in x and y-direction? 1. I tried it with 1e-5 and with the original inlet velocity and it crashes. https://dl.dropboxusercontent.com/u/...log.icoFsiFoam 2. This is checkMesh: Code:
Create time 4. motionU Code:
dimensions [0 1 -1 0 0 0 0]; Code:
dimensions [0 2 -2 0 0 0 0]; Code:
dimensions [0 1 -1 0 0 0 0]; |
Hi,
1. Yes, it is minimum size of the mesh in x or y direction. Here's how OpenFOAM calculates Courant number: Code:
CoNum = 0.5*gMax(sumPhi/mesh.V().field())*runTime.deltaTValue(); Code:
writeControl timeStep; |
hello,
You use totalPressure for p at outlet, so you should use pressure(InletOutlet, ...)Velocity BC familly for U at outlet too. regards, olivier |
So, with 4 m/s and timeStep for writeControl and 1 for writeInterval I get the following velocity distribution:
t=1e-5 http://s3.postimg.org/pj67u8czn/velocity1.png t=2e-5 http://s28.postimg.org/cd9yo2wrh/velocity2.png t=3e-5 http://s13.postimg.org/ll77kdeqv/velocity3.png After here, it crashes again. And again logfile: https://dl.dropboxusercontent.com/u/...tydistribution @olivierG What kind of BC would you suggest? |
hello,
Just try pressureInletOutletVelocity. regards, olivier |
Just like this?
0/U Code:
|
Quote:
Have you had the opportunity to have a look at my case? I'm stuck.. Really appreciate your help! Thanks. Harak |
Hi,
Change of BC did not help? Please attach archive of the case, it'll be simpler; guess there no NDA as you've posted mesh and screenshots. |
1 Attachment(s)
Unfortunately, it didn't.
In this configuration I can only run the simulation at 1.5 m/s. And another question: Why does the simulation crash, too, when I change the E-Module in the mechanicalProperties in solid? For example from 2e+6 to 2e+3. I would be stranded without your help! Thanks in advance :) |
Quote:
have you had time to look over it? And, what do you mean with "..there no NDA.."? Thanks! |
Hi,
Yes, but without success yet. NDA is NDA. And as "there is no NDA" you can post the case on the forum. |
I did not know about the NDA
Thanx man :) |
Quote:
I talked to my supervisor regarding this problem and he assumed that it could be because of my limited computer ressources (I've got an old Notebook with 4GB RAM). As soon foam-extend is installed on the super-computers of my department, I'll try to run it over there. Maybe it was just as easy as that :D I'll let you know :) |
Really, is it system limitation?
Advice: Your mesh can be handled with present system configuration :) |
All times are GMT -4. The time now is 03:16. |