[Mojtaba.a]

Hi,
I am using simpleFunctionObject to average some fields in volume. I can do this for simple filelds like T. for instance I add the following code into controlDict file:

functions
(
temp_average
{
type volumeAverage;
functionObjectLibs
(
"libsimpleFunctionObjects.so"
);
verbose true;
fields (T);
}
);

But I don't know how to to do this for total velocity magnitude. When I use U instead of T in above code, I get average volume of velocity vector. I need average velocity magnitude.
How can I do that? any suggestions?

[gschaider]

Originally Posted by Mojtaba.a

Hi,
I am using simpleFunctionObject to average some fields in volume. I can do this for simple filelds like T. for instance I add the following code into controlDict file:

But I don't know how to to do this for total velocity magnitude. When I use U instead of T in above code, I get average volume of velocity vector. I need average velocity magnitude.
How can I do that? any suggestions?

With the big brother of the simpleFunctionObjects: swak4Foam. Something like:

functions
{
  velAverage
  {
     type swakExpression;
     functionObjectLibs
     (
       "libsimpleSwakFunctionObjects.so"
     );
     verbose true;
     variables (
        "totalV=sum(vol());"
     );
     expression "vol()*mag(U)/totalV";
     accumulations (
        sum
     );
}
);

That would be the volume-weighted average.

An alternative would be to construct a separate field:

functions
{
    makeMagU {
       type expressionField;
         functionObjectLibs
        (
            "libswakFunctionObjects.so"
        );      autowrite false;
       fieldName magU;
       expression "mag(U)";
    }
    temp_average
    {
        type volumeAverage;
        functionObjectLibs
        (
            "libsimpleFunctionObjects.so"
        );
        verbose true;
        fields (magU);
    }
}

[Mojtaba.a]

Hi Bernhard and thanks for your useful answer. there is problem I have while running my case. When I use your second code in controlDict File, I get the following error message in openFOAM:

--> FOAM Warning :
From function dlLibraryTable:pen(const fileName&, const bool)
in file db/dynamicLibrary/dlLibraryTable/dlLibraryTable.C at line 96
could not load "libswakFunctionObjects.so"
--> FOAM Warning :
From function dlLibraryTable:pen(const dictionary&, const word&, const TablePtr&)
in file lnInclude/dlLibraryTableTemplates.C at line 67
Could not open library "libswakFunctionObjects.so"



--> FOAM FATAL ERROR:
Unknown function type expressionField

Valid functions are :

23
(
executeIfEnvironmentVariable
executeIfExecutableFits
executeIfFunctionObjectPresent
executeIfObjectExists
functionObjectListProxy
initSwakFunctionObject
panicDump
patchAverage
patchFieldFlow
patchIntegrate
patchMassFlow
patchMassFlowAverage
patchProbes
probes
readGravitation
sets
surfaces
trackDictionary
volumeAverage
volumeIntegrate
volumeMinMax
writeAdditionalFields
writeFieldsOften
)



From function functionObject::New(const word& name, const Time&, const dictionary&)
in file db/functionObjects/functionObject/functionObject.C at line 89.

FOAM exiting

and when I use your first code I get the following error:

--> FOAM FATAL IO ERROR:
keyword valueType is undefined in dictionary "::vel_average"

file: ::vel_average from line 65 to line 77.

From function dictionary::lookupEntry(const word&, bool, bool) const
in file db/dictionary/dictionary.C at line 400.

FOAM exiting

I have compiled swak4Foam without any error (maybe just some warnings), can you please help me in this manner?

[gschaider]

Sorry. I should have said that I wrote the examples without testing them:

Originally Posted by Mojtaba.a

Hi Bernhard and thanks for your useful answer. there is problem I have while running my case. When I use your second code in controlDict File, I get the following error message in openFOAM:

I expected a typo in the library but I can't find it. Check with

ls $FOAM_USER_LIBBIN/libswakFunctionObjects.so

if it really exists.

Originally Posted by Mojtaba.a

and when I use your first code I get the following error:


I have compiled swak4Foam without any error (maybe just some warnings), can you please help me in this manner?

This one is easy. Forgot

valueType internalField;

