sample utility stuck at non-continuous domain
 

Hello World,

I have a 3D interFoam case, which - roughly drawn - looks like the black geometry in this picture:

http://www.cfd-online.com/Forums/att...chmentid=40491

Now I want to find the water surface, and since the cases already run I wanted to use the sample utility. However, it seems that it cannot deal with non-continuous domains. I tried to methods:

1. Line(s): Multiple lines (example see below) defined over the height of the domain and distributed equally over the width (shown in the blue dashed lines).
   What happens here is that I get a full set of data for both left lines, while the center line, in which a part of the domain has been cut out, I only get data below the missing domain (green), not abve (red).
   
   
   Code:

   ---

   line1
    {
        type      uniform;
        axis      distance;
       
        start      (-0.300 0.0010 0.0000);
        end        (-0.300 0.0010 0.200);
        nPoints    100;
    }

   ---

2. Surface: I defined a surface to be sample (see below) which should sample the geometry regularly (probably based on cell position).
   The result in this case is basically the same as above. It also appears to be irrelevant wheter the basePoint or coordinate origin is above or below the cut out part (x in picture).
   
   
   Code:

   ---

   interpolatedPlane
    {
        type            plane;
        coordinateSystem
        {
            origin      (0 0 0.08);
           
            coordinateRotation
            {
                type    axesRotation;
                e1      (1 0 0);
                e2      (0 1 0);
            }
        }

        basePoint      (0 0 0);
        normalVector    (0 1 0);
        interpolate    true;
    }

   ---

Now I could probably use the line approach and shift the beginning of the line higher, but hat would still require me to evaluate a few dozen lines, which is tedious.

So I wondered...

• if anyone has encountered this problem before and found a solution
• if this should be considered a bug (then I'll report) or if there is a logical reason for this that I don't see.

If anyone wants a case file I could probably provide a similar on, I just cannot publish the current case Im working on.