[astronauti]

Hello,

i have a cooler where the exhaust and the water flow is in the same directory (z directory). Now I want to plot the average Temperature in the xy-plane over the z Axis, to see how the Average-Temperature changes over the z-axis. Is this possible with paraFoam.

[gschaider]

Originally Posted by astronauti

Hello,

i have a cooler where the exhaust and the water flow is in the same directory (z directory). Now I want to plot the average Temperature in the xy-plane over the z Axis, to see how the Average-Temperature changes over the z-axis. Is this possible with paraFoam.

The way I would do it (but I'm extremely biased) is with a swak4Foam-function object (this would be in controlDict):

libs (
    "libsimpleSwakFunctionObjects.so"
);
functions {
    temperatureLine {
        type swakExpressionAverageDistribution;
        outputControlMode outputTime;
        valueType internalField;
        expression "T";
        weight "vol()";
        mask "true";
        abscissa "pos().z";
        binNumber 100;
        valueIfZero -666;
    }
}

This would generate files with the data every time the regular field data gets written (averages are calculated volume-weighted)

Disadvantage is that you will have to install swak4Foam

[astronauti]

Thank you very much. Swak4foam was already installed, so thats no problem. Managed to get it working for a multiRegion simulation. Whats the difference between the value in key and raw?

[gschaider]

Originally Posted by astronauti

Thank you very much. Swak4foam was already installed, so thats no problem. Managed to get it working for a multiRegion simulation. Whats the difference between the value in key and raw?

You have already been tempted by the Dark Side? Good for you.

"Key" should be the value of the abscissa (in your case z). "Raw" is the weighted average (long story. The name was inherited and I never bothered to change it). "Min" and "Max" should be obvious. "nSamples" is the number of cells that fell into the bin defined by "key" (the sad truth is that it doesn't really "cut" through the simulation but just looks at the cells. But that is much faster and "good enough")