[fanny]

Hello everyone,

I would want to set non-uniform values to the temperature field to selected cells. I suppose I may use fixedFieldValueConstraint in the fvOptions, as

fixedTValues
{
type scalarFixedValueConstraint;
active yes;

selectionMode cellSet;
cellSet myCellsSet;

fieldValues
{
T 0.1;
}
}


Is it possible to replace the constant "1.0" by a function of the cell positions ?

Is it even possible to replace it by a time-dependent function ?


Than you for your help !
Fanny

[Tobi]

Simply. Yesno. What you can do is:

• Manipulate the matrix of the solver / field directly by applying a point list and the value - but here you would need to constrain the enthalpy equation (as there is no temperature one)
• Use the scalarFixedValueConstraint and apply it to the enthalpy equation but again, the constraint values need to be "enthalpy data". Just apply all single points to a cellZone and you are done
• Use the fixedTemperatureConstraint and directly set the temperature (its equal to the above one but setting the temperature values rather than enthalpy)
• Use a coded fvOption and do it there (similar to option #1)

So probably you go with option #3. The only thing you need to do is to use setSet or topoSet to create the cellZone. The cellZone contains all cells you want to manipulate.
To the other questions: I cannot find any number named 1.0. In the latest Foundation version (v9) you can apply a «function1» to the values of the cells and make it "what-ever" dependent.

  fixedTemperature                                                            
    {                                                                           
        type            fixedTemperatureConstraint;                             
                                                                                
        selectionMode   all;                                                    
                                                                                
        phase           gas; // Optional phase name                             
                                                                                
        // Uniform temperature constraint                                       
        mode            uniform;                                                
        temperature     constant 500; // Uniform temperature << you can make it TIME dependent                   
                                                                                
        // // Looked-up field temperature constraint                            
        // T            T; // Temperature field name                            
    }

[fanny]

Hi Tobi, and thank you very much for your reply.



Actually my variable T is not the temperature, but a scalar field I want to transport. (I can be anything, it doesn't mind). So I have a T-equation (the transport one) but no energy equation. Thus, I suppose I can not use fixedTemperatureConstraint, but I should use scalarFixedValueConstraint, isn't it ?


I would want to write something like:

fixedTValues
{
    type                   scalarFixedValueConstraint;
    active                yes;
    selectionMode  cellSet;
    cellSet               myCellsSet;
    fieldValues
    {
        T    0.1 * t * x ;
    }
}

but it does not work, off course - the expression must be input differently but I don t know how..

Thanks
Fanny

[Tobi]

Ah okay, a passive scalar or any other field can be handled by using the other one. The special stuff about the temperature... guy is that it is directly applied to the enthalpy equation and you don't have to think about anything else.

I just checked the Foundation version v9 and the scalar... guy. It seems that you cannot use a time-dependency here as the entries are not of function1.

    porosityTurbulence                                                          
    {                                                                           
        type            fixedValueConstraint;                                   
                                                                                
        selectionMode   cellZone;                                               
        cellZone        porosity;                                               
                                                                                
        fieldValues                                                             
        {                                                                       
            k           1;                                                      
            epsilon     150;                                                    
        }                                                                       
    }

However, in the source code it states:

        //- Field values                                                        
        HashPtrTable<objectFunction1> fieldValues_;

Therefore, it should be a function1 possibility. Try it by using:

fixedTValues
{
    type                   scalarFixedValueConstraint;
    active                yes;
    selectionMode  cellSet;
    cellSet               myCellsSet;
    fieldValues
    {
        T     constan 34;   // write constant wrong such as constan ...
    }
}

If it will return an error with possible options, the value is of type «function1» and you have a lot of freedom.

[fanny]

I am using the OF version v7.


Yes I had tried the "banana" method :



fixedTValues { type scalarFixedValueConstraint; active yes; selectionMode cellSet; cellSet myCellsSet; fieldValues { T banana 34; } }

returns
--> FOAM FATAL IO ERROR:
wrong token type - expected Scalar, found on line 28 the word 'banana'
It seems that there is no other option than to input a scalar number.
pre.cjk { font-family: "Nimbus Mono L", monospace } p { margin-bottom: 0.1in; line-height: 120% }

[Tobi]

Its related to the fact that in v7 its not implemented as <Function1>:

    // Private member data                                                      
                                                                                
        //- Field values                                                        
        List<Type> fieldValues_;

Hence, its not possible to use it. Two options:

• Update the constrain class
• Upgrade foam to v9 or v2106

[fanny]

OK. Thank you very much.

[JMcnetee]

Is there a ScalarMaxValueConstraint option?

The ScalarFixedValueConstraint sets the scalar to a fixed, non-changing value, right?

[Tobi]

Correct, yes.

The ESI-OpenCFD version v2306 (openfoam.com) does not have such an fvOption. But you can simply derive it from, e.g., this one: https://gitlab.com/openfoam/openfoam...tTemperature.H


If you use the cfd.direct version (openfoam.org), there is a function for that called limitMag: https://github.com/OpenFOAM/OpenFOAM...Mag/limitMag.H


In principle you can also use the limitMag and compile it against ESI-OpenCFD version while resolving potential compiling issues based on naming convention changes or so on.



Cheers, Tobi

[JMcnetee]

I think you had a typo!

The ESI-OpenCFD version v2306 (openfoam.com) does have such an fvOption

https://www.openfoam.com/news/main-n...rs-and-physics

[Tobi]

I don't get your statement, there does not exist a `scalarMinMax` fvOption for the ESI-OpenCFD version. The one you are referring to is only for the turbulent viscosity.

[JMcnetee]

Ahhh....you are correct. I got ahead of myself

I was specifically looking for an nuT limiter, which is now available, but the thread is about Scalar Limiters in general

Thanks for the correction