BTW: this is generally applicable for working with OpenFOAM: if it is complaining about a missing entry then add that entry (in this case valueType) and then use the "banana trick": http://openfoamwiki.net/index.php/Op...de/Use_bananas

[Mojtaba.a]

Originally Posted by gschaider

Sorry. I should have said that I wrote the examples without testing them:


I expected a typo in the library but I can't find it. Check with

ls $FOAM_USER_LIBBIN/libswakFunctionObjects.so

if it really exists.

You are right, it doesn't exists. now How can I find libswakFunctionObjects.so and put it in this folder? Am I going to do this manually?

This one is easy. Forgot
valueType internalField;

BTW: this is generally applicable for working with OpenFOAM: if it is complaining about a missing entry then add that entry (in this case valueType) and then use the "banana trick": http://openfoamwiki.net/index.php/Op...de/Use_bananas

yea,Thanks, this solved the problem. banana trick rules !

[gschaider]

Originally Posted by Mojtaba.a

You are right, it doesn't exists. now How can I find libswakFunctionObjects.so and put it in this folder? Am I going to do this manually?

No. Either rerun the compilation and see if thee is a problem with that lib or (more likely) I mistyped the test. Have a look in $FOAM_USER_LIBBIN for a similar name

Originally Posted by Mojtaba.a

yea,Thanks, this solved the problem. banana trick rules !

Good

[Mojtaba.a]

Originally Posted by gschaider

No. Either rerun the compilation and see if thee is a problem with that lib or (more likely) I mistyped the test. Have a look in $FOAM_USER_LIBBIN for a similar name

I cleaned and recompiled swak4Foam.There is no libswakFunctionObjects.so in $FOAM_USER_LIBBIN again.
I have attached the log file of recompilation.

[gschaider]

Originally Posted by Mojtaba.a

I cleaned and recompiled swak4Foam.There is no libswakFunctionObjects.so in $FOAM_USER_LIBBIN again.
I have attached the log file of recompilation.

OK. Seems you're working with a OF 2.0 and there was a change in the interface of the coded-FunctionObject. Go to Libraries/swakFunctionObjects/Make/files and remove the line with swakCodedFunctionObject.C (you won't miss it). Then that library should compile.

Also go to Libraries/Allwmake and in the first line replace /bin/sh with /bin/bash

[Mojtaba.a]

Originally Posted by gschaider

OK. Seems you're working with a OF 2.0 and there was a change in the interface of the coded-FunctionObject. Go to Libraries/swakFunctionObjects/Make/files and remove the line with swakCodedFunctionObject.C (you won't miss it). Then that library should compile.

Also go to Libraries/Allwmake and in the first line replace /bin/sh with /bin/bash

Wow, Thanks Bernhard ! Now it works like a charm ! I have libswakFunctionObjects.so in $FOAM_USER_LIBBIN right now !

Bernhard is there any way to define a new volume to calculate averages in this specified volume?

[gschaider]

Originally Posted by Mojtaba.a

Wow, Thanks Bernhard ! Now it works like a charm ! I have libswakFunctionObjects.so in $FOAM_USER_LIBBIN right now !

Bernhard is there any way to define a new volume to calculate averages in this specified volume?

swak can do calculations on cellZones and cellSets if that's what you mean.

Specification of zones and set is either done in the mesh generator or with the topoSet (or the setSet)-utility. But the usage of those has nothing to do with swak4Foam (except that swak provides topoSources based on expressions)

[Mojtaba.a]

Originally Posted by gschaider

swak can do calculations on cellZones and cellSets if that's what you mean.

Specification of zones and set is either done in the mesh generator or with the topoSet (or the setSet)-utility. But the usage of those has nothing to do with swak4Foam (except that swak provides topoSources based on expressions)

You mean that if i make a zone using toposet or the setset utility, I can not use this zone in swak4Foam?

[gschaider]

Originally Posted by Mojtaba.a

You mean that if i make a zone using toposet or the setset utility, I can not use this zone in swak4Foam?

No. I just mean that I don't feel responsible for them and won't explain them in detail

[Mojtaba.a]

Originally Posted by gschaider

No. I just mean that I don't feel responsible for them and won't explain them in detail

Bernhard, Thank you for your grateful help.

[simpomann]

Hey,

