[Roskiki]

thank you very much

[gschaider]

Originally Posted by Roskiki

swak4foam error

please help!!!

http://openfoamwiki.net/index.php/Ho..._Message_Board

[luckyhat]

Could someone please confirm which steps of the wiki page for Installing 2.2.2 would be applicable, if I was to install 2.3.1 using this patch?

https://openfoamwiki.net/index.php/I...OpenFOAM_2.2.2

Are there any steps I should ignore or do differently?

Also, is it still possible to install 2.2.2 at this point (I am thinking this might be an easier option, as it would mean I could just follow the instructions step by step)

Thanks for your help, I have spent the past few days trying to understand how this all fits together and am a bit confused

[rdbisme]

Originally Posted by luckyhat

Could someone please confirm which steps of the wiki page for Installing 2.2.2 would be applicable, if I was to install 2.3.1 using this patch?

https://openfoamwiki.net/index.php/I...OpenFOAM_2.2.2

Are there any steps I should ignore or do differently?

Also, is it still possible to install 2.2.2 at this point (I am thinking this might be an easier option, as it would mean I could just follow the instructions step by step)

Thanks for your help, I have spent the past few days trying to understand how this all fits together and am a bit confused

I'm so sorry I could not upload the guide for the 2.3 version. I'm very busy with exam session. I would likely do it in few months.

Anyway the procedure about 2.2. is practically the same, except for the fact that now the patch it's just one to apply, and not two.

Last time I compiled 2.3, some editing on some Makefiles were required, they're however described in previous posts.

Just try to do it yourself, if you get errors try to search before around here, and if you can't succeed try to ask.

[luckyhat]

Originally Posted by alexeym

Hi,



Cause I don't know what you'd done already, I'll describe whole procedure from the beginning (more or less how I do these things):

1. Create disk image with case sensitive file system. There is a guide in wiki with pictures but I prefer CLI interface:

$ cd
$ hdiutil create -size 4.4g -type SPARSEBUNDLE -fs HFSX -volname OpenFOAM -fsargs -s OpenFOAM.sparsebundle

This command will create disk image with a name OpenFOAM.sparsebundle in you home folder. Wiki suggests creation of sparseimage type disk image but sparse bundle disk images ... here is a quote from a discussion with my colleague:



2. Create mount point for disk image and attach disk image (again it was suggested by my colleague, to have single disk image for all OF versions):

$ mkdir -p $HOME/OpenFOAM
$ hdiutil attach -mountpoint $HOME/OpenFOAM OpenFOAM.sparsebundle

3. Now you clone sources into the disk image (command for OF 2.3.x):

$ cd $HOME/OpenFOAM
$ git clone git://github.com/OpenFOAM/OpenFOAM-2.3.x.git

At this point you have sources on case sensitive FS, so now it's time to get patch, apply patch to the sources and run compilation:

$ cd OpenFOAM-2.3.x
$ curl -L http://sourceforge.net/p/openfoam-extend/svn/HEAD/tree/trunk/Breeder_2.3/distroPatches/MacPatch/OpenFOAM-2.3.x-Mac.patch?format=raw > OpenFOAM-2.3.x-Mac.patch
$ patch -p1 < OpenFOAM-2.3.x-Mac.patch

After these manipulations you need to edit etc/bashrc (I don't know what version of gcc you're using, I don't know if you installed all necessary software dependencies using Macports, so at this points it's all up to you).

After you just

$ source etc/bashrc
$ ./Allwmake > log.Allwmake 2>&1

and wait.

Hey guys,

I have used the method proposed by alexeym above, and I was wondering if someone would be able to check my log file (attached) to see if everything is working properly? I am new to using terminal and OpenFOAM so would appreciate any help / advice.

Thanks

[alexeym]

Hi,

Well, there were 3 principal errors. All of them are caused by missing flags in Make/options files of the corresponding solvers.

Errors are in driftFluxFoam, interFoam, interDyMFoam, porousInterFoam, and LTSInterFoam. If you can live without these solvers there's no reason to worry. Otherwise you have two choices: correct Make/options yourself, wait for new patches (though the error with driftFluxFoam was there from the initial 2.3.0 release, it seems, the error is still there).

[luckyhat]

Originally Posted by alexeym

Hi,

Well, there were 3 principal errors. All of them are caused by missing flags in Make/options files of the corresponding solvers.

Errors are in driftFluxFoam, interFoam, interDyMFoam, porousInterFoam, and LTSInterFoam. If you can live without these solvers there's no reason to worry. Otherwise you have two choices: correct Make/options yourself, wait for new patches (though the error with driftFluxFoam was there from the initial 2.3.0 release, it seems, the error is still there).

Thanks Alexeym for your help, I really appreciate that you took the time to review my log file. I don't need any of those solvers at this time so I guess I can go ahead with the tutorials now!

For any other newbies on this thread looking for a simple method to install OpenFOAM on Yosemite, I would recommend alexeym's method as being very quick and easy.

[luckyhat]

I have started going through the tutorial and have hit one more issue - I don't seem to have Paraview installed. When I type the command paraFoam

I get this:
FATAL ERROR: ParaView reader module libraries do not exist

