[Roskiki]

it is the same solution

1- in fact it's just addition of a line "-lincompressibleTransportModels \" and
" -linterfaceProperties" in Make/option
2- wmake

source alexeym

[f0208secretx]

Originally Posted by Roskiki

it is the same solution

1- in fact it's just addition of a line "-lincompressibleTransportModels \" and
" -linterfaceProperties" in Make/option
2- wmake

source alexeym

Thanks Roskiki and alexeym, it compiles now.

For the complete record, I changed the options file in the following folders manually,
$FOAM_APP/solvers/multiphase/driftFluxFoam/Make
$FOAM_APP/solvers/multiphase/interFoam/Make
$FOAM_APP/solvers/multiphase/interDyMFoam/Make
$FOAM_APP/solvers/multiphase/porousInterFoam/Make
$FOAM_APP/solvers/multiphase/LTSInterFoam/Make

For each of the options file, I added

-lincompressibleTransportModels \
-linterfaceProperties \

in the list of EXE_LIBS.

Thanks for the help.


JHW

[frantov]

Hello
I have successfully installed OF 2.3 in MacOS, cases are running But cant get Paraview to run. I can open it independently, but I guess Im missing a way to link it. Hope someone can help.

when I write in terminal: paraFoam, this is what I got:

>> paraFoam
created temporary 'OpenFOAM-2.3.0.foam'
/Users/frantov/OpenFOAM/OpenFOAM-2.3.0/bin/paraFoam: line 265: paraview: command not found

[alexeym]

Hi,

I guess it's the same error as:

http://www.cfd-online.com/Forums/ope...tml#post491039

[gschaider]

Originally Posted by frantov

Hello
I have successfully installed OF 2.3 in MacOS, cases are running But cant get Paraview to run. I can open it independently, but I guess Im missing a way to link it. Hope someone can help.

when I write in terminal: paraFoam, this is what I got:

>> paraFoam
created temporary 'OpenFOAM-2.3.0.foam'
/Users/frantov/OpenFOAM/OpenFOAM-2.3.0/bin/paraFoam: line 265: paraview: command not found

Currently the patch assumes that you've got the official Paraview-binaries installed as ParaView in your applications folder (/Applications/ParaView.app on the shell). If it doesn't find that it will do nothing. Otherwise it will create an alias to the paraview-binary.

paraFoam won't work though as the filter distributed with OpenFOAM needs a source-installation of paraview. But paraview has a fine built-in OpenFOAM-filter. That's why I currently don't bother to install it from source

[alexeym]

Dear Bernhard,

