View Issue Details

IDProjectCategoryView StatusLast Update
0002738OpenFOAMBugpublic2018-08-28 10:59
Reporterdeepbandivadekar Assigned Tochris  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSUbuntuOS Version16.04 LTS
Summary0002738: FOAM FATAL IO ERROR: paraFoam gives different outputs for two installed versions OpenFoam 2.4.0 and OpenFoam 5.0
DescriptionI successfully installed OpenFoam 2.4.0-MFN version from (https://github.com/MicroNanoFlows/OpenFOAM-2.4.0-MNF/tree/devel-craig)
Successfully - because there are no errors anymore in the log.make and log.makePV files for openfoam and paraview.

I also have the latest build of openfoam (5.0) already installed on my system. If I try to start ParaView by typing in paraFoam in appropriate environment, I get different results for the two versions.

--------------------------------------------------
--> FOAM FATAL IO ERROR:
cannot find file

file: /home/ywb17176/system/controlDict at line 0.

    From function regIOobject::readStream()
    in file db/regIOobject/regIOobjectRead.C at line 73.

FOAM exiting
-------------------------------------------

Is this a bug !?

I have also posted this issue on CFD-Online forum: https://www.cfd-online.com/Forums/openfoam-installation/194804-installation-problem-paraview-4-1-go-openfoam-2-4-0-mnf.html#post669120


Steps To Reproduceof240 #alias for openfoam-2.4.0-mnf
paraFoam #to start ParaView just to test if it's working fine

WARN file does not exist:
    ./system/controlDict
    ./system/fvSchemes
    ./system/fvSolution
created temporary 'ywb17176.OpenFOAM'


--> FOAM FATAL IO ERROR:
cannot find file

file: /home/ywb17176/system/controlDict at line 0.

    From function regIOobject::readStream()
    in file db/regIOobject/regIOobjectRead.C at line 73.

FOAM exiting

compare the output in a new window against following:

of500 #alias for openfoam 5.0
paraFoam #to start ParaView just to test if it's working fine

WARN file does not exist:
    ./system/controlDict
    ./system/fvSchemes
    ./system/fvSolution
Cannot locate OpenFOAM-format case files
Would you like to open ParaView anyway <Y|n>
Additional InformationSince, there are no errors in the logs I'm assuming the installation went fine. I have attached the paraview installation log.

Also, are those warnings normal ? If not, how to correct this.
TagsNo tags attached.

Activities

deepbandivadekar

2017-10-25 12:42

reporter  

log.makePV (4,122,482 bytes)

chris

2017-10-25 12:59

manager   ~0008936

The paraFoam script is different between OpenFOAM 5.0 and OpenFOAM 2.4.0. That is not a bug.

deepbandivadekar

2017-10-25 13:05

reporter   ~0008937

OK. So, ParaView is treated differently by the two versions.
So how do I resolve these warnings which are common for both versions:

WARN file does not exist:
    ./system/controlDict
    ./system/fvSchemes
    ./system/fvSolution

chris

2017-10-25 13:11

manager   ~0008938

To avoid the warnings, run ParaFoam from a case directory. This is basic knowledge, I suggest reading the User Guide.

In version 5.0, when a user runs the paraFoam script when they are not in an OpenFOAM case directory, it offers the opportunity to open ParaView as normal [y/n].

A minor change in the way something works is not an issue. This is closed.

deepbandivadekar

2017-10-25 13:28

reporter   ~0008940

I'm sorry I troubled you with a minor issue. In general someone who is very new to Linux as well as OpenFoam it is impractical to know if it is minor or serious issue. I was simply trying to resolve my queries.

Nonetheless, thanks for your quick resolution! Good day.

Issue History

Date Modified Username Field Change
2017-10-25 12:42 deepbandivadekar New Issue
2017-10-25 12:42 deepbandivadekar File Added: log.makePV
2017-10-25 12:59 chris Assigned To => chris
2017-10-25 12:59 chris Status new => closed
2017-10-25 12:59 chris Resolution open => fixed
2017-10-25 12:59 chris Note Added: 0008936
2017-10-25 13:05 deepbandivadekar Status closed => feedback
2017-10-25 13:05 deepbandivadekar Resolution fixed => reopened
2017-10-25 13:05 deepbandivadekar Note Added: 0008937
2017-10-25 13:11 chris Note Added: 0008938
2017-10-25 13:12 chris Status feedback => closed
2017-10-25 13:12 chris Resolution reopened => fixed
2017-10-25 13:12 chris Sticky Issue No => Yes
2017-10-25 13:28 deepbandivadekar Status closed => feedback
2017-10-25 13:28 deepbandivadekar Resolution fixed => reopened
2017-10-25 13:28 deepbandivadekar Note Added: 0008940
2017-10-25 17:46 henry Status feedback => closed
2017-10-25 17:46 henry Resolution reopened => no change required
2018-08-28 10:59 wyldckat Sticky Issue Yes => No