I am sorry to bring this up again, but I experience problems with the described way of calculating the average mag(U) over a plane.


I have a simple pipe (flow is 12m/s with air, laminar, no turb model yet) and added the following to my controlDict:

functions
{
    makeMagU {
       type expressionField;
         functionObjectLibs
        (
            "libswakFunctionObjects.so"
        );      autowrite false;
       fieldName magU;
       expression "mag(U)";
    }
    makerho {
       type expressionField;
         functionObjectLibs
        (
            "libswakFunctionObjects.so"
        );      autowrite false;
       fieldName rho;
       expression "1.199";
    }

messung_40d
    {
        type            faceSource;
        functionObjectLibs ("libfieldFunctionObjects.so");

        enabled         true;
        outputControl   outputTime;

        // Output to log&file (true) or to file only
        log             true;

        // Output field values as well
        valueOutput     true;  //true;

        // Type of source: patch/faceZone/sampledSurface
        source          sampledSurface;

        sampledSurfaceDict
        {
                type cuttingPlane;
                planeType           pointAndNormal;
                pointAndNormalDict
                {
                        basePoint       (0.185 0 0);  
                        normalVector    (1 0 0);
                }
                source cells; // sample cells or boundaryFaces
                interpolate true;
        }
        // Operation: areaAverage/sum/weightedAverage ...
        operation       areaAverage;

        fields
        (
            p
            U
        magU
        );
    }

messung_48d
    {
        type            faceSource;
        functionObjectLibs ("libfieldFunctionObjects.so");

        enabled         true;
        outputControl   outputTime;

        // Output to log&file (true) or to file only
        log             true;

        // Output field values as well
        valueOutput     true;  //true;

        // Type of source: patch/faceZone/sampledSurface
        source          sampledSurface;

        sampledSurfaceDict
        {
                type cuttingPlane;
                planeType           pointAndNormal;
                pointAndNormalDict
                {
                        basePoint       (0.281 0 0);
                        normalVector    (1 0 0);
                }
                source cells; // sample cells or boundaryFaces
                interpolate true;
        }
        // Operation: areaAverage/sum/weightedAverage ...
        operation       areaAverage;

        fields
        (
            p
            U
        magU
        );
    }


}

And I get an output over my plane (cut through the pipe after 40 diameters, flow is straight x-directional):

# Source : sampledSurface sampledSurface
# Faces  : 204
# Time    sum(magSf)    areaAverage(p)    areaAverage(U)    areaAverage(magU)
100    0.000104042    -0.511471    (14.8039 0.00143989 0.0096608)    14.804
200    0.000104042    -1.07848    (15.1898 -0.002704 0.00862669)    15.1898
300    0.000104042    -1.10052    (15.2711 -0.002448 0.00478738)    15.2711
400    0.000104042    -1.13157    (15.2688 -0.00338944 0.00642759)    15.2688
500    0.000104042    -1.05324    (15.2643 -0.00676656 0.00863005)    15.2643
600    0.000104042    -1.30854    (15.2804 -0.00189827 0.00590263)    15.2804
700    0.000104042    -1.30885    (15.2774 -0.00181508 0.00626128)    15.2774
800    0.000104042    -1.29363    (15.2785 -0.00386213 0.00488485)    15.2785
900    0.000104042    -1.29393    (15.278 -0.00271772 0.00544641)    15.2781
1000    0.000104042    -1.28934    (15.2778 -0.00274002 0.00545235)    15.2781

If I load the case into paraView, slice at the same distance, extract and integrate variables (cell values) I end up with a more reasonable mag(U) average of 12.009.

What did I do wrong here?
I thought my lines to the control dict would just create a field mag(U) out of the calculated U vector field and then place a slice through it and calculate an average.
Is it possible that the SWAK-code leaves out cells with a mag(U) value of 0 for some reason? My mesh is pretty rough, so a high percentage of the cells actually has the wall boundary condition of U = (0 0 0).

I found out that my average values for pressure seem to be perfectly fine (SWAK sampling and manual paraView pp lead to the exact same numbers)!
So its only a mag(U) thing here...

[gschaider]

Originally Posted by simpomann

Hey,

I am sorry to bring this up again, but I experience problems with the described way of calculating the average mag(U) over a plane.