I'm not quite sure that the problem is in desire to build Paraview from sources. To illustrate the problem, I've created test.sh and test1.sh files (it's more or less vanilla OS X 10.9, maybe Macports installs its own version of bash). test.sh is:

#!/bin/sh

alias lha='ls -lha'

test1.sh is

#!/bin/sh

lha

Analog of 'source $WM_PROJECT_DIR/etc/bashrc' is 'source test.sh' and analog of paraFoam is ./test1.sh (as during first step alias is created and during second step we are trying to execute created alias). The result is the same as in error messages of the people reported here:

$ . test.sh 
$ ./test1.sh 
./test1.sh: line 3: lha: command not found

IIRC I had this problem with 2.1.1 patch but I've create symlink to paraview in $PATH, so the problem was solved (surely paraview.app was installed in binary form).

If I change test.sh to:

#!/bin/sh

lha() {
    ls -lha
}

export -f lha

then ./test1.sh will return listing of cwd.

Maybe it's worth changing alias to function in future patches? Also there was an issue with driftFluxFoam.

[gschaider]

Originally Posted by alexeym

Dear Bernhard,

I'm not quite sure that the problem is in desire to build Paraview from sources. To illustrate the problem, I've created test.sh and test1.sh files (it's more or less vanilla OS X 10.9, maybe Macports installs its own version of bash). test.sh is:

#!/bin/sh

alias lha='ls -lha'

test1.sh is

#!/bin/sh

lha

Analog of 'source $WM_PROJECT_DIR/etc/bashrc' is 'source test.sh' and analog of paraFoam is ./test1.sh (as during first step alias is created and during second step we are trying to execute created alias). The result is the same as in error messages of the people reported here:

$ . test.sh 
$ ./test1.sh 
./test1.sh: line 3: lha: command not found

IIRC I had this problem with 2.1.1 patch but I've create symlink to paraview in $PATH, so the problem was solved (surely paraview.app was installed in binary form).

If I change test.sh to:

#!/bin/sh

lha() {
    ls -lha
}

export -f lha

then ./test1.sh will return listing of cwd.

Maybe it's worth changing alias to function in future patches? Also there was an issue with driftFluxFoam.

OK. Wasn't aware that the alias doesn't work because I usually use paraview as paraview. Mainly because paraFoam doesn't bring me any additional benefits as only the built-in reader works (the one tht comes with the OpenFOAM-sources NEEDs a paraview-installation from sources). But I'll have a look at converting the alias to a function.

About driftFluxFoam. There is a problem with it not linking, right? Adding -ltwoPhaseMixture to Make/options fixes that. It's not in the patch because the solver has been added only recently and I don't rush out a new version of the patch every time something changes (especially in cases like this where nothing else depends on the compilation failure).

[alexeym]

Originally Posted by gschaider

Mainly because paraFoam doesn't bring me any additional benefits as only the built-in reader works

Well, at least if creates *.foam file for you and pass necessary flags to paraview. Also it's a workflow one gets used to on Linux.

(the one tht comes with the OpenFOAM-sources NEEDs a paraview-installation from sources).

Not exactly. By default yes, but paraFoam has -builtin flag for built-in paraview OpenFOAM reader. Also one can edit lines 71 and 73 of paraFoam file to permanently remove the requirement of PV3Readers compilation.

[frantov]

Hi All
problem was solved after reinstalling everything. I think I messed up with the creation of the .sparseimage file.
Thanks a lot
F

[gschaider]

Originally Posted by alexeym

Well, at least if creates *.foam file for you and pass necessary flags to paraview. Also it's a workflow one gets used to on Linux.



Not exactly. By default yes, but paraFoam has -builtin flag for built-in paraview OpenFOAM reader. Also one can edit lines 71 and 73 of paraFoam file to permanently remove the requirement of PV3Readers compilation.

OK. We're entering the territory where differences between solutions are 5 key-strokes and the main reason why people do things one way or another is habit. For me the main reason is that I used the built-in reader before paraFoam had a -builtin-flag. PyFoam adds a .foam-file to every case it touches and for me "paraview --data=foo.foam" is almost as simple as "paraFoam --builtin"

[maCrobo]

Has anyone tried parallel running on a single machine?

I've started to use the program for a few weeks on Mavericks (10.9.1). Today, I wanted to see how to perform a parallel run on a i7 quad core. I know it is possible, but I get some errors.

I would like to get some feedback on that; has anyone tried and succeeded?

[RMacReamoinn]

Originally Posted by maCrobo

Has anyone tried parallel running on a single machine?

I've started to use the program for a few weeks on Mavericks (10.9.1). Today, I wanted to see how to perform a parallel run on a i7 quad core. I know it is possible, but I get some errors.

I would like to get some feedback on that; has anyone tried and succeeded?

I have an MacBook Pro with i7 quad core. I ran one of the tutorials that utilises parallel processing and it ran fine.

[maCrobo]

Originally Posted by RMacReamoinn

I have an MacBook Pro with i7 quad core. I ran one of the tutorials that utilises parallel processing and it ran fine.

What tutorial?

[RMacReamoinn]

If I remember correctly it was the wingMotion tutorial in the incompressible/pimpleDyMFoam/ directory.

[alexeym]

Hi,

Originally Posted by maCrobo

I've started to use the program for a few weeks on Mavericks (10.9.1). Today, I wanted to see how to perform a parallel run on a i7 quad core. I know it is possible, but I get some errors.

Can you post error message(s)? I've run it in parallel on a single machine and it was OK.

[maCrobo]

Well, I'm sorry that I didn't reply sooner, but the problem was not in the program itself but in some cell distortion I got after scaling the mesh with different ratios in different directions.

I took the engineFoam tutorial, scaled its mesh to (0.7 0.7 0.5) to make it closer to my cylinder, split the domain in 4 parts and it diverged. Using 2 subdomains solved the problem.
I know I should have made a new mesh, but I did't know a fast way for it.
As far as the tutorials I made a stupid mistake.

Bye.

[dav.dap83]

I am encountering some problems in compiling.

Every time it attempts to compile something, it writes:

ld: library not found for -lPstream
collect2: ld returned 1 exit status

[gschaider]

Originally Posted by dav.dap83

I am encountering some problems in compiling.

Every time it attempts to compile something, it writes:

ld: library not found for -lPstream
collect2: ld returned 1 exit status

The problem must have happened before (during compilation of Pstream). A LITTLE bit of context would be helpful

[Roskiki]

Pre-compiled disk images of version 2.3.x for Mac 10.9?

[gschaider]

Originally Posted by Roskiki

Pre-compiled disk images of version 2.3.x for Mac 10.9?

None that I know of (but I haven't looked very much for precompiled versions to be honest). Closest thing I know of is found at https://sourceforge.net/projects/ope...am-extend-3.1/ (but of course that is the other fork).