View Issue Details

IDProjectCategoryView StatusLast Update
0004214OpenFOAMBugpublic2025-02-17 21:25
Reportermichael.mueller-wrd Assigned Towill  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformGNU/LinuxOSOtherOS Version(please specify)
Product Versiondev 
Summary0004214: PIMPLE flow, thermophysics, models controls fails when modified during runtime
DescriptionWhen those controls are switched on/off during runtime, the simulation may crash with not finding the fvSolution file:
--> FOAM FATAL ERROR:
cannot find file ".../system/fluid/fvSolution"
                                                                                        
    From function virtual Foam::autoPtr<Foam::ISstream> Foam::fileOperations::uncollatedFileOperation::readStream(Foam::regIOobject&, const Foam::fileName&, const Foam::word
    in file global/fileOperations/uncollatedFileOperation/uncollatedFileOperation.C at line 538.
                                                                                        
FOAM exiting

I have tested these features (see commit https://github.com/OpenFOAM/OpenFOAM-dev/commit/c822a9b786a38bdc8f885c1dfad9c616bf1efc9f ) with 'circuitBoardCooling' tutorial case.
While changing the new PIMPLE controls for subsequent re-starts seems to work fine, I found that changes during runtime may result in crash / FOAM FATAL ERROR.
Steps To ReproduceModify 'circuitBoardCooling' tutorial case: include control switches in system/fluid/fvSolution ->
PIMPLE
{
    momentumPredictor yes;
    nNonOrthogonalCorrectors 0;
    pRefCell 0;
    pRefValue 0;
                                            
    flow on;
    thermophysics on;
    models on;
}

Run simulation & change switches during runtime.
TagsNo tags attached.

Activities

henry

2025-02-13 16:29

manager   ~0013529

The error:
> cannot find file ".../system/fluid/fvSolution"

appears to relate to the filing system on your computer or the way in which you are editing the file, it seems that it disappears for a while. I am not able to reproduce this issue on my system using emacs as the editor.

will

2025-02-17 21:25

manager   ~0013530

Following email correspondence with the reporter... This issue seems to be largely confined to people using vi/vim, and it can be mitigated by putting `set backupcopy=yes` in the ~/.vimrc. So, it seems to be largely a third-party configuration issue. Closing.

Issue History

Date Modified Username Field Change
2025-02-13 16:21 michael.mueller-wrd New Issue
2025-02-13 16:29 henry Note Added: 0013529
2025-02-17 21:25 will Note Added: 0013530
2025-02-17 21:25 will Assigned To => will
2025-02-17 21:25 will Status new => closed
2025-02-17 21:25 will Resolution open => no change required