I have a simple pipe (flow is 12m/s with air, laminar, no turb model yet) and added the following to my controlDict:

<snip>

And I get an output over my plane (cut through the pipe after 40 diameters, flow is straight x-directional):

# Source : sampledSurface sampledSurface
# Faces  : 204
# Time    sum(magSf)    areaAverage(p)    areaAverage(U)    areaAverage(magU)
100    0.000104042    -0.511471    (14.8039 0.00143989 0.0096608)    14.804
200    0.000104042    -1.07848    (15.1898 -0.002704 0.00862669)    15.1898
300    0.000104042    -1.10052    (15.2711 -0.002448 0.00478738)    15.2711
400    0.000104042    -1.13157    (15.2688 -0.00338944 0.00642759)    15.2688
500    0.000104042    -1.05324    (15.2643 -0.00676656 0.00863005)    15.2643
600    0.000104042    -1.30854    (15.2804 -0.00189827 0.00590263)    15.2804
700    0.000104042    -1.30885    (15.2774 -0.00181508 0.00626128)    15.2774
800    0.000104042    -1.29363    (15.2785 -0.00386213 0.00488485)    15.2785
900    0.000104042    -1.29393    (15.278 -0.00271772 0.00544641)    15.2781
1000    0.000104042    -1.28934    (15.2778 -0.00274002 0.00545235)    15.2781

If I load the case into paraView, slice at the same distance, extract and integrate variables (cell values) I end up with a more reasonable mag(U) average of 12.009.

What did I do wrong here?
I thought my lines to the control dict would just create a field mag(U) out of the calculated U vector field and then place a slice through it and calculate an average.
Is it possible that the SWAK-code leaves out cells with a mag(U) value of 0 for some reason? My mesh is pretty rough, so a high percentage of the cells actually has the wall boundary condition of U = (0 0 0).

I found out that my average values for pressure seem to be perfectly fine (SWAK sampling and manual paraView pp lead to the exact same numbers)!
So its only a mag(U) thing here...

I really love a good bug-hunt as much as the next guy but I'm afraid I'm not going to go hunting here (at least not in swak). Have a look at the averages of U (which are untouched by swak): they're completely consistent with the ones for mag(U). So I'd say the problem is in the faceSource. Or the velocity field is not what you expect it to be.

What you can do to check is:
- set autowrite for magU to true and check it in Paraview
- emulate the area-weighted average in with a swakExpression on the same sampledSurface (I think the expression would be "mag(U)*area()/sum(area())" with an accumulation sum)

[simpomann]

Hey,

Great thanks for your quick reply!
I checked the magU field, slicing and integrating it in a paraView leads to 12.05 m/s, so the field data actually seems to be ok!

The problem seems to be the sampled Surface (as you suggested). But is it a user fault or a bug?
I tested the same function object in different cases, the results for velocity were always a bit higher than expected and they differ from those obtained in paraView up to 20%. The results from paraView always seem more accurate to me (considering my expectations/boundary etc).
As it is working out for the pressure field perfectly, I would say the sampled Surface is defined and adressed correctly, there must be something in the way this deals with the mag(U) field.
Because I am only a user (and student), I lack the knowledge to understand the problem.

I try to make use of your second advice but i struggle with the code. I put an update here asap.

# "keyword weightField is undefined" , lets see if I can find out where I have to initialise this one
# okay, i think i figured out the place for the code
#okay i was wrong!

[gschaider]

Originally Posted by simpomann

Hey,

Great thanks for your quick reply!
I checked the magU field, slicing and integrating it in a paraView leads to 12.05 m/s, so the field data actually seems to be ok!

The problem seems to be the sampled Surface (as you suggested). But is it a user fault or a bug?
I tested the same function object in different cases, the results for velocity were always a bit higher than expected and they differ from those obtained in paraView up to 20%. The results from paraView always seem more accurate to me (considering my expectations/boundary etc).
As it is working out for the pressure field perfectly, I would say the sampled Surface is defined and adressed correctly, there must be something in the way this deals with the mag(U) field.
Because I am only a user (and student), I lack the knowledge to understand the problem.

Can't comment on that. Are you using the latest version (because you might have stumbled on a bug that might already be fixed ... but that is just a guess).

