[katakgoreng]

Originally Posted by ngj

Good morning Hao,

To me, it sounds as if there are problems with the sampling utilities on 2.3 (and perhaps even above?). Could you please perform the following couple of tests:

1. Test whether the problem persists on static meshes, e.g. make a dambreak onto your cylinder with and without the surfaceElevation utility.

2. Perform your test case with line sampling instead of surfaceElevation. surfaceElevation is derived from the sampling utility in version 1.6 (if I remember correctly), so there could be some discrepancies.

If the problem still persists for '2', it suggests that there is a problem with multiple sampling in 2.3+ and that it is not related to surfaceElevation itself.

Good luck,

Niels

P.S. Rafa, thank you for the feed-back.

Hi Niels,

In regards of the sampling utilities, I have issue when sampling the surface elevation for negative times in which the sampling (done as post processing step using surfaceElevationDict) only occur from t=0s and disregard the negative time value.

There is no issue if the sampling is done as run-time post-processing. I have attached the case file & hope you can have a look at them. I'm using Openfoam 2.2.2 on Xubuntu 14.04.

[ngj]

Hallo,

I do not have such an old version available, but have you tried the following?

surfaceElevation -time -1:

Perhaps, it is simply the time-selection routine that does not consider negative values by default. At least, I do not think that it originated from waves2Foam itself.

Kind regards,

Niels

[katakgoreng]

Originally Posted by ngj

Hallo,

I do not have such an old version available, but have you tried the following?

surfaceElevation -time -1:

Perhaps, it is simply the time-selection routine that does not consider negative values by default. At least, I do not think that it originated from waves2Foam itself.

Kind regards,

Niels

Many thanks. I have tried specifying "surfaceElevation -time -1:" but still got the same problem. I've also tried using openfoam 2.3.0, but the problem is still there. I guess it is due to time-selection routine then.