[kar]

Hello,
when building all openfoam directory, not always support for old PV 2.4 is necessary, so how to switch that off?

[jaswi]

Hi

check out the OpenFOAM-1.4.1/.OpenFOAM-1.4.1/bashrc

Scroll down this file and you will find a section :

# Source user setup files for optional packages
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SOURCE $WM_PROJECT_DIR/$FOAM_DOT_DIR/apps/ensightFoam/bashrc
SOURCE $WM_PROJECT_DIR/$FOAM_DOT_DIR/apps/paraview/bashrc
#SOURCE $WM_PROJECT_DIR/$FOAM_DOT_DIR/apps/dxFoam/bashrc
#SOURCE $WM_PROJECT_DIR/$FOAM_DOT_DIR/apps/ParaView3/bashrc


There you can suit to your need

Hope i was correct and that helps

Regards
Jaswi

[kar]

Well, it didn't. ./Allwmake tries to build everything in a source tree, so one sees dxFoam etc errors, if there is no particular software code. I was brutal and threw away some code like mico and unnecessary postprocessing things.
I see that OF 1.5 is migrating to PV 3.X.

One thing still remains - why the hell FoamX is necessary?! It takes far more time to do simple things I could just rewrite in files... I didn't saw the FoamX's beauty somehow.
Yes, that would be nice, if there was a switch for FoamX. But I guess, these are just my wishes, also it doesn't takes much of time to deal with those things, but they do confuse at first.

[philippose]

Hello Kārlis,

If you take a look into the folder "PVFoamReader" in "applications/utilities/postProcessing/graphics/", you will find a "local" Allwmake file (I am looking into OpenFOAM-1.4.1-dev)

This file checks to see if the paraview folder (as it has been provided in the paraview bashrc file as pointed out in the previous post) exists or not.

If the folder does not exist, OpenFOAM does not try to compile PVFoamReader and vtkFoam...

If the folder does exist, it tries to compile PVFoamReader and vtkFoam irrespective of whether the version of Paraview is a compatible one or not.


As for FoamX.... personally, I started using OpenFOAM with practically no prior experience with any form of CFD software. For me, FoamX was a good starting point, because it constrains some of the common boundary conditions based on the physical type you choose.

This way, I was able to see what combination of boundary conditions are required for a specific kind of physical condition. I agree that this can also be found by looking through the tutorials... but for that you need to first know what kind of systems the tutorials are simulating... and that is much more work than FoamX dishing it out on a platter :-)!

Additionally, it provides you with a list of the various schemes and solvers available, and roughly guides you (via different dialog-boxes) to set up a particular type of scheme or solver.

Yet another feature I found useful was the list of the commonly used "utilities" available with OpenFOAM.

I would say.... on the whole I would have used FoamX for probably 2 or 3 weeks, after which I found it too restraining and cumbersome, but... for those "first-steps", it was definitely a helpful tool.

I agree that there is a lot of room for improvement, and that no one has really made any changes to FoamX since OpenFOAM-1.3 (maybe even older)....

However.... I guess thats the whole point of Open Source software :-)! The code is available, there are no restrictions to making modifications.... so if someone does not like FoamX... don't use it... if someone likes FoamX... go ahead and use it.... and if someone wants to improve on FoamX or completely rewrite it.... this freedom exists too :-)! All completely up to you to decide..... :-)!

Have a nice day!

Philippose