If the problem is in the sampledSurface-code then it will affect swak too. If it is in the faceSource-code ... not

Originally Posted by simpomann

I try to make use of your second advice but i struggle with the code. I put an update here asap.

# "keyword weightField is undefined" , lets see if I can find out where I have to initialise this one
# okay, i think i figured out the place for the code
#okay i was wrong!

What I understood: For a weighted average I have to initialise another Field, so I tried and added:

    makegewichtungsfeld {
       type expressionField;
         functionObjectLibs
        (
            "libswakFunctionObjects.so"
        );      autowrite true;
       fieldName gewichtungsfeld;
       expression "magU*area()/sum(area())";
    }

And I modified the function object for the measurement:

messung_40d
    {
        type            faceSource;
        functionObjectLibs ("libfieldFunctionObjects.so");

        enabled         true;
        outputControl   outputTime;

        // Output to log&file (true) or to file only
        log             true;

        // Output field values as well
        valueOutput     true;  //true;

        // Type of source: patch/faceZone/sampledSurface
        source          sampledSurface;

        sampledSurfaceDict
        {
                type cuttingPlane;
                planeType           pointAndNormal;
                pointAndNormalDict
                {
                        basePoint       (0.185 0 0);  
                        normalVector    (1 0 0);
                }
                source cells; // sample cells or boundaryFaces
                interpolate false;
        }
        // Operation: areaAverage/sum/weightedAverage ...
        operation       weightedAverage;
    weightField     gewichtungsfeld;

        fields
        (
        magU
        );
    }

But potential and simpleFoam end up with this error

--> FOAM FATAL ERROR: 
 Parser Error at "1.6-9" :"syntax error, unexpected TOKEN_area"
"magU*area()/sum(area())"
"      ^^^^             "

Best thanks,

Simon

You got it wrong. You've got to create a sampled surface and then you can do calculations on that. I'll sketch it. You'll have to adapt it to your case (especially the sampledSurface)

    createPlane
    {
        type createSampledSurface;
        outputControl timeStep;
        outputInterval 1;
        surfaceName plane;
        surface {
  <insert your sampled surface definition here>
        }
    }
    magUAverage
    {
        type swakExpression;
        valueType surface;
        surfaceName plane;
        verbose true;
        expression "mag(U)*area()/sum(area())";
        accumulations (
            sum
        );
    }

The second one just calculates the weighted average over surface (area() is the size of the faces on the surface)

Clearer?

[simpomann]

Big thanks,

with this code I can observe the mag(U) value on a self defined plane for each time step!
Wonderful!


This was very helpful. Unluckily the behaviour is the same like the other function object

Greetings,
Simon

[simpomann]

So I tried with your work around as well:

#         Time          sum
            1      12.0545
            2      12.2684
            3      12.4398
            4      12.7395
            5      12.8805
....
           45      14.2587
           46      14.2731
           47      14.2887
           48      14.3114
           49      14.3319
           50      14.3429

The results are the same like with the other function object (sorry for not using the appropriate names). I checked various time steps manually with paraView and the magU-field created by a function object and the U field (standard) come up to 12 m/s in average no matter which time I look at (at the same point in the mesh), so the fields are okay.

With every timestep the difference between the actual field values and the processed average becomes bigger.

I use Ubuntu 12.04, OF 210 and compiled SWAK 1 month ago so it should be up to date i guess, although I dont know exactly how can i verify this.

[gschaider]

Originally Posted by simpomann

Big thanks,

with this code I can observe the mag(U) value on a self defined plane for each time step!
Wonderful!

Glad you like it

If you feel like giving back it would be nice if you consider adding this as a little recipie on the openfoamwiki.net (either on the swak-page or linked from it)

Originally Posted by simpomann

This was very helpful. Unluckily the behaviour is the same like the other function object

OK. Then my guess is that there is a problem with the underlying sampledSurface (as paraview seems to report the expected values. But just in case: recheck that you used the same data in paraview. It happened before). Several things to try

- check if the area of the surface is as expected (calculate "area()" with an accumulation "sum" on the surface). But that would be too easy
- use the sample-utilitiy to write VTKs of the surface and check in Paraview whether the values there are the same as the ones you get when cutting the volume data in paraview