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

Problem AMI roating mesh

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

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   May 22, 2019, 10:11
Default Problem AMI roating mesh
  #1
New Member
 
Edoardo
Join Date: Mar 2019
Posts: 15
Rep Power: 7
cutmountain is on a distinguished road
Hello everybody,

I am working on a simplyfied test case for a moving flap.

I have a stationary zone and a rotating zone and all of the mesh and the simulation seems to works well.

The problem it that watching at the tke seems like that the two zones (stationary and rotating) are not talking each others.

Looking at the velocity fields, epsilon and nut and p the two zones are talking each others but not tke.

Is something that is needed to be activated or something that I am missing?

I add two screen of two different time step on a plane cutting the rotating part for k and U and my BCs for k.

Code:
/*--------------------------------*- C++ -*----------------------------------*\
| =========                 |                                                 |
| \\      /  F ield         | OpenFOAM: The Open Source CFD Toolbox           |
|  \\    /   O peration     | Version:  4.0                                   |
|   \\  /    A nd           | Web:      www.OpenFOAM.org                      |
|    \\/     M anipulation  |                                                 |
\*---------------------------------------------------------------------------*/
FoamFile
{
    version     2.0;
    format      ascii;
    class       volScalarField;
    object      k;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

dimensions      [0 2 -2 0 0 0 0];

internalField   uniform 0.01;

boundaryField
{
    "rotor|stator"
    {
        type            kqRWallFunction;
        value           $internalField;
    }

    inlet 
    {
        type            fixedValue;
        value           uniform 0.01;
    }

    outlet
    {
        type            zeroGradient;
    }

    "AMI.*"
    {
        type            cyclicAMI;
        value           $internalField;
    }
    defaultFaces
    {
        type            slip;
    }

}

// ************************************************************************* //

Thanks in advance as always,

Edoardo.
Attached Images
File Type: jpg k1.jpg (24.8 KB, 16 views)
File Type: jpg k2.jpg (24.7 KB, 17 views)
File Type: jpg U1.jpg (33.1 KB, 19 views)
File Type: jpg U2.jpg (29.9 KB, 16 views)
cutmountain is offline   Reply With Quote

Old   May 27, 2019, 05:52
Default
  #2
New Member
 
Edoardo
Join Date: Mar 2019
Posts: 15
Rep Power: 7
cutmountain is on a distinguished road
Is there anybody out there?
cutmountain is offline   Reply With Quote

Old   May 27, 2019, 07:19
Default
  #3
Senior Member
 
louisgag's Avatar
 
Louis Gagnon
Join Date: Mar 2009
Location: Stuttgart, Germany
Posts: 338
Rep Power: 18
louisgag is on a distinguished road
Send a message via ICQ to louisgag
Ciao Edoardo,


Your post made me curious so I tried running a similar tutorial from my OpenFOAM version (foundation's release, build "dev"), and found that k was, at least apparently, properly transmitted across the AMI interface. See my attached snapshot.


The snapshot comes from the mixerVesselAMI tutorial, maybe you could find the difference between that tutorial and your case to understand why this issue happens on your setup.
From what I see it is likely not caused by the k boundary condition file you pasted here....



Kind regards,




-Louis
Attached Images
File Type: jpg Screenshot from 2019-05-27 13-13-46.jpg (46.6 KB, 8 views)
louisgag is offline   Reply With Quote

Old   May 27, 2019, 07:31
Default
  #4
New Member
 
Edoardo
Join Date: Mar 2019
Posts: 15
Rep Power: 7
cutmountain is on a distinguished road
Ciao Louis,

thanks for caring.

The problem is that I've started my case from that tutorial because it seemed to be the closest to mine problem and in that tutorial k seemed to be transmitted across the AMI.

If you have any ideas about this strange behaviour please share it.
cutmountain is offline   Reply With Quote

Old   May 27, 2019, 07:43
Default
  #5
Senior Member
 
louisgag's Avatar
 
Louis Gagnon
Join Date: Mar 2009
Location: Stuttgart, Germany
Posts: 338
Rep Power: 18
louisgag is on a distinguished road
Send a message via ICQ to louisgag
I'm not sure I would know more as I did not have such issues before (I often run without turbulence).
The only further advice I can give is to compare the fvSchemes and fvSolution files... did you change something?
louisgag is offline   Reply With Quote

Reply

Tags
amicyclic, openfoam

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
how to set periodic boundary conditions Ganesh FLUENT 15 November 18, 2020 06:09
AMI speed performance danny123 OpenFOAM 21 October 24, 2020 04:13
[ICEM] problem in mesh output mehrzad ANSYS Meshing & Geometry 2 December 10, 2014 18:07
Compressor Simulation using rhoPimpleDyMFoam Jetfire OpenFOAM Running, Solving & CFD 107 December 9, 2014 13:38
Moving mesh Niklas Wikstrom (Wikstrom) OpenFOAM Running, Solving & CFD 122 June 15, 2014 06:20


All times are GMT -4. The time now is 16:11.