[superkelle]

Hi I wonder why there is only a very restricted limitTemperature option in fvOptions, and not a very gerneral limitScalar:

limitT
    {
        type            limitTemperature;
        active          yes;

        selectionMode   all;
        min             200;
        max             500;
        phase           gas; // optional
    }

I know that it applied on the "he" field of basicThermo, so not directly on a scalarField.

I also know that it is not hard to hard code it in a solver:

fieldX.max(minValue);
fieldX.min(maxValue);

but I would like to do it just with something like:

fvOptions.correct(fieldX);

and a fvOptions entry like:

limitMyScalar
    {
        type            limitScalar;
        active          yes;
        
        field                sigma; 
        selectionMode  cellZone; //all
        cellZone          porosity;   
        min                 200;
        max                500;
 
    }

I also already tried to edit the limitTemperature files in that way, but since my genaral C++ knowledge specialy templetisation, class and type understanding is not so sophisticated I got stuck at how I could implement it to a specific field that is mentioned in the dictionary. And later on the implementation / linkage in OF fvOptions, so I could use it in any OF Code.


Huge thanks if someone gives me some advice.

[HPE]

Hi,

- If you would like to have a general limiter for fields, you can use limitFields function object, instead.

Hope it helps.

[superkelle]

Yes that should be what I like was looking for, thanks. Sometimes I wonder about implemented functionalities, that are somehow redundant. I am also motivated to implement it in fvOptions, for learning purpose and for the fact that it would nice to have it all in one place.