|
[Sponsors] |
Unexpected behaviour of timeVaryingMappedFixedValue |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
July 13, 2012, 22:03 |
Unexpected behaviour of timeVaryingMappedFixedValue
|
#1 |
New Member
Join Date: Jul 2012
Posts: 5
Rep Power: 14 |
Hi Guys,
this is my first post but not my first experience with this forum. I worked on CFD since about 2 years and this forum was always a great source of usefull information. So thanks for all your great work here. Now I got an unexpected problem and I would be glad to hear some experiences and opinions. I want to investigate the development of turbulence in time and space by calculating a direct numerical simulation (DNS). The geometrical setup is a simple channel. To avoid development of a boundary layer I use symmetry conditions on the "walls". To generate the inlet conditions I previously ran a simulation with a pseudospectral code (hit3d) and extracted slices. I fed these slices into my channel domain by using the "timeVaryingMappedFixedValue" boundary condition for U. So far everything seems to be perfect. While postprocessing I got some unexpected behaviour of the turbulence on the inlet. A closer look reveled a strange behaviour of the inlet conditions: Timestep t1: HIT Simulation ................... OpenFOAM Timestep t2: HIT Simulation ................... OpenFOAM The four pictures show the slice which is defined in the constants/boundaryData/inlet directory (called HIT Simulation) and the slice extracted from the inlet in the result file of openFOAM (called openFOAM) for two different time steps. In timestep t1 you can see, that the pictures (respectively the velocity fields) are very simmilar. If you have a closer look you would see that the magnitude of the velocity is different: The velosity in the openFOAM solution is less than in the HIT slice. Timestep t2 shows a complete reverse behaviour: It is still the same field, but the velocities in openFOAM are incrased compared to the HIT slice. This is a very unexpectable behaviour (for me!). The grid resolution in the plane is in both cases 128² so I would exclude interpolation errors. Did someone experienced problems like this? Do you have any idea what is going on while interpolating? Is there any other interpolation? I would be glad to share more information if you need more. Thanks in advance for your help. Kopy |
|
July 15, 2012, 19:15 |
|
#2 |
New Member
Join Date: Jul 2012
Posts: 5
Rep Power: 14 |
Hey Guys,
I would like to disable interpolation of the inlet conditions just to check if this is the reason for the damping of my velocity field. Is it possible to disable the interpolation without touching the source code? |
|
July 18, 2012, 16:11 |
|
#3 |
New Member
Join Date: Jul 2012
Posts: 5
Rep Power: 14 |
Solved my problem.
My physical setup caused a pressure gradient. The input data works just fine. |
|
March 15, 2013, 12:27 |
|
#4 |
Senior Member
Julien
Join Date: Jun 2012
Location: France
Posts: 152
Rep Power: 14 |
Hi Kopy,
could you explain me be a bit more about "My physical setup caused a pressure gradient. The input data works just fine. " ? What about your p-inlet? What BC did you use for outlet? |
|
Tags |
dns, icofoam, inlet boundary condition, varyingmappedfixedvalue |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
unexpected flow speeds within porous zones | MasterCooler | OpenFOAM | 11 | May 2, 2012 08:48 |
Odd residual behaviour for Two Layer K Epsilon | dvcauwe | Main CFD Forum | 1 | March 7, 2012 06:47 |
Unstable behaviour after long period of stablility | plunge11 | FLUENT | 1 | April 6, 2011 10:15 |
Installation of OpenFOAM15dev | antonio_ing | OpenFOAM Installation | 34 | December 18, 2009 11:06 |
Modelling Industrial cyclone behaviour | Günther Hasse | Main CFD Forum | 3 | October 12, 1999 20:34 |