[derekm]

moving from 2.4.0 to 3.0+ and the fvOption temperatureLimitsConstraint has been removed.is this a bug or policy? I've checked the src and it is definitely gone.

edit/
I 've subsequently found out its deliberate in 3.0. however in 3.0+ its replacement (limitTemperature) at the moment is subject to an installation bug ... (limitTemperature missed out of the fvOptions/Make/files)
/edit

[derekm]

Be aware that in the transition to v3.0 from v2.4 some fvOptions have:
changed name,
changed location,
changed syntax


e.g

fvoptions are now in the constant directory
p, li { white-space: pre-wrap; } temperatureLimitsConstraint is no longer there, its supposed to be replaced by limitTemperature ( edit it works in 3.0.1 but not in 3.0+). I dont know if thats the only one


the location in the syntax of "selectionmode" and other stuff has changed

from

porousToair
{
    type            constantHeatTransfer;
    active          on;
    selectionMode   mapRegion;
    interpolationMethod cellVolumeWeight;
    nbrRegionName   air;
    master          true;

    constantHeatTransferCoeffs
    {
        nbrModelName    airToporous;
        fieldNames      (h);
        semiImplicit    no;
    }
}

to

porousToair
{
    type            constantHeatTransfer;
    active          yes;

    constantHeatTransferCoeffs
    {
        interpolationMethod cellVolumeWeight;
        nbrRegionName   air;
        master          true;

        nbrModelName    airToporous;
        fieldNames      (h);
        semiImplicit    no;
    }
}

can someone point me to the release notes where this was advertised as happening.

[wyldckat]

Greetings Derek,

The release notes that relate to this should be the ones from OpenFOAM 3.0.0: http://www.openfoam.org/version3.0.0/ - section "Sources and Constraints (fvOptions)"

Unfortunately, there were several more changes that weren't listed in the release notes and that you've stumbled upon. These changes are listed here:

• Regarding the renaming of "temperatureLimitsConstraint" to "limitTemperature": https://github.com/OpenFOAM/OpenFOAM...fac057ff7d3a9d
• As for the change in the selection mechanism: https://github.com/OpenFOAM/OpenFOAM...a5d4ff73e9dabc

There are a couple more features I managed to list here: http://www.cfd-online.com/Forums/ope...m-3-0-0-a.html - post #2, but it's still far from listing all changes that were made.

The code present in OpenFOAM 3.0.0 was started in December 2014 and was released almost a year later, which is why the release notes are not 100% complete.


Either way, the trick in these situations is to compare a tutorial in each version of OpenFOAM to see what changed between versions for the particular feature you're trying to use.


For the record, I noticed that you've also reported a bug for this in OpenFOAM+ at https://develop.openfoam.com - in issue #89. I only haven't given a full link, given that the access is visible only to registered users on their system.

Best regards,
Bruno

[derekm]

Originally Posted by wyldckat

Greetings Derek,
...

Either way, the trick in these situations is to compare a tutorial in each version of OpenFOAM to see what changed between versions for the particular feature you're trying to use.
...

Best regards,
Bruno

Normally true
alas the feature in question and its replacement don’t have a presence in the tutorials

[wyldckat]

Sorry, I saw on the second commit that I listed above, near the end, how it had changed for the other tutorials, but I forgot to look for examples for this particular fvOption

[aee]

So it's not just me...
Thanks for brining this up for the rest of us. I'm dealing with temperature runaway in reactingParcelFilmFoam and your info may put an end to many many hours of frustration and angst.

Thanks again!

This is what i have in fvOptions now, and it seems to be working:

temperatureLimit
{
type limitTemperature;

active true;
limitTemperatureCoeffs
{
selectionMode all;
Tmax 410;
Tmin 200.0;
}
}

The big question however, is "Is this the only way to deal with temperature runaway, or is there something that can prevent it with htcConv settings or solver parameters?"

[fritznieb]

I just Had similar issues as people in this thread, but seems like the Format changed so in case someone after 2020 using OpenFOAM8 has similar issues, this is my code for the system/fvOptions File that seemingly solved this issue for me.

FoamFile

{
    version 2.0;
    class dictionary;
    location "system";
    format ascii;
    object fvOptions;
}
limitTemperature
{
    type limitTemperature;
    active      true;
    limitTemperatureCoeffs
    {
        selectionMode all;
        min     200;
        max     400;
    }
}