[IHFOAM Team]

Hi Maoyanjun,

If you are not using IHFOAM...

Originally Posted by Maoyanjun

hi foamers:
I am using the WaveMaker piston type boundary in the OLAFoam to

...you should post it in the correct thread, not in the IHFOAM Thread.

Best Regards,
IHFOAM Team

[Maoyanjun]

Originally Posted by IHFOAM Team

Hi Maoyanjun,

If you are not using IHFOAM...

...you should post it in the correct thread, not in the IHFOAM Thread.

Best Regards,
IHFOAM Team

I am sorry for that I thought the OLAFoam and IHFOAM are the same solvers for ocean engineering.So I post it here. I will post it to the olaFoam thread.

[IHFOAM Team]

Hi Maoyanjun,

No need to apologize.

Originally Posted by Maoyanjun

I thought the OLAFoam and IHFOAM are the same solvers for ocean engineering.

I would like to clearly point out the diffferences: OLAFoam is just a crude imitation of IHFOAM-v1.0 by someone who claims to be the unique developer of IHFOAM.

Nowadays, IHFOAM-V2.0 is fully integrated in OpenFOAM-v1612+ and OpenFOAM-v1706, thanks to an agreement (2016) betwen IHCantabria and ESI-Group.


Free surface time history of a cnoidal wave. Dashed red line: IHFOAM-v1.0 (release 2014). Dotted green line: Theoretical solution. Black solid line: IHFOAM-v2.0 (OpenFOAM® release v1706).

You can find more info in the web site:
http://ihfoam.ihcantabria.com

[cfd_hchen]

Hi,

I just found that the irregular wave in IHFOAM in v1706 was removed, if I remember correctly, it was available in previous versions. Is there any explaination on this issue?

Originally Posted by IHFOAM Team

Hi Maoyanjun,

No need to apologize.



I would like to clearly point out the diffferences: OLAFoam is just a crude imitation of IHFOAM-v1.0 by someone who claims to be the unique developer of IHFOAM.

Nowadays, IHFOAM-V2.0 is fully integrated in OpenFOAM-v1612+ and OpenFOAM-v1706, thanks to an agreement (2016) betwen IHCantabria and ESI-Group.


Free surface time history of a cnoidal wave. Dashed red line: IHFOAM-v1.0 (release 2014). Dotted green line: Theoretical solution. Black solid line: IHFOAM-v2.0 (OpenFOAM® release v1706).

You can find more info in the web site:
http://ihfoam.ihcantabria.com

[IHFOAM Team]

Hi Hao

Originally Posted by cfd_hchen

irregular wave in IHFOAM in v1706 was removed

Yes, indeed!!

Originally Posted by cfd_hchen

s there any explaination on this issue?

We are currently working in a bunch of new boundary conditions to be released in the near future, and a newer version of irregular waves will be one of those.

[cfd_hchen]

Hi,

Thanks a lot for your reply!

I am recently also working on oblique uni-directional and multi-directional waves. So this is actually the first time for me to use more than one wave paddle. It seems that I got some stability issues.

So I am just wondering usually how many wave paddles shall I choose for multi-directional waves for the inlet and outlet? As far as I remember, there was some different options on 2D and 3D wave absorption in the original version. Are they now merged into one boundary condition in OpenFOAM v1706?

Best regards
Hao

Originally Posted by IHFOAM Team

Hi Hao



Yes, indeed!!



We are currently working in a bunch of new boundary conditions to be released in the near future, and a newer version of irregular waves will be one of those.

[IHFOAM Team]

HI Hao,

So I am just wondering usually how many wave paddles shall I choose for multi-directional waves for the inlet and outlet? As far as I remember, there was some different options on 2D and 3D wave absorption in the original version. Are they now merged into one boundary condition in OpenFOAM v1706?

Yes, if you look at the tutorials, in your case in version v1706, for example: ~/OpenFOAM-v1706/tutorials/multiphase/interFoam/laminar/waveExampleStokesII

and you look into: constant/waveProperties, you will find a parameter called nPaddle. This is the number of paddles that you want to divide a particular patch.

