[mabinty]

hi!

Where line 71 is "globalBoundaryList = buildGlobalBoundaryList(mesh); " as described above. I suppose, that "mesh" is only used to describe what has to be done in something like a meta language rather than the correct syntax. What should be used there instead?

globalBoundaryList = buildGlobalBoundaryList(fluidRegions[i]);

cheers,
aram

[Wolle]

Hey Aram!

Thanks for your code, that was exactly, what I was looking for. Indeed, as I expected, one has to refer to the fluid regions (resp. their meshes) seperately. I just didn't know the correct syntax (learned some ANSI C some years ago, don't know the syntax of C++ too much) and the object structure of OpenFoam is still a miracle to me...

Thanks a lot, I'm going to start some tests with that right now...

Ciao
Wolle

P.S.: As I intended to calculate heat flux over the boundaries later on, this is also a nice tutorial and a good point to start I think...

EDIT: Strange that I can only see your postings just after posting a reply myself - updating the browser page doesn't help so far? Strange...

[Wolle]

As boundary face normals point outwards of the domain, I suppose positive flux values should be read as a flux of mass leaving the domain?

[mabinty]

correct! positive flux = out of the domain; negative flux into domain.

aram

[Wolle]

Hi all,

I tried the waveTransmissive bc just for the ceiling, while all other patches remained walls. This looked good at first sight, but then the case ran into problems... I think due to inappropriate geometry.

So I chose to use waveTransmissive BC for left, right and top. First 200 time steps look good so far. At the moment I'm running this for a longer time just to see, what happens...

I tried to clean up the case, translated the comments into (maybe somehow humble) English and packed things up together with the modified solver (mass flux calculation). Here it is, feel free to comment...

Ciao
Wolle

P.S.: I didn't get tar to produce multiple volumes and due to the upload file size restrictions, I packed everything up with 7z, which should be installed on most Linux machines (or can be installed through official repositories). As the file attachment dialogue doesn't accept the file endings, I added ".doc". To unpack simply remove ".doc" from the file names, rightclick and unpack with 7z...

[Wolle]

Hi all!

I think, I've got a nice setup now, that will do for my purposes. Now I intend to include heat flux calculation similar to the mass flux calculation.

Do I have to include it this way or is there already a feature doing this?

As I don't know, where to start and the documentation remains rather cryptic to me... could someone please explain, what the lines

flux = sum(phi.boundaryField()[patchIndex]);

and

reduce(flux, sumOp<scalar>());

do?

The first line calculates the sum of phi at the boundary field of the processed patch, I think. But so far I couldn't find out, where to look for what the sum() function REALLY does, what arguments it takes, what it gives as return value etc. Please help me to help myself and give a hint, where to look in order to find the solution by myself.

I'm totally clueless, what the second line does. But in the end it's the same: I just don't know, WHERE to look in the code...

Ciao
Wolle

[Daniele111]

Hi all
Where can i find multiRegionLiquidHeater solver?

Thanks

[Wolle]

Hi all!

I dug in the depths of the "C++ Source Guide"... is that the same as what's known as "Doxygen"? However: it's really confusing. Is there something like a beginners guide to that?

In order to calculate heat flux at the borders, I thought about this a little. With respect to my setup (fluid with solid heater of constant temperature), I think at first I'd like to sum up the heat flux at the boundaries. At the moment, I'm not even sure, which variables I can use and how to do this in the end. All I write from now on, refers to the chtMultiRegionFoam solver as of OF-1.7.

From reading the code (and trying hard to understand), some questions arise. The fields "gh" and "ghf" seem to only calculate the inner product of g and the position of the cell/face centre, returning a scalar. What are those fields for?

Now, what's even more interesting, is the thermoFluid stuff.

In createFluidFields.H, line 22, it says:

        Info<< "    Adding to thermoFluid\n" << endl;
        thermoFluid.set
        (
            i,
            basicPsiThermo::New(fluidRegions[i]).ptr()
        );

