CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM

help: results depend on writeInterval

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

Reply
 
LinkBack Thread Tools Display Modes
Old   March 31, 2010, 05:10
Default help: results depend on writeInterval
  #1
New Member
 
Christian Koch
Join Date: Mar 2010
Posts: 1
Rep Power: 0
ckoch is on a distinguished road
Hi everyone !

I am using OpenFOAM for simulating solidification of a two immiscible fluids. For that, I augmented the interFoam solver with a few things such as heat-treatment, thermophysical properties and a solidification model. As you can imagine, the solver-code now looks pretty different to the original one. So far, my first runs gave me promising results.
BUT
yesterday when I did a long-time simulation, the results differed heavily from former ones.
My first runs, which gave me physically feasible results, used a delta_t of 1e-3 sec and I wrote out every 10th timestep.
Then the long-time run used the same delta_t of 1e-3 sec but a writeInterval of 1000 timesteps (to have one data folder for each second). So far the code ran smoothly with little courant-no and continuity-errors. But the visualization showed highly unphysical behaviour that differed heavily from the runs with every 10th timestep written out.
I did NOT change the delta_t, ONLY the writeInterval.
Has anyone made a similar experience ?
Any idea on what could cause that behaviour ?
I guess my code overwrites a variable from the last timestep with a value that it reads from the last written-out folder. But apart from the createFields.H (which I definately only use once BEFORE the time-loop) I could not find any read-and-write command, at least in the code lines I did by myself.
Does anyone know of OpenFOAM reading values from the last WRITTEN-OUT timestep rather than using the value from the actual last timestep ?
I am using 1st order "Euler" as ddt-scheme and my controlDict looks as follows

application myFreezeFoam;
startFrom startTime;
startTime 0;
stopAt endTime;
endTime 20;
deltaT 0.001;
writeControl timeStep;
writeInterval 1000;
purgeWrite 0;
writeFormat ascii;
writePrecision 6;
writeCompression uncompressed;
timeFormat general;
timePrecision 6;
runTimeModifiable no;
adjustTimeStep no;
maxCo 0.1;
maxDeltaT 0.1;

Thanks a lot for any suggestions and best regards,

Chris
ckoch is offline   Reply With Quote

Old   March 31, 2010, 07:39
Default
  #2
Member
 
Costas K
Join Date: Nov 2009
Location: UK
Posts: 51
Rep Power: 7
thekay is on a distinguished road
Send a message via ICQ to thekay Send a message via MSN to thekay
Have you made sure that you don't have alpha1=0 in your visualising of the results? This can give strange results with phases.
thekay is offline   Reply With Quote

Old   September 1, 2010, 18:42
Default
  #3
Member
 
Join Date: Nov 2009
Posts: 48
Rep Power: 7
farhagim is on a distinguished road
Hi Chris,

Have you managed to solve your problem? Would you please explain how did you implement a solidification in interFoam.
Is it possible to share your implementation?

Thanks,

Mehran

Quote:
Originally Posted by ckoch View Post
Hi everyone !

I am using OpenFOAM for simulating solidification of a two immiscible fluids. For that, I augmented the interFoam solver with a few things such as heat-treatment, thermophysical properties and a solidification model. As you can imagine, the solver-code now looks pretty different to the original one. So far, my first runs gave me promising results.
BUT
yesterday when I did a long-time simulation, the results differed heavily from former ones.
My first runs, which gave me physically feasible results, used a delta_t of 1e-3 sec and I wrote out every 10th timestep.
Then the long-time run used the same delta_t of 1e-3 sec but a writeInterval of 1000 timesteps (to have one data folder for each second). So far the code ran smoothly with little courant-no and continuity-errors. But the visualization showed highly unphysical behaviour that differed heavily from the runs with every 10th timestep written out.
I did NOT change the delta_t, ONLY the writeInterval.
Has anyone made a similar experience ?
Any idea on what could cause that behaviour ?
I guess my code overwrites a variable from the last timestep with a value that it reads from the last written-out folder. But apart from the createFields.H (which I definately only use once BEFORE the time-loop) I could not find any read-and-write command, at least in the code lines I did by myself.
Does anyone know of OpenFOAM reading values from the last WRITTEN-OUT timestep rather than using the value from the actual last timestep ?
I am using 1st order "Euler" as ddt-scheme and my controlDict looks as follows

application myFreezeFoam;
startFrom startTime;
startTime 0;
stopAt endTime;
endTime 20;
deltaT 0.001;
writeControl timeStep;
writeInterval 1000;
purgeWrite 0;
writeFormat ascii;
writePrecision 6;
writeCompression uncompressed;
timeFormat general;
timePrecision 6;
runTimeModifiable no;
adjustTimeStep no;
maxCo 0.1;
maxDeltaT 0.1;

Thanks a lot for any suggestions and best regards,

Chris
farhagim is offline   Reply With Quote

Reply

Tags
different results, interfoam, read error, read results, writeinterval

Thread Tools
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 On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
OpenFOAM - Validation of Results Ahmed OpenFOAM Running, Solving & CFD 9 June 22, 2011 18:59
Different Results from Fluent 5.5 and Fluent 6.0 Rajeev Kumar Singh FLUENT 6 December 19, 2010 12:33
compile errors of boundary condition "expDirectionMixed" liying02ts OpenFOAM Bugs 2 February 1, 2010 21:11
validation of CFD results andy FLUENT 0 June 13, 2007 13:55
Problems with repeating results Lee CD-adapco 4 May 26, 2006 03:39


All times are GMT -4. The time now is 00:40.