You can put any number, but of course, we recommend you to split the patch in paddles of the same size.

[cfd_hchen]

Hi,

Thanks a lot for your kind reply.

But regarding the absorption of waves, I am just wondering that the current shallowWaterAbsorption condition is based on 2D or 3D theory? I mean does it estimate a wave angle and mainly absorb waves in that angle? Is it beneficial to assign more paddles on the absorption boundary?

Best regards
Hao

Originally Posted by IHFOAM Team

HI Hao,

Yes, if you look at the tutorials, in your case in version v1706, for example: ~/OpenFOAM-v1706/tutorials/multiphase/interFoam/laminar/waveExampleStokesII

and you look into: constant/waveProperties, you will find a parameter called nPaddle. This is the number of paddles that you want to divide a particular patch.

You can put any number, but of course, we recommend you to split the patch in paddles of the same size.

[IHFOAM Team]

Hi Hao,

Yes, it is based on a 2d theory, therefore we can just absorb the incoming waves perpendicular to the patch.

By adding several paddles, we can minimize the 3d effects, but we will never be able to absorb the waves that are tangencial to the patch. Nevertheless, the results are very accurate.

Note that if you increase your number of paddles, you will increase the computational cost too.

Best Regards.

[IHFOAM Team]

Hi,

We are very happy to announce that you can find the multi-directional irregular waves boundary condition in OpenFOAM v1816 release:

https://www.openfoam.com/releases/op...ave-generation







Best Regards,
IHFOAM Team

[Ramsay]

Hi, I have newly installed IHFOAM and I am trying to run the first example, /genAbs

However, I get the below error. Can anybody please help me with this?

wmake libso waveGeneration
wmakeLnInclude: linking include files to ./lnInclude
Making dependency list for source file IH_Waves_InletVelocityFvPatchVectorField.C
Making dependency list for source file IH_Waves_InletAlphaFvPatchScalarField.C
g++ -std=c++11 -m64 -Dlinux64 -DWM_ARCH_OPTION=64 -DWM_DP -DWM_LABEL_SIZE=32 -Wall -Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter -Wno-invalid-offsetof -Wno-attributes -O3 -DNoRepository -ftemplate-depth-100 -DOFVERSION=60 -I/opt/openfoam6/src/finiteVolume/lnInclude -I./IH_Waves_InletVelocity/velProfiles -I../common -I../common/checks -I../common/calculateWaterLevel -IlnInclude -I. -I/opt/openfoam6/src/OpenFOAM/lnInclude -I/opt/openfoam6/src/OSspecific/POSIX/lnInclude -fPIC -c IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C -o Make/linux64GccDPInt32Opt/IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.o
In file included from IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.H:277:0,
from IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C:47:
../common/memberFun.H: In member function ‘Foam::scalar Foam::IH_Waves_InletAlphaFvPatchScalarField::PI()’ :
../common/memberFun.H:7:35: error: ‘mathematicalConstant’ has not been declared
const scalar PI = mathematicalConstant:i;
^~~~~~~~~~~~~~~~~~~~
IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C: In member function ‘virtual void Foam::IH_Waves_InletAlphaFvPatchScalarField::updat eCoeffs()’:
IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C:340:26: error: ‘dimensionedInternalField’ was not declared in this scope
const fvMesh& mesh = dimensionedInternalField().mesh();
^~~~~~~~~~~~~~~~~~~~~~~~
IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C:340:26: note: suggested alternative: ‘DimensionedScalarField_H’
const fvMesh& mesh = dimensionedInternalField().mesh();
^~~~~~~~~~~~~~~~~~~~~~~~
DimensionedScalarField_H
IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C:316:12: warning: unused variable ‘auxiliarSolit’ [-Wunused-variable]
scalar auxiliarSolit = 0;
^~~~~~~~~~~~~
IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C:319:12: warning: unused variable ‘Csolitary’ [-Wunused-variable]
scalar Csolitary = 0;
^~~~~~~~~
IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C:320:12: warning: unused variable ‘ts’ [-Wunused-variable]
scalar ts = 0;
^~
IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C:321:12: warning: unused variable ‘Xa’ [-Wunused-variable]
scalar Xa = 0;
^~
IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.C:361:18: warning: unused variable ‘g’ [-Wunused-variable]
const scalar g = 9.81;
^
/opt/openfoam6/wmake/rules/General/transform:25: recipe for target 'Make/linux64GccDPInt32Opt/IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.o' failed
make: *** [Make/linux64GccDPInt32Opt/IH_Waves_InletAlpha/IH_Waves_InletAlphaFvPatchScalarField.o] Error 1
\n\nWave generation boundary conditions compilation failed

[vince_44]

Hi Foamers,


I use ihFoam included in OpenFOAM v1806.



My test case is a ship hull (70m), V=0m/s, H=5.5m T=5.5s.



The calculation work well but when I analyse the results, the wave generation seem to stop a as you can see on the roll movement graph. It's confirmed by paraFoam display.



I joins my wavesProperties file.



Can you help me to understand this problem?


Thanks

[IHFOAM Team]

Hi Ramsay,

Originally Posted by Ramsay

Hi, I have newly installed IHFOAM and I am trying to run the first example, /genAbs

However, I get the below error. Can anybody please help me with this?

Can yo give us more details about the OpenFOAM version that you are using?

IHFOAM Team.

[IHFOAM Team]

Hi vince_44,

Originally Posted by vince_44

I use ihFoam included in OpenFOAM v1806.

The calculation work well but when I analyse the results, the wave generation seem to stop a as you can see on the roll movement graph. It's confirmed by paraFoam display.

Can you help me to understand this problem?

Can you give us any more information about the domain, the numerical mesh, etc?


IHFOAM Team

[vince_44]

Hi


Here you can find an image with the domain. The mesh have around 5,7 millions of cells, refined around the free surface.



More I join dynamicMeshDic file, U and alpha files and fvSchemes file.


Best regard

[Ramsay]

Originally Posted by IHFOAM Team

Hi Ramsay,



Can yo give us more details about the OpenFOAM version that you are using?

IHFOAM Team.

Hi,

I am using OpenFoam 6 and I have just downloaded IHFOAM tutorials and solvers and according to the manual I am trying to solve the "genAbs" model.

Thanks

[IHFOAM Team]

Hi Ramsay,

Originally Posted by Ramsay

I am using OpenFoam 6

IHFOAM will not work with OpenFOAM-6 unless you adapt the code.


But, you might find much easier to use OpenFOAM-v1806 in which IHFOAM will work straighforward.


Best Regards,
IHFOAM Team.

[Ramsay]

Originally Posted by IHFOAM Team

Hi Ramsay,



IHFOAM will not work with OpenFOAM-6 unless you adapt the code.


But, you might find much easier to use OpenFOAM-v1806 in which IHFOAM will work straighforward.


Best Regards,
IHFOAM Team.

Thanks a lot. I started using it and it seems that you use the "boussinesq" name for the solitary wave model.

[IHFOAM Team]

Hi Ramsay,

You can find three theories and three tutorials, related to solitary waves:

- waveExampleSolitary (Boussinesq)
- waveExampleSolitaryGrimshaw (Grimshaw)
- waveExampleSolitaryMcCowan (McCowan)

Regards,
IHFOAM Team

[Ramsay]

Hi,

I am a new IHFOAM user and I am trying to verify the solitary wave profile in OpenFOAM 1806 and also plot it in a file. I am trying to use the code provided by the openfoam.org in their tutorials which is like:

functions
{
interfaceHeight1
{
type interfaceHeight;
libs ("libfieldFunctionObjects.so");
locations ((300 0 0) (450 0 0) (600 0 0));
alpha alpha.water;
}
}

However, I cannot get any outputs when I implement this code in solitary wave example of OF 1806. Does anyone have any recommendation on how to get the free surface elevation of solitary waves in OpenFOAM 1806.

P.S. There are no interfaceHeight.c and .h files in OpenFOAM 1806