HronTurekFsi3 foam-extend3.1

Maimouna · January 13, 2016, 08:22

Hello Woj3x,

the transportProperties and the rheologyProperties files are shown

Code:

/*--------------------------------*- C++ -*----------------------------------*\
| =========                 |                                                 |
| \\      /  F ield         | foam-extend: Open Source CFD                    |
|  \\    /   O peration     | Version:     3.0                                |
|   \\  /    A nd           | Web:         http://www.extend-project.de       |
|    \\/     M anipulation  |                                                 |
\*---------------------------------------------------------------------------*/
FoamFile
{
    version     2.0;
    format      ascii;
    class       dictionary;
    object      transportProperties;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

nu              nu [0 2 -1 0 0 0 0]  0.513; // for Re = 100

rho             rho [1 -3 0 0 0 0 0] 1000; 

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

Code:

/*--------------------------------*- C++ -*----------------------------------*\
| =========                 |                                                 |
| \\      /  F ield         | foam-extend: Open Source CFD                    |
|  \\    /   O peration     | Version:     3.0                                |
|   \\  /    A nd           | Web:         http://www.extend-project.de       |
|    \\/     M anipulation  |                                                 |
\*---------------------------------------------------------------------------*/
FoamFile
{
    version     2.0;
    format      ascii;
    class       dictionary;
    object      rheologyProperties;
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //

planeStress no; //No for 3D, Yes for 2D

rheology
{
    type linearElastic;

    rho rho [1 -3 0 0 0 0 0] 7.82e3; 
    E E [1 -1 -2 0 0 0 0]   2.0e10; //Young's modulus--> elasticity value
    nu nu [0 0 0 0 0 0 0]   0.265; //Poisson's ratio
    omega omega [0 0 0 0 0 0 0] 105; // rad/s
    thickness thickness [0 1 0 0 0 0 0] 0.1;
}

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

I will try what you suggest. I hope that could help.

Many thanks

Maimouna

Maimouna · January 19, 2016, 09:19

Hi All,

could you please help me to answer the following questions

1. What is the easiest way to mesh the 3D case (picture attached)?
2. Is blockMesh is helpful in that case?
3. If yes, how could start?
4. Is there any easy way to change the blockMeshDict file for the 2D case (attached) to 3D case according to its dimensions if the blockMeshDict file for fluid and solid are shown respectively

Code:

/*--------------------------------*- C++ -*----------------------------------*\ 
| =========                 |                                                 | 
| \\      /  F ield         | OpenFOAM: The Open Source CFD Toolbox           | 
|  \\    /   O peration     | Version:  2.2.2                                 | 
|   \\  /    A nd           | Web:      www.OpenFOAM.org                      | 
|    \\/     M anipulation  |                                                 | 
\*---------------------------------------------------------------------------*/ 
FoamFile 
{ 
    version     2.0; 
    format      ascii; 
    class       dictionary; 
    object      blockMeshDict; 
} 
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // 
 
convertToMeters 1;//dimensions in meters --> conversion 1 
 
vertices 
( 
    (0 0 0) //0 
    (4.5 0 0) //1 
    (5.5 0 0) //2 
    (9.5 0 0) //3 
    (13 0 0) //4 
    (19.5 0 0) //5 
 
    (19.5 2 0) //6 
    (19.5 5.5 0) //7 
    (19.5 5.97 0) //8 
    (19.5 6.03 0) //9 
    (19.5 6.5 0) //10 
    (19.5 10 0) //11 
 
    (19.5 12 0) //12 
    (13 12 0) //13 
    (9.5 12 0) //14 
    (5.5 12 0) //15 
    (4.5 12 0) //16 
    (0 12 0) //17 
 
    (0 10 0) //18 
    (0 6.5 0) //19 
    (0 5.5 0) //20 
    (0 2 0) //21 
 
    (4.5 10 0) //22 
    (5.5 10 0) //23 
    (9.5 10 0) //24 
    (13 10 0) //25 
 
    (4.5 6.5 0) //26 
    (5.5 6.5 0) //27 
    (9.5 6.5 0) //28 
    (13 6.5 0) //29 
 
    (5.5 6.03 0) //30 
    (9.5 6.03 0) //31 
    (13 6.03 0) //32 
 
    (5.5 5.97 0) //33 
    (9.5 5.97 0) //34 
    (13 5.97 0) //35 
 
    (4.5 5.5 0) //36 
    (5.5 5.5 0) //37 
    (9.5 5.5 0) //38 
    (13 5.5 0) //39 
 
    (4.5 2 0) //40 
    (5.5 2 0) //41 
    (9.5 2 0) //42 
    (13 2 0) //43 
 
    (0 0 0.05) //44 <== 0 
    (4.5 0 0.05) //45 <== 1 
    (5.5 0 0.05) //46 <== 2 
    (9.5 0 0.05) //47 <== 3 
    (13 0 0.05) //48 <== 4 
    (19.5 0 0.05) //49 <== 5 
 
    (19.5 2 0.05) //50 <== 6 
    (19.5 5.5 0.05) //51 <== 7 
    (19.5 5.97 0.05) //52 <== 8 
    (19.5 6.03 0.05) //53 <== 9 
    (19.5 6.5 0.05) //54 <== 10 
    (19.5 10 0.05) //55 <== 11 
 
    (19.5 12 0.05) //56 <== 12 
    (13 12 0.05) //57 <== 13 
    (9.5 12 0.05) //58 <== 14 
    (5.5 12 0.05) //59 <== 15 
    (4.5 12 0.05) //60 <== 16 
    (0 12 0.05) //61 <== 17 
 
    (0 10 0.05) //62 <== 18 
    (0 6.5 0.05) //63 <== 19 
    (0 5.5 0.05) //64 <== 20 
    (0 2 0.05) //65 <== 21 
 
    (4.5 10 0.05) //66 <== 22 
    (5.5 10 0.05) //67 <== 23 
    (9.5 10 0.05) //68 <== 24 
    (13 10 0.05) //69 <== 25 
 
    (4.5 6.5 0.05) //70 <== 26 
    (5.5 6.5 0.05) //71 <== 27 
    (9.5 6.5 0.05) //72 <== 28 
    (13 6.5 0.05) //73 <== 29 
 
    (5.5 6.03 0.05) //74 <== 30 
    (9.5 6.03 0.05) //75 <== 31 
    (13 6.03 0.05) //76 <== 32 
 
    (5.5 5.97 0.05) //77 <== 33 
    (9.5 5.97 0.05) //78 <== 34 
    (13 5.97 0.05) //79 <== 35 
 
    (4.5 5.5 0.05) //80 <== 36 
    (5.5 5.5 0.05) //81 <== 37 
    (9.5 5.5 0.05) //82 <== 38 
    (13 5.5 0.05) //83 <== 39 
 
    (4.5 2 0.05) //84 <== 40 
    (5.5 2 0.05) //85 <== 41 
    (9.5 2 0.05) //86 <== 42 
    (13 2 0.05) //87 <== 43 
     
); 
 
blocks 
( 
    hex (0 1 40 21 44 45 84 65) (30 15 1) simpleGrading (1 1 1) //1 
    hex (1 2 41 40 45 46 85 84) (15 15 1) simpleGrading (1 1 1) //2 
    hex (2 3 42 41 46 47 86 85) (30 15 1) simpleGrading (1 1 1) //3 
    hex (3 4 43 42 47 48 87 86) (35 15 1) simpleGrading (1 1 1) //4 
    hex (4 5 6 43 48 49 50 87) (50 15 1) simpleGrading (10 1 1) //5 
 
    hex (43 6 7 39 87 50 51 83) (50 8 1) simpleGrading (10 1 1) //6 
    hex (42 43 39 38 86 87 83 82) (35 8 1) simpleGrading (1 1 1) //7 
    hex (41 42 38 37 85 86 82 81) (30 8 1) simpleGrading (1 1 1) //8 
    hex (40 41 37 36 84 85 81 80) (15 8 1) simpleGrading (1 1 1) //9 
    hex (21 40 36 20 65 84 80 64) (30 8 1) simpleGrading (1 1 1) //10 
 
    hex (20 36 26 19 64 80 70 63) (30 2 1) simpleGrading (1 1 1) //11 
    hex (37 38 34 33 81 82 78 77) (30 2 1) simpleGrading (1 1 1) //12 
    hex (38 39 35 34 82 83 79 78) (35 2 1) simpleGrading (1 1 1) //13 
    hex (39 7 8 35 83 51 52 79) (50 2 1) simpleGrading (10 1 1) //14 
    hex (35 8 9 32 79 52 53 76) (50 2 1) simpleGrading (10 1 1) //15 
    hex (34 35 32 31 78 79 76 75) (35 2 1) simpleGrading (1 1 1) //16 
    hex (30 31 28 27 74 75 72 71) (30 2 1) simpleGrading (1 1 1) //17 
    hex (31 32 29 28 75 76 73 72) (35 2 1) simpleGrading (1 1 1) //18 
    hex (32 9 10 29 76 53 54 73) (50 2 1) simpleGrading (10 1 1) //19 
 
    hex (29 10 11 25 73 54 55 69) (50 15 1) simpleGrading (10 1 1) //20 
    hex (28 29 25 24 72 73 69 68) (35 15 1) simpleGrading (1 1 1) //21 
    hex (27 28 24 23 71 72 68 67) (30 15 1) simpleGrading (1 1 1) //22 
    hex (26 27 23 22 70 71 67 66) (15 15 1) simpleGrading (1 1 1) //23 
    hex (19 26 22 18 63 70 66 62) (30 15 1) simpleGrading (1 1 1) //24 
 
    hex (18 22 16 17 62 66 60 61) (30 13 1) simpleGrading (1 1 1) //25 
    hex (22 23 15 16 66 67 59 60) (15 13 1) simpleGrading (1 1 1) //26 
    hex (23 24 14 15 67 68 58 59) (30 13 1) simpleGrading (1 1 1) //27 
    hex (24 25 13 14 68 69 57 58) (35 13 1) simpleGrading (1 1 1) //28 
    hex (25 11 12 13 69 55 56 57) (50 13 1) simpleGrading (10 1 1) //29 
     
    
); 
 
edges 
( 
); 
 
patches 
( 
 
    patch inlet //left 
        ( 
           (17 61 62 18)  
           (18 62 63 19)  
           (19 63 64 20)  
           (20 64 65 21) 
           (21 65 44 0) 
        ) 
 
    patch outlet //right    
        ( 
            (12 56 55 11)  
            (11 55 54 10)  
            (10 54 53 9)     
        (9 53 52 8)  
        (8 52 51 7)  
            (7 51 50 6) 
            (6 50 49 5) 
        ) 
    
 
    patch top //up    
        ( 
             
            (17 61 60 16) 
            (16 60 59 15) 
            (15 59 58 14) 
            (14 58 57 13) 
            (13 57 56 12) 
 
        )  
 
    patch bottom //down 
        ( 
 
            (0 44 45 1) 
            (1 45 46 2) 
            (2 46 47 3) 
            (3 47 48 4) 
            (4 48 49 5) 
 
        ) 
 
    patch cylinder //solid 
        ( 
            (26 70 71 27)    
            (27 71 74 30)   
            (33 77 81 37)    
            (37 81 80 36)    
            (36 80 70 26)  
        ) 
    
 
  patch plate //solid 
        ( 
            (30 74 75 31)    
            (31 75 78 34)    
            (34 78 77 33)  
        ) 
  
  empty frontAndBackPlanes //ahead behind 
        ( 
 
            (0 1 40 21) //Block 1 front 
            (1 2 41 40) //Block 2 front 
            (2 3 42 41) //Block 3 front 
            (3 4 43 42) //Block 4 front 
            (4 5 6 43) //Block 5 front 
            (43 6 7 39) //Block 6 front 
            (42 43 39 38) //Block 7 front 
            (41 42 38 37) //Block 8 front 
            (40 41 37 36) //Block 9 front 
            (21 40 36 20) //Block 10 front 
            (20 36 26 19) //Block 11 front 
            (37 38 34 33) //Block 12 front 
            (38 39 35 34) //Block 13 front 
            (39 7 8 35) //Block 14 front 
            (35 8 9 32) //Block 15 front 
            (34 35 32 31) //Block 16 front 
            (30 31 28 27) //Block 17 front 
            (31 32 29 28) //Block 18 front 
            (32 9 10 29) //Block 19 front 
            (29 10 11 25) //Block 20 front 
            (28 29 25 24) //Block 21 front 
            (27 28 24 23) //Block 22 front 
            (26 27 23 22) //Block 23 front 
            (19 26 22 18) //Block 24 front 
            (18 22 16 17) //Block 25 front 
            (22 23 15 16) //Block 26 front 
            (23 24 14 15) //Block 27 front 
            (24 25 13 14) //Block 28 front 
            (25 11 12 13) //Block 29 front 
 
            (44 45 84 65) //Block 1 back 
            (45 46 85 84) //Block 2 back 
            (46 47 86 85) //Block 3 back 
            (47 48 87 86) //Block 4 back 
            (48 49 50 87) //Block 5 back 
            (87 50 51 83) //Block 6 back 
            (86 87 83 82) //Block 7 back 
            (85 86 82 81) //Block 8 back 
            (84 85 81 80) //Block 9 back 
            (65 84 80 64) //Block 10 back 
            (64 80 70 63) //Block 11 back 
            (81 82 78 77) //Block 12 back 
            (82 83 79 78) //Block 13 back 
            (83 51 52 79) //Block 14 back 
            (79 52 53 76) //Block 15 back 
            (78 79 76 75) //Block 16 back 
            (74 75 72 71) //Block 17 back 
            (75 76 73 72) //Block 18 back 
            (76 53 54 73) //Block 19 back 
            (73 54 55 69) //Block 20 back 
            (72 73 69 68) //Block 21 back 
            (71 72 68 67) //Block 22 back 
            (70 71 67 66) //Block 23 back 
            (63 70 66 62) //Block 24 back 
            (62 66 60 61) //Block 25 back 
            (66 67 59 60) //Block 26 back 
            (67 68 58 59) //Block 27 back 
            (68 69 57 58) //Block 28 back 
            (69 55 56 57) //Block 29 back 
 
       ) 
); 
 
mergePatchPairs 
( 
); 
 
// ************************************************************************* //

Code:

/*--------------------------------*- C++ -*----------------------------------*\ 
| =========                 |                                                 | 
| \\      /  F ield         | OpenFOAM: The Open Source CFD Toolbox           | 
|  \\    /   O peration     | Version:  2.2.2                                 | 
|   \\  /    A nd           | Web:      www.OpenFOAM.org                      | 
|    \\/     M anipulation  |                                                 | 
\*---------------------------------------------------------------------------*/ 
FoamFile 
{ 
    version     2.0; 
    format      ascii; 
    class       dictionary; 
    object      blockMeshDict; 
} 
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // 
 
convertToMeters 1;//dimensions in meters --> conversion 1 
 
vertices 
( 
    (5.5 5.97 0) //0--19 
    (9.5 5.97 0) //1--20 
    (9.5 6.03 0) //2--22 
    (5.5 6.03 0) //3--21 
     
    (5.5 5.97 0.05) //4--45 
    (9.5 5.97 0.05) //5--46 
    (9.5 6.03 0.05) //6--48 
    (5.5 6.03 0.05) //7--47 
); 
 
blocks 
( 
    hex (0 1 2 3 4 5 6 7) (30 2 1) simpleGrading (1 1 1) //0 
); 
 
edges 
( 
); 
 
patches 
( 
     patch plateFix 
     ( 
         (3 7 4 0) 
     ) 
 
     patch plate 
     ( 
      (3 2 6 7) 
      (6 2 1 5) 
      (1 0 4 5) 
     ) 
 
     empty frontAndBackPlanes 
     ( 
     (0 1 2 3) 
     (7 6 5 4) 
     ) 
); 
 
mergePatchPairs 
( 
); 
 
// ************************************************************************* //

I knew that as one step to separate frontAndBackPlanes to frontPlane and backPlane.

5. If blockMesh isn't useful, what about snappyHexMesh? I never used it before. Any answer would be really grateful.

Thank you very much.

Maimouna

Woj3x · January 19, 2016, 10:16

Hi,
I use ICEM CFD for meshing so I can't help you in this but IMO this case isn't so hard, so you can easly handle this with blockMesh but it's gonna be time consuming (it's all depend on your experience with blockMesh).

Good option could be to analyze blockMeshDict file from case beamInCrossFlow (it's 3D case from fsiFOAM tutorials). It should be good place to start.

Best regards,
Wojciech

Woj3x · January 22, 2016, 13:12

Dear Maimouna,
Could you show me how your chart FD over time looks? how your chart drag forces from time it looks for the case of 2D? Because I'm not sure why this value is negative in my case. Thank you in advance!

Dear nctiwary,
Your case requires a lot of knowledge about this topic so I suppose it will be better for you to create
separate topic. Neverless I suppose that case: beamInCrossFlow could be good place to start. Good luck!

Best regards,
Wojciech

[Moderator note: nctiwary had asked in a ton of threads and all of nctiwary's posts were deleted due to not following the rules.]

Maimouna · January 23, 2016, 07:19

Hi Wojciech,

the attached pictures are showed FD with time in two different cases in 2D (same case with different parameters).

Kind regards

Maimouna

wyldckat · January 31, 2016, 12:15

Quick side note: There are a few GUIs for editing the "blockMeshDict" files. One example is this one: http://openfoamwiki.net/index.php/Contrib/SwiftBlock

For more details about blockMesh: https://openfoamwiki.net/index.php/BlockMesh

Woj3x · January 31, 2016, 12:45

Dear Bruno
Could you tell me why Drag force forom script hronTurekReport.C is negative?
I suppose that direction of this force should correspond to the direction of fluid flow.

Thank you in advance

Wojciech

wyldckat · January 31, 2016, 12:57

Greetings Wojciech,

Quote:

Originally Posted by Woj3x

Could you tell me why Drag force forom script hronTurekReport.C is negative?
I suppose that direction of this force should correspond to the direction of fluid flow.

Sorry, but what exactly are you referring to? I'm not familiar with the code itself, I only took care of re-adapting it to work on foam-extend 3.1. Therefore, please provide more specific details to both the code and what you are seeing.

Nonetheless, is the drag force showing you an opposite sign to the fluid flow?
If yes, then it's because it's the "drag force": https://en.wikipedia.org/wiki/Drag_%28physics%29 - and I quote:

Quote:

In fluid dynamics, drag [...] refers to forces acting opposite to the relative motion of any object moving with respect to a surrounding fluid.

Best regards,
Bruno

Maimouna · February 5, 2016, 11:30

Quote:

Originally Posted by wyldckat

Quick side note: There are a few GUIs for editing the "blockMeshDict" files. One example is this one: http://openfoamwiki.net/index.php/Contrib/SwiftBlock

For more details about blockMesh: https://openfoamwiki.net/index.php/BlockMesh

Dear Bruno,

I started learning swiftBlock, but that is not easy to understand in few days. I spent days to understand but I found it so hard.

. Sorry, my technical experience and information so poor.

Are there any other easy way instead? Any way to change 2D case to 3D case?

I never stopped, I'm trying with gmsh, hopefully it will work. But, another question regarding this,
How is Allrun file will be looked after gmsh. Allrun is shown below

Code:

#!/bin/sh

# Source tutorial run functions
. $WM_PROJECT_DIR/bin/tools/RunFunctions

# Get application name
application=`getApplication`

runApplication -l log.blockMesh.solid blockMesh -region solid
runApplication -l log.setSet.solid setSet -case ../solid -batch ../solid/setBatch
runApplication -l log.setToZones.solid setsToZones -case ../solid -noFlipMap

runApplication blockMesh
runApplication setSet -batch setBatch
runApplication setsToZones -noFlipMap

# Build hronTurekReport function object
wmake libso ../hronTurekReport

runApplication $application

# ----------------------------------------------------------------- end-of-file

My deadline is being too close

, I need your help please to find my case results.

Many thanks.

Maimouna

Maimouna · February 18, 2016, 11:14

Dear Bruno and others,

I need your help again please, I'm doing 3d beam cantilever case (picture attached). I followed case ''beamInCrossFlow'' case to implement my case (attached). The meshing and running the solid part is ok, he proplem I faced with the fluid part. I think their is something problem in ''interface'' meshing because I got this error message in the log file

Code:

--> FOAM FATAL ERROR: 
Solid face zone name interface-zone not found.  Please check your face zone definition.

    From function 
    in file fluidStructureInterface/fluidStructureInterface.C at line 737.

FOAM aborting

Aborted (core dumped)

Or it could be with cylinder because checkMesh utility gives error too. I couldn't able to determine where is the exact error. I did for about 5 different blockMeshDict files, but unfortunately, non of them would able to run in my solver. Could you please have a look to my case and try to run it for me might you could determine where is the problem. I'm really struggling and need some help. the meshing way is attached as well to have a look. Let me know please if the method is correct, this is following ''beamInCrossFlow'' tutorial case.

Lots of thanks in advanced and regards.

Maimouna

Woj3x · February 18, 2016, 11:32

Dear Maimouna,
In file setBatch you can define name for FSI interface. In your file FSI interface is called "plate" so fsiFOAM is trying to find boundary "plate". You need to correct this (change setBatch or name in your BC).
I also have a few problems with this solver so I don't have time to test your case sorry but I hope that this will help you.

Best regards,
Wojciech

Maimouna · February 18, 2016, 12:12

Dear Wojciech,

thanks for your quick replay. I already did what you suggested, may be I attached wrong setBatch file with the case. The correct one is

Code:

faceSet interfaceZone new patchToFace interface
quit

but my confusing still with the blockMesh, since checkMesh utility gives me error

Code:

/*---------------------------------------------------------------------------*\
| =========                 |                                                 |
| \\      /  F ield         | foam-extend: Open Source CFD                    |
|  \\    /   O peration     | Version:     3.1                                |
|   \\  /    A nd           | Web:         http://www.extend-project.de       |
|    \\/     M anipulation  |                                                 |
\*---------------------------------------------------------------------------*/
Build    : 3.1-f61aab88e799
Exec     : checkMesh
Date     : Feb 18 2016
Time     : 17:00:36
Host     : owner-HP-Pavilion-Sleekbook-15-PC
PID      : 4743
CtrlDict : /home/owner/foam/foam-extend-3.1/etc/controlDict
Case     : /home/owner/foam/owner-3.1/FluidStructureInteraction/run/fsiFoam/3dBeamInCrossFlow/fluid
nProcs   : 1
SigFpe   : Enabling floating point exception trapping (FOAM_SIGFPE).

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create polyMesh for time = 0

Time = 0

Mesh stats
    all points:           28230
    live points:          28230
    all faces:            76976
    live faces:           76976
    internal faces:       69024
    cells:                24448
    boundary patches:     9
    point zones:          0
    face zones:           0
    cell zones:           0

Overall number of cells of each type:
    hexahedra:     23760
    prisms:        688
    wedges:        0
    pyramids:      0
    tet wedges:    0
    tetrahedra:    0
    polyhedra:     0

Checking topology...
    Boundary definition OK.
    Point usage OK.
    Upper triangular ordering OK.
    Face vertices OK.
    Number of regions: 1 (OK).

Checking patch topology for multiply connected surfaces ...
    Patch               Faces    Points   Area [m^2]  Surface topology                  
    top                 0        0        0           ok (empty)                        
    bottom              688      783      220         ok (non-closed singly connected)  
    outlet              320      361      104.5       ok (non-closed singly connected)  
    inlet               256      289      104.5       ok (non-closed singly connected)  
    cylinder            512      578      8           ok (non-closed singly connected)  
    interface           320      369      121         ok (non-closed singly connected)  
    back                2800     2974     204         ok (non-closed singly connected)  
    frontPlane          2800     2974     372.035     ok (non-closed singly connected)  
    defaultFaces        256      297      55          ok (non-closed singly connected)  

Checking geometry...
    This is a 2-D mesh
    Overall domain bounding box (0 0 0) (20 11 11)
    Mesh (non-empty, non-wedge) directions (0 1 1)
    Mesh (non-empty) directions (0 1 1)
    Mesh (non-empty, non-wedge) dimensions 2
    All edges aligned with or perpendicular to non-empty directions.
    Boundary openness (0 1.46407e-16 3.14327e-15) Threshold = 1e-06 OK.
 ***High aspect ratio cells found, Max aspect ratio: 4.6875e+09, number of cells 24448 Threshold = 1000
  Writing 24448 cells with high aspect ratio to set highAspectRatioCells
    Minumum face area = 0.0078125. Maximum face area = 0.6875.  Face area magnitudes OK.
 ***Zero or negative cell volume detected.  Minimum negative volume: -0.214844, Number of negative volume cells: 24448
  Writing 24448 zero volume cells to set zeroVolumeCells
    Mesh non-orthogonality Max: 180 average: 158.784 Threshold = 70
 ***Number of non-orthogonality errors: 69024.
  Writing 69024 non-orthogonal faces to set nonOrthoFaces
 ***Error in face pyramids: 146000 faces are incorrectly oriented.
  Writing 76976 faces with incorrect orientation to set wrongOrientedFaces
    Max skewness = 0.851667 OK.

Failed 4 mesh checks.

End

I just want you to check my meshing way (picture attached) if what I'm doing is correct or not. Sorry for asking to give some time to check my mesh please. That would be really appreciated.

Kind regards

Maimouna

Maimouna · February 22, 2016, 11:26

Hi all,

the blockMesh and checkMesh utilities for both fluid and solid are ok, but the problem in the log file still the same

Code:

/*---------------------------------------------------------------------------*\
| =========                 |                                                 |
| \\      /  F ield         | foam-extend: Open Source CFD                    |
|  \\    /   O peration     | Version:     3.1                                |
|   \\  /    A nd           | Web:         http://www.extend-project.de       |
|    \\/     M anipulation  |                                                 |
\*---------------------------------------------------------------------------*/
Build    : 3.1-f61aab88e799
Exec     : fsiFoam
Date     : Feb 22 2016
Time     : 16:06:41
Host     : owner-HP-Pavilion-Sleekbook-15-PC
PID      : 7801
CtrlDict : /home/owner/foam/foam-extend-3.1/etc/controlDict
Case     : /home/owner/foam/owner-3.1/FluidStructureInteraction/run/fsiFoam/3dBeamInCrossFlow/fluid
nProcs   : 1
SigFpe   : Enabling floating point exception trapping (FOAM_SIGFPE).

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create dynamic mesh for time = 0

Selecting dynamicFvMesh dynamicMotionSolverFvMesh
Selecting motion solver: velocityLaplacian
Selecting motion diffusion: quadratic
Selecting motion diffusion: inverseDistance
 Reading stress mesh
Creating fixed displacement boundary condition
Creating traction displacement boundary conditions
Creating fixed displacement boundary condition
Selecting rheology model linearElastic
Creating constitutive model


--> FOAM FATAL ERROR: 
Solid face zone name interface-zone not found.  Please check your face zone definition.

    From function 
    in file fluidStructureInterface/fluidStructureInterface.C at line 737.

FOAM aborting

Aborted (core dumped)

even I checked every single file in the attached case, the error still the same. Any help please.

Lots of thanks in advanced and regards.

Maimouna

Woj3x · February 22, 2016, 12:37

Dear Maimouna,

In solid setBatch looks:

Quote:

faceSet plateZone new patchToFace plate
quit

In solid setBatch looks:

Quote:

faceSet interfaceZone new patchToFace interface
quit

I see that in fluid/constant/polymesh/blockMeshDict you use name interface, so IMO you need to change this for plate.
I am also not sure if in this solver both FSI interfaces don't needs to have same name.

Best regards,
Wojciech

Maimouna · February 23, 2016, 05:17

Hi Wojciech,

I already changed the interface-zone name in both setBatch files as

Code:

faceSet interfaceZone new patchToFace interface
quit

I think the error given is related to something else. Could you please take some time to have a look in my case please.

Kind regards

Maimouna

Woj3x · February 23, 2016, 07:14

Hi Maimouna,
I suppose that I found file with problem.

In fluid/constant/fsiProperties you've got:

Quote:

solidPatch interface;
solidZone interface-zone;
fluidPatch interface;
fluidZone interface-zone;

So IMO you need to change name "interface-zone" for "interfaceZone" (name form setBatch) in this file. Sorry but I don't have time to check this closer (I work on my own thesis).

Best regards,
Wojciech

Maimouna · February 23, 2016, 14:23

Many thanks Wojciech, you are right, I was silly with that error

, it is solved now. But there is another one needs to sort out

Code:

--> FOAM FATAL ERROR: 
Master point addressing is not correct

I will chick what I was going again. If you get some time to have a look please try and let me know. I understand that you are busy with your thesis, but do your best please to have a look, would be cheeky to ask that again.

Regarding your request about tetFemSolution, I don't know more than than it used for moving mesh because the motion solver is FEM and the flow solver is FVM. Since motionU is a tetFem field, the number of boundary locations is be different and mapping is required. I saved that from some time ago in my note and I used it for every moving mesh solver. I hope that would help.

Kind regards

Maimouna

Maimouna · February 26, 2016, 12:01

Hi All,

have a good day. Any idea please to solve the the last error posted in #57. What's the problem? Any answer would be really appreciated.

Best regards

Maimouna

Woj3x · February 26, 2016, 17:27

Hi Maimouna,

I didn't have problem like this so I have no idea how to fix this. I would consider to make this case again.
You've done a lot of changes in this case when you used trial and error method to solve problems and you could accidentally create this error.
Isn't in log.fsiFoam any additional information about this error?

Best regards,
Wojciech

Woj3x · March 8, 2016, 19:13

Hi all,

Maimouna, did you solve this problem?
I've got same one right now:

Quote:

Create extended GGI zone-to-zone interpolator
Checking fluid-to-solid face interpolator
Fluid-to-solid face interpolation error: 0.000339184
Checking solid-to-fluid point interpolator (GGI)
Extended GGI, master point distance, max: 1e+15, avg: 7.21732e+12, min: -0.00035
Extended GGI, master point orientation (<0), max: 1, min: -1, nIncorrectPoints: 1198/4988

--> FOAM FATAL ERROR:
Master point addressing is not correct

From function ExtendedGGIInterpolation::masterToSlavePointInterp olate(const Field<Type> pf)
in file ./numerics/ggi/ExtendedGGIInterpolation/ExtendedGGIInterpolation.C at line 703.

FOAM aborting

Aborted (core dumped)

Is it connected with my geometry? How can I find and fix a wrong parts of the geometry
Thank you in advance

Best regards,
Wojciech

January 22, 2016, 13:12		#44
Woj3x New Member Wojciech Gołąbek Join Date: Dec 2013 Posts: 29 Rep Power: 12	Dear Maimouna, Could you show me how your chart FD over time looks? how your chart drag forces from time it looks for the case of 2D? Because I'm not sure why this value is negative in my case. Thank you in advance! Dear nctiwary, Your case requires a lot of knowledge about this topic so I suppose it will be better for you to create separate topic. Neverless I suppose that case: beamInCrossFlow could be good place to start. Good luck! Best regards, Wojciech [Moderator note: nctiwary had asked in a ton of threads and all of nctiwary's posts were deleted due to not following the rules.] Last edited by wyldckat; January 31, 2016 at 12:12. Reason: added moderator note

February 26, 2016, 17:27		#59
Woj3x New Member Wojciech Gołąbek Join Date: Dec 2013 Posts: 29 Rep Power: 12	Hi Maimouna, I didn't have problem like this so I have no idea how to fix this. I would consider to make this case again. You've done a lot of changes in this case when you used trial and error method to solve problems and you could accidentally create this error. Isn't in log.fsiFoam any additional information about this error? Best regards, Wojciech Last edited by Woj3x; February 26, 2016 at 18:55.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Other] mesh airfoil NACA0012	anand_30	OpenFOAM Meshing & Mesh Conversion	13	March 7, 2022 17:22
[blockMesh] error message with modeling a cube with a hold at the center	hsingtzu	OpenFOAM Meshing & Mesh Conversion	2	March 14, 2012 09:56
[blockMesh] BlockMesh FOAM warning	gaottino	OpenFOAM Meshing & Mesh Conversion	7	July 19, 2010 14:11
[blockMesh] Axisymmetrical mesh	Rasmus Gjesing (Gjesing)	OpenFOAM Meshing & Mesh Conversion	10	April 2, 2007 14:00
[Gmsh] Import gmsh msh to Foam	adorean	OpenFOAM Meshing & Mesh Conversion	24	April 27, 2005 08:19

January 19, 2016, 10:16		#43
Woj3x New Member Wojciech Gołąbek Join Date: Dec 2013 Posts: 29 Rep Power: 12	Hi, I use ICEM CFD for meshing so I can't help you in this but IMO this case isn't so hard, so you can easly handle this with blockMesh but it's gonna be time consuming (it's all depend on your experience with blockMesh). Good option could be to analyze blockMeshDict file from case beamInCrossFlow (it's 3D case from fsiFOAM tutorials). It should be good place to start. Best regards, Wojciech

January 31, 2016, 12:15		#46
wyldckat Retired Super Moderator Bruno Santos Join Date: Mar 2009 Location: Lisbon, Portugal Posts: 10,975 Blog Entries: 45 Rep Power: 128	Quick side note: There are a few GUIs for editing the "blockMeshDict" files. One example is this one: http://openfoamwiki.net/index.php/Contrib/SwiftBlock For more details about blockMesh: https://openfoamwiki.net/index.php/BlockMesh

January 31, 2016, 12:45		#47
Woj3x New Member Wojciech Gołąbek Join Date: Dec 2013 Posts: 29 Rep Power: 12	Dear Bruno Could you tell me why Drag force forom script hronTurekReport.C is negative? I suppose that direction of this force should correspond to the direction of fluid flow. Thank you in advance Wojciech

February 18, 2016, 11:32		#51
Woj3x New Member Wojciech Gołąbek Join Date: Dec 2013 Posts: 29 Rep Power: 12	Dear Maimouna, In file setBatch you can define name for FSI interface. In your file FSI interface is called "plate" so fsiFOAM is trying to find boundary "plate". You need to correct this (change setBatch or name in your BC). I also have a few problems with this solver so I don't have time to test your case sorry but I hope that this will help you. Best regards, Wojciech

February 23, 2016, 05:17		#55
Maimouna Senior Member ok Join Date: Oct 2013 Posts: 346 Rep Power: 13	Hi Wojciech, I already changed the interface-zone name in both setBatch files as Code: faceSet interfaceZone new patchToFace interface quit I think the error given is related to something else. Could you please take some time to have a look in my case please. Kind regards Maimouna

February 23, 2016, 14:23		#57
Maimouna Senior Member ok Join Date: Oct 2013 Posts: 346 Rep Power: 13	Many thanks Wojciech, you are right, I was silly with that error, it is solved now. But there is another one needs to sort out Code: --> FOAM FATAL ERROR: Master point addressing is not correct I will chick what I was going again. If you get some time to have a look please try and let me know. I understand that you are busy with your thesis, but do your best please to have a look, would be cheeky to ask that again. Regarding your request about tetFemSolution, I don't know more than than it used for moving mesh because the motion solver is FEM and the flow solver is FVM. Since motionU is a tetFem field, the number of boundary locations is be different and mapping is required. I saved that from some time ago in my note and I used it for every moving mesh solver. I hope that would help. Kind regards Maimouna

February 26, 2016, 12:01		#58
Maimouna Senior Member ok Join Date: Oct 2013 Posts: 346 Rep Power: 13	Hi All, have a good day. Any idea please to solve the the last error posted in #57. What's the problem? Any answer would be really appreciated. Best regards Maimouna