[rafal]

Hi all,
I am trying to understand mixerVessel2D and
i stuck (i need somebodys help).
Here is what i figured out so far.

I have found small script makeMesh.
lets do it by parts:
1) generating blockMeshDict file by macros (inexpensive clever way of generating blockmesh on parameters)

m4 <constant/polymesh/blockmeshdict.m4> constant/polyMesh/blockMeshDict

2) than standard mesh generation on the basis of blockMeshDict generated in 1)
blockMesh .. mixerVessel2D

3) generation of a set of cells belonging to zone rotor
cellSet .. mixerVessel2D

4) take cells obtained in 3) generate faces of those cells
cp system/faceSetDict_rotorFaces system/faceSetDict
faceSet .. mixerVessel2D

5) take faces from 4) and delete boundary faces
cp system/faceSetDict_noBoundaryFaces system/faceSetDict
faceSet .. mixerVessel2D
- is that right? what boundaries?All? why?

6) write faceZones for the mesh on the basis of 5)
setsToZones .. mixerVessel2D -noFlipMap

so at the end we generated list of faces belonging to rotor region that are not boundary faces of a region?
but why do we need this?


7) next kind of mistery is a file constant/MRFZones.
it contains:
name of zone = rotor - thats ok
patch = rotor (unfortunately patch of this case has the same name like region :/) - what patch(es) i should specify here? all that are under centrifugal and/or Coriolis force that would normally rotate?
origin, axis, omega - the rest is ok except look 8)

8) MRFZones defines origin, axis, omega the same things are defined in dynamicMeshDict.
but wait, why do i need dynamicMeshDict in MRF? in MRF i have static mesh and i dont need sliding interfaces. is that right?
i deleted this file and MRFSimpleFoam runs without problem.

Does the existance of this file mean that i can actually somehow run it like old mixer2D in OF13? in a transient way with sliding interface?
I tried icoDyMFoam with some minor fixes and it does not recognize mixerFvMesh as a valid type of dynamicFvMesh.
mixerFvMesh exist in topoChangerFvMesh. how it is used in OF14? is it used at all?


I will be happy to read any post giving light on any of this points.

cheers,
rafal

[gabriel]

Hi Rafa,

did you succeed understanding MRFsimpleFoam?

Bests Gabriel

[rafal]

Hi Gabriel,
I have understood some parts of it, but I quit the
idea and no longer use it. If you drop me an email
with the parts you do understand and with the parts
you have problem with maybe I will be able to help
you.

[mahendra]

Hi people

Can anyone please send me details with regards to simulation of Moving Refrence Frame Problem using OpenFOAM. I am unable to decipher anything form the Tutorial Problem....

My Eamil: mahendra.wankhede@gmail.com

Regards,
Mahendra

[vbesteban]

Originally Posted by rafal

Hi all,
I am trying to understand mixerVessel2D and
i stuck (i need somebodys help).
Here is what i figured out so far.

I have found small script makeMesh.
lets do it by parts:
1) generating blockMeshDict file by macros (inexpensive clever way of generating blockmesh on parameters)

m4 <constant/polymesh/blockmeshdict.m4> constant/polyMesh/blockMeshDict

2) than standard mesh generation on the basis of blockMeshDict generated in 1)
blockMesh .. mixerVessel2D

3) generation of a set of cells belonging to zone rotor
cellSet .. mixerVessel2D

4) take cells obtained in 3) generate faces of those cells
cp system/faceSetDict_rotorFaces system/faceSetDict
faceSet .. mixerVessel2D

5) take faces from 4) and delete boundary faces
cp system/faceSetDict_noBoundaryFaces system/faceSetDict
faceSet .. mixerVessel2D
- is that right? what boundaries?All? why?

6) write faceZones for the mesh on the basis of 5)
setsToZones .. mixerVessel2D -noFlipMap

so at the end we generated list of faces belonging to rotor region that are not boundary faces of a region?
but why do we need this?


7) next kind of mistery is a file constant/MRFZones.
it contains:
name of zone = rotor - thats ok
patch = rotor (unfortunately patch of this case has the same name like region :/) - what patch(es) i should specify here? all that are under centrifugal and/or Coriolis force that would normally rotate?
origin, axis, omega - the rest is ok except look 8)

8) MRFZones defines origin, axis, omega the same things are defined in dynamicMeshDict.
but wait, why do i need dynamicMeshDict in MRF? in MRF i have static mesh and i dont need sliding interfaces. is that right?
i deleted this file and MRFSimpleFoam runs without problem.

Does the existance of this file mean that i can actually somehow run it like old mixer2D in OF13? in a transient way with sliding interface?
I tried icoDyMFoam with some minor fixes and it does not recognize mixerFvMesh as a valid type of dynamicFvMesh.
mixerFvMesh exist in topoChangerFvMesh. how it is used in OF14? is it used at all?


I will be happy to read any post giving light on any of this points.

cheers,
rafal

Dear Rafal.

Have you received an answer about this question? I really need the same help, I'm stuck.

I really appreciate your time. Thanks and best regards.