So, what does this mean? Does every fluidRegion now have a "thermoFluid" property of basicPsiThermo type? Or is the region itself of basicPsiThermo type? basicPsiThermo inherits the p field (volScalarField) from basicThermo which is used later on (calculating p_rgh) is that right so far?

The basicThermo class also has other interesting properties/functions:
* rho Density [kg/m^3].
* h Total enthalpy [J/kg].
* hs Sensible enthalpy [J/kg].
* e Internal energy [J/kg].
* T Temperature [K].
* Cp Heat capacity at constant pressure for patch [J/kg/K].

Now for some of those, there is a further distinction, let's take h for example:
* virtual volScalarField & h () = Total enthalpy [J/kg].
* virtual const volScalarField & h () const = Total enthalpy [J/kg].
* virtual tmp< scalarField > h (const scalarField &T, const labelList &cells) const = Total enthalpy for cell-set [J/kg].
* virtual tmp< scalarField > h (const scalarField &T, const label patchi) const = Total enthalpy for patch [J/kg].

Does that mean, that refering to some basicThermoObject.h(const scalarField &T, const label patchi), which returns a scalarField, gives all the h values at the patch? What patch label to use can be figured out from the calculateMassFlux.H as mentioned above... but what (and how?!!!) to use as T scalar field? Would something like this be correct?

{
    scalar netHeatFlux = 0;
    forAll (globalBoundaryList, patchI)
    {
        scalar heatFlux = 0;
        label patchIndex = mesh.boundaryMesh().findPatchID(globalBoundaryList[patchI]);
        scalarField totalEnthalpyOfPatchField = h(T, patchIndex); // I know, this variable is not further used...
        if (patchIndex >= 0)
        {
            heatFlux = sum(h.boundaryField()[patchIndex]);
       }
        reduce(heatFlux, sumOp<scalar>());
        Info<< "Heat flux at " << globalBoundaryList[patchI]
            << " = " << heatFlux << endl;
        netHeatFlux += heatFlux;
    }
    Info<< "Net heat flux = " << netHeatFlux << endl;
    cumulativeHeatFlux += netHeatFlux;
    Info<< "Cumulative heat flux = " << cumulativeHeatFlux << endl << endl;
}

But.... OH NO!!!
http://foam.sourceforge.net/docs/cpp...rce.php#l00271
Not implemented?!?!

Well, after all it seems, that I have to refer to hPsiThermo class, as this one is specified in my thermophysicalProperties dictionary. hPsiThermo seems to have cp as well as h. It took me hours to realize that, as I can see no statement in the code, that performs the lookup of that dictionary until now... where can I find that?

Ciao
Wolle

EDIT: Of course h is always positive, so I guess, I would have to calculate h*phi? How to do that?

[Wolle]

Hi all!

Now... in order to get the dimensions right, I think I've got to multiply with deltaT.

{
    scalar netMassFlux = 0;
    scalar netHeatFlux = 0;
    scalar netHEATFlux = 0;

    forAll (globalBoundaryList, patchI)
    {
        scalar massFlux = 0;
        scalar heatFlux = 0;
        label patchIndex = mesh.boundaryMesh().findPatchID(globalBoundaryList[patchI]);
        if (patchIndex >= 0)
        {
            massFlux = sum(phi.boundaryField()[patchIndex]);
            heatFlux = sum(h.boundaryField()[patchIndex]);
        }
        reduce(massFlux, sumOp<scalar>());
        reduce(heatFlux, sumOp<scalar>());
        scalar HEATFlux = heatFlux * massFlux * runTime.deltaT().value();
        Info<< "Mass flux at " << globalBoundaryList[patchI]
            << " = " << massFlux << endl;
        netMassFlux += massFlux;
        Info<< "Heat flux at " << globalBoundaryList[patchI]
            << " = " << heatFlux << endl;
        netHeatFlux += heatFlux;
        Info<< "HEAT flux at " << globalBoundaryList[patchI]
            << " = " << HEATFlux << endl;
        netHEATFlux += HEATFlux;
    }
    Info<< "Net mass flux = " << netMassFlux << endl;
    cumulativeMassFlux += netMassFlux;
    Info<< "Cumulative mass flux = " << cumulativeMassFlux << endl;
    Info<< "Net heat flux = " << netHeatFlux << endl;
    cumulativeHeatFlux += netHeatFlux;
    Info<< "Cumulative HEAT flux = " << cumulativeHEATFlux << endl;
    Info<< "Net HEAT flux = " << netHEATFlux << endl;
    cumulativeHEATFlux += netHEATFlux;
    Info<< "Cumulative HEAT flux = " << cumulativeHEATFlux << endl;
}

Then, I realized, that phi is of dimension "dimVolume/dimTime"... so that makes the mass flux calculation a rather volumetric flux calculation or did I miss something?

So I guess, I should multiply by rho. As phi and h are summed up for each patch, I think an average rho of the respective patch would be good. How to obtain that?

Yes, I know it's rather ugly code.... please note, that I'm a beginner.

By the way... I still don't know, what the reduce function does?

Ciao
Wolle

[Fransje]

Hi Wolle,

Look at the following link to (start) to understand what the reduce function does.

Good luck,
Kind regards,

Francois.

[mirko]

Originally Posted by sebonator

Hi marval,

it's me again ;-)

I just had a look at my cases and realized that I told you something wrong again:
You don't have to indicate something like a "neighbourPatch" in your time directories. What I meant are the keywords "samplePatch" and "sampleRegion" which have to be set inside the constant/Region/polyMesh/boundary-files. Make sure these entries are correct to ensure that your fluid patches sample with the correct solid patches!

Goog luck!
Greetings Sebastian

Looking at OF's tutorial multiRegionHeater, the samplePatch and sampleRegion are set after running allRun. So, I don't think one has to set them ahead of time.

On the other hand, I've seen tutorials where these are set in system/Region/changeDictionaryDict boundary entry.

Mirko

[alvora]

Hi.. Aram,
I have some confusion in boundary condition in chtMultiRegionFoam.. you explain as below...

_solidWallTemperatureCoupledFvPatchScalarField.C:

Foam::tmp<foam::scalarfield>
Foam::solidWallTemperatureCoupledFvPatchScalarFiel d::flux() const
{
const fvPatchScalarField& Kw =
patch().lookupPatchField<volscalarfield,>(KName_);

const fvPatchScalarField& Tw = *this;

return Tw.snGrad()*patch().magSf()*Kw;
}

in this condition, mathematical equestion is K1*T1=K2*T2 ? I am not sure.. please correct me if I am wrong.. if this is correct, How can Implement below boundary condition?
K1*(normal component of gradient (T1))=K2*(normal component of gradient(T2))?

where, K1 and K2 are scalarvolume for different filed respectevely, and T1 and T2 are also scalar for different fields.. actually I want to use for electrostatic problem for multiregion.. in that, K used as permitivitty and T used as electric potential (Volt).

thank you in advance for any help...

kind regards
alpesh

[alvora]

Originally Posted by mabinty

_solidWallTemperatureCoupledFvPatchScalarField.C:

Foam::tmp<foam::scalarfield>
Foam::solidWallTemperatureCoupledFvPatchScalarFiel d::flux() const
{
const fvPatchScalarField& Kw =
patch().lookupPatchField<volscalarfield,>(KName_);

const fvPatchScalarField& Tw = *this;

return Tw.snGrad()*patch().magSf()*Kw;
}

thx in advance for any comments!!
aram

Hi.. Aram,
I have some confusion in boundary condition in chtMultiRegionFoam.. you explain as below...

_solidWallTemperatureCoupledFvPatchScalarField.C:

Foam::tmp<foam::scalarfield>
Foam::solidWallTemperatureCoupledFvPatchScalarFiel d::flux() const
{
const fvPatchScalarField& Kw =
patch().lookupPatchField<volscalarfield,>(KName_);

const fvPatchScalarField& Tw = *this;

return Tw.snGrad()*patch().magSf()*Kw;
}

in this condition, mathematical equestion is K1*T1=K2*T2 ? I am not sure.. please correct me if I am wrong.. if this is correct, How can Implement below boundary condition?
K1*(normal component of gradient (T1))=K2*(normal component of gradient(T2))?

where, K1 and K2 are scalarvolume for different filed respectevely, and T1 and T2 are also scalar for different fields.. actually I want to use for electrostatic problem for multiregion.. in that, K used as permitivitty and T used as electric potential (Volt).

thank you in advance for any help...

kind regards
alpesh

[mabinty]

hi alpesh,

in the solidWallTemperatureCoupledMixed BC the common interface temperature between two regions "0" and "1"is calculated from the energy balance

diffusiveFlux[region0] = diffusiveFlux[region1]

leading to

Tw = (K0*intField0/Dx0+K1*intField1/Dx1)/(K0*/Dx0+K1*/Dx1)

where Dx is the distance from the interface to the first internal grid point, and intField the value at this point in the respective region. Tw is set as BC for both regions at the interface based on the mixedFvPatchField BC type (src/finiteVolume/fields/fvPatchFields/basic/mixed). See also Patankar: Numeric Heat Transfer and Fluid Flow, p 44 ff, the code at solvers/heatTransfer/chtMultiRegionFoam/derivedFvPatchFields/solidWallMixedTemperatureCoupled/solidWallMixedTemperatureCoupledFvPatchScalarField .C and search the forum for the BC for more info.

hope that helps!

cheers,
aram

[alvora]

Hello Aram,

Thank you very much for reply..

Kind Regards
Alepsh

[alvora]

Hello friends,

I am using chtmultiregionFoam for my case.. my case consists two regions (solid and fluid).. one sphere subjected to under external electric field.. hence, I made geometry in gmsh, one sphere in box, and sphere define as solid and surrounding air region in box defined as fluid, air. I transfer gmshToFoam and made set up.
I don't need NS equation in fluid region and also don't need heat equation in fluid region. Hence, I removed all equation and implement my own equation for both region... I succeed in that.. I run simulation and it's work..
But, I am not sure about boundary condition.. because I used "SolidWallMixedTemperatureCoupled" boundary condition.. My equations (problem) need boundary condition at interface as below:

e1*d/dn(Voltage1)=e2*d/dn(Volatage2) or e1*(En1)=e2*(En2)
where, e1 & e2 is permittivity of solid and fluid, respectively. En is the normal component of electric field strength. electric field strength is also define as : -1*grad(Voltage).

I used "swmtc" boundary condition with K define as "e" and neighbour field define as "voltage".. because in solver code, variable is voltage in both regions.. solver solving equation is: divergence(e*gradient(Voltage))=0


The question is: is it correct boundary condition for above case? or can you tell me that the "SolidWallMixesTemperatureCoupled" b.c. solves which condition at interface? is it solving following condition for temperature.. k1*d/dn(T1)=k2*d/dn(T2) ? where, K is thermal conductivity and T is temperature..

I also tried to read the code file "SolidWallMixedTemperatureCOupledFvPatchScalarFiel d.C" and also ".H".. But, I didn't get completely..

I didn't get:
this->refValue() = nbrIntFld;
this->refGrad()=0.0;
this->valueFraction()=nbrKDelta / (nbrKDelta + myKDelta ());

Can anyone help me to understand these, please?

Kind regards and thanks in advance
Alpesh

[felipecondo92]

HI
I'm Felipe a mechanical student from ESPOL, Ecuador. I have to work on the simulation of axial flow pump in Fluent, but i don't even have the geometry does anyone can please help me with this?Please
Thanks
Felipe

[elvis]

Hi Felipe,

This is a Forum for OpenFOAM users
you will find Fluent User discussing http://www.cfd-online.com/Forums/fluent/
and someone might be able to share a case there
For OpenFOAM there is Special Interest Group Turbomachinery that provides some Validation test cases
see->The DARPA HIREP (High Reynolds Number Pump) axial flow pump
http://openfoamwiki.net/index.php/Si...ion_test_cases if you want to convert that case to fluent
there is a tool foamMeshToFluent that writes out the OPENFOAM® mesh in Fluent mesh format , but you have to install OF to use that tool.
My guess among the Fluent users someone might have a case for you that need no converting