Please build the reader module before continuing:
cd $FOAM_UTILITIES/postProcessing/graphics/PV4Readers
./Allwclean
./Allwmake

I tried following these instructions but the last command gives the error:
ERROR: ParaView not found in /Users/luckyhat/OpenFOAM/ThirdParty-2.3.x/platforms/darwinIntel64Gcc46/ParaView-4.1.0

I tried creating those folders and copying ParaView-4.1.0 into the directory but then I get the error: ./Allwmake : PV_PLUGIN_PATH not valid - it is unset

Any ideas on the best / easiest way to install ParaView?

Thanks

[alexeym]

Hi,

You should install binary version of paraview in /Applications. Download it from http://www.paraview.org/paraview-dow...rwin-64bit.dmg. And use built-in reader module using 'paraFoam -builtin'.

[luckyhat]

When I run paraFoam -builtin I get:

created temporary 'PV4Readers.foam'
/Users/brendanfox/OpenFOAM/OpenFOAM-2.3.x/bin/paraFoam: line 265: paraview: command not found

I tried restarting terminal and running the command again, now I get:

paraFoam -builtin
-bash: paraFoam: command not found

Any ideas?

[alexeym]

Originally Posted by luckyhat

created temporary 'PV4Readers.foam'
/Users/brendanfox/OpenFOAM/OpenFOAM-2.3.x/bin/paraFoam: line 265: paraview: command not found

Well, you've installed paraview.app but this operation did not put paraview in $PATH. The easiest way to solve this problem is to create symlink to paraview in $WM_PROJECT_DIR/bin. I.e. you do something like

$ cd $WM_PROJECT_DIR/bin
$ ln -s /Applications/paraview.app/Contents/MacOS/paraview

Though sometimes this operation break python console in paraview.

I tried restarting terminal and running the command again, now I get:

paraFoam -builtin
-bash: paraFoam: command not found

Any ideas?

You've closed Terminal, you've destroyed environment, so you have to recreate it after you've opened new terminal session.

[luckyhat]

Originally Posted by alexeym

You've closed Terminal, you've destroyed environment, so you have to recreate it after you've opened new terminal session.

Sorry to ask a really dumb question, but could you please clarify what steps are required in order to "recreate" the environment? Is this required every time I reboot or close terminal?

Thanks

[alexeym]

Hi,

In the guide on openfoamwiki.net (I guess you've used it to compile OF) it is called:

9. Source the bashrc file:
#Current Folder: ~/OpenFOAM/OpenFOAM-2.2.2
. etc/bashrc

You have to do this operation every time you open new terminal session. There's also chapter about Paraview in the guide.

[luckyhat]

Originally Posted by alexeym

Well, you've installed paraview.app but this operation did not put paraview in $PATH. The easiest way to solve this problem is to create symlink to paraview in $WM_PROJECT_DIR/bin. I.e. you don something like

$ cd $WM_PROJECT_DIR/bin
$ ln -s /Appli/Applications/paraview.app/Contents/MacOS/paraview

Though sometimes this operation break python console in paraview.

The error I am getting is:
ln: ./paraview: File exists

[alexeym]

Well, the output contradicts to itself, let's learn a little bit more about your installation. What is the output of the following commands:

1.

$ which paraview

2.

$ type paraview

[luckyhat]

Yeah, I think there are still some problems with my environment. Right now I am reading up on OpenFOAM shell environment (http://www.cfd-online.com/Forums/blo...vironment.html) to try and better understand what is going on.

The first command (which paraview) gave no output

The second command (type paraview) gave the following output:
-bash: type: paraview: not found

Thanks for your help

[jjstickel]

I am using Macports on Mountain Lion and have followed all the requisite steps (using case-sensitive sparse image, applied patch, edited etc/bashrc, etc.). However, I am getting errors. I will attach the log up to the first instance of "Error 1". Any suggestions?

[ajmas]

Has anyone created a github fork of the OpenFOAM 2.3.x project and applied the patch to it? If not, does anyone oppose the idea?

I am just wondering whether this would help reduce issues around the patching?

[jjstickel]

Originally Posted by ajmas

Has anyone created a github fork of the OpenFOAM 2.3.x project and applied the patch to it? If not, does anyone oppose the idea?

I am just wondering whether this would help reduce issues around the patching?

This would be great to do! As much as possible, please provide sources that are applicable to multiple OS X versions and third-party software system (Macports vs. Homebrew vs. manual).

[ajmas]

Originally Posted by jjstickel

This would be great to do! As much as possible, please provide sources that are applicable to multiple OS X versions and third-party software system (Macports vs. Homebrew vs. manual).

I have started looking at this, but I am running into issues with the my base clone already listing modified files, so I can't even start patching. Has anyone run into this issue and resolved this. I have tried playing around with my git settings, but no luck yet.

When I do get things working, I will certainly take into account your suggestion, but also try to make any solution support a cross-platform use case.

Edit: user error. I seem to have missed the part which indicated I needed to use a case-sensitive file system. Creating a case-sensitive HFS+ disk image made a difference. I wonder whether the main devs would be interested in trying to resolve the issues requiring a case-sensitive FS?