CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM Installation (https://www.cfd-online.com/Forums/openfoam-installation/)
-   -   Version 15 on Mac OS X (https://www.cfd-online.com/Forums/openfoam-installation/57216-version-15-mac-os-x.html)

gschaider July 18, 2008 07:56

Hi! I managed to compile 1.
 
Hi!

I managed to compile 1.5 on my iBook and I thought I might share my experience with the other Mac-Heads out there. Two words of caution:

- I only have a PowerPC-iBook with 10.4 available (so the milage for the Intel/10.5-guys out there might vary)
- the description is very short. Some info about previous versions (found on the Wiki and here) might be applicable (especially the disk-image etc)

So be ready to wear your asbestos-pants (like a certain Canadian usually says). Previous experience with compiling OF helps

I assume you have a Lower/Upper-case filesystem available.
The two patch-files http://www.cfd-online.com/OpenFOAM_D...hment_icon.gif OpenFOAM-1.5-Mac-v1.patch.gz and http://www.cfd-online.com/OpenFOAM_D...hment_icon.gif ThirdParty1.5-Mac-v1.patch are to be applied with "patch -p0 <patchfile" in the appropriate directories (figure it out from the filename)

After that compilation should work as described in the Release-notes

Some notes:
- On my system I use the ancient vendor supplied gcc 4.0.1 (don't know what the version is for 10.5)
- I don't know the correct output of 'uname -p' on Intel-Macs. Could somebody please supply me with that so that I can update the scripts
- I distinguish two architectures darwinPpc and darwinIntel. This might be a slight overkill and of course some of the #ifdefs are untested on Intels
- My only testing so far was running interFoam on the damBreak-case and building household appliances for eskimos (you'll know the tutorial case when you see it) with snappyHexMesh. All of them successfully
- due to the linker options some applications might compile AT RUNTIME about missing symbols. Usually from the finiteVolume-library. Add -lfiniteVolume in the Make/options-file of that application and recompile it.
- I didn't bother to build the supplied version of paraView yet. So you'll have to go via the foamToVTK/downloadedParaviewBinary-route
- The OpenMPI from ThirdParty is used (no need to get the one from ports)
- For one of the (PAR)Metis-libraries the .dylib has to be copied to the corresponding .so (can't remember which one) Otherwise one of the linker scripts in ThirdParty won't find it
- The only application that does not yet compile for me is the cht-solver (I blame the old compiler)

Feedback that helps to improve the patch is most welcome

Bernhard

gschaider July 18, 2008 08:10

I forgot: some versions of pat
 
I forgot: some versions of patch don't automatically create the wmake/rules/darwinPpc-directory. Do so by hand before applying the patch. The Intel-guys will have to copy everything from darwinPpc to darwinIntel (that is the punishment you have to accept for having a faster machine than me)

Bernhard

podallaire July 18, 2008 08:19

Bernhard : thank you ! I wi
 
Bernhard : thank you !

I will try to compile it on my Intel Mac today and will post my findings.

Best regards,

Pierre-Olivier

mgz1985 July 18, 2008 14:00

hi bernard......i am having pr
 
hi bernard......i am having problems installing 1.4.1 on mac....i downlaoded the image files and everything was ok until i came to sourcing it when i realized there was no bashrc file in the bin or anywhere....this avoided me from sourcing the file......where can i get the bashrc file.....is it possible to copy it from a linux version openfoam....can u really help me fix this problem

podallaire July 18, 2008 18:30

mayank, all the info that y
 
mayank,

all the info that you need to compile 1.4.1 on Mac OS X can be found at :

http://openfoamwiki.net/index.php/Ho...e_OpenFOAM_Mac
http://www.cfd-online.com/OpenFOAM_D...tml?1216150424

Bernhard,

for your info -> uname -p is "i386" on a Core Duo Machine (32-bit intel). I'm compiling the beast ... I have this strange error :

cp: wmakeFiles/libccmio: No such file or directory

The wmake directory does not seem to be in ThirdParty - any idea ? I will post some minor modifications that I made in order to compile on Leopard as soon as it's done.

Regards,

PO

mgz1985 July 19, 2008 02:01

hi pierre-olivier i tried ever
 
hi pierre-olivier i tried everything on theses 2 forums. Everything works fine except the sourcing. As i am new to unix, i am using disk images. My mounting and creation of sparse images is fine but after that when i am setting up the environment i get this error of no such file or directory.

I have spent entire 2 days on the internet trying to debug this but to no avail. i shall be trying it again tonite and then shall post the entire console here...

mgz1985 July 19, 2008 03:35

thanx all it is working now...
 
thanx all it is working now........especially Mr. Wild for his notes on the ETH website........and Pierre-olivier for his response....i hope i can learn to use it..

mgz1985 July 19, 2008 13:39

apps/paraview/??rc what doe
 
apps/paraview/??rc

what does this mean in the wikipedia forum for paraview....i m unable to understand this command........I have installed paraview 3 as a disk image...

fra76 July 20, 2008 04:16

Hi Pierre-Olivier, how did yo
 
Hi Pierre-Olivier,
how did you download XCodeTools from Apple website? I cannot find it...
However, I've used fink to install gcc 4.2.2. I'll try to compile OpenFOAM using it.

Francesco

mgz1985 July 20, 2008 04:36

Hi again PO, my precise err
 
Hi again PO,

my precise error is this

mayank-guptas-macbookhttp://www.cfd-online.com/OpenFOAM_D...part/proud.gifpenFOAM-1.4.1 mayankgupta$ paraFoam ~/openfoam/mayank/run/icoFoam cavity
/Users/mayankgupta/OpenFOAM/OpenFOAM-1.4.1/bin/paraFoam: line 75: paraview: command not found

I have tried setting the path in my bashrc to DYLD.... from $1:$DYLD...

but when I do that i cant save the edited file.

Can u please tell me what is wrong? OpenFOAM seems to be running ok but paraFoam command is generating the error.

mgz1985 July 20, 2008 04:42

sorry for not giving you my re
 
sorry for not giving you my results for 1.5

I tried it too but it does not work too. it is not compiling on my system as i cant unzip my gtgz files and when i download the patches their format changes from patch to unk..(i am very new to UNIX and openFoam so please be patient)

referring to my above note. I have created the softlinks for paraview and openfoam disk images in my openfoam directory. how and where do i put Takuya's patch for paraview (they are also downloaded as unk format. is it in the disk image of paraview or where i downloaded. probably the error could be here....

thanks.

podallaire July 20, 2008 08:52

Francesco, XCode can be dow
 
Francesco,

XCode can be downloaded from : http://connect.apple.com/cgi-bin/Web...MemberSite.woa

You need to register first, it's free. After, you go in Download section and you'll find it.


mayank, I cannot give you support on paraFoam since I don't use it. You can post a question in the appropriate thread:

http://www.cfd-online.com/OpenFOAM_D...tml?1216547856

I'm aware of the "hunk" extension when downloading - just rename the file with the right extension and decompress after. To apply Takuya's patch, you need to download the source code with cvs and follow the procedure to compile Paraview. Qt and cmake are required. Please look at :

http://www.paraview.org/New/download.html (see current development distribution section)

http://paraview.org/Wiki/ParaView:Build_And_Install

Pierre-Olivier

mgz1985 July 20, 2008 09:11

thanx PO for ur help and patie
 
thanx PO for ur help and patience..

If you do not use paraFoam then how do you visualize your results. As I am getting no where with paraFoam, i think i can follow your lead.

podallaire July 20, 2008 09:34

You can open an OpenFOAM case
 
You can open an OpenFOAM case directly with Paraview3.3 if you use Takuya's patch. Still, you need to compile it from sources. Please take a look at :

http://www.cfd-online.com/OpenFOAM_D...tml?1211418745
http://www.cfd-online.com/OpenFOAM_D...tml?1216503048

Another otpion is to convert the results to VTK files using the command foamToVTK than you can open direclty vtk files with pre-compiled Paraview.

Hope this helps,

Pierre-Olivier

mgz1985 July 20, 2008 09:52

thanx a lot PO... i shall t
 
thanx a lot PO...

i shall try the latter option as i m very bad at computers..i cant tr the thing today but shall try it tomorrow and let you know...

regarding the second option, my command shuld be as underneath or not

foamtoVTK <root> <case>

i hope it works...just as a backup if i have to compile then at the paraview website, the software is in gtgz or tgz extension. how do i extract it from there coz tar is not being accepted by my system

egp July 20, 2008 16:32

Bernhard and Pierre-Olivier,
 
Bernhard and Pierre-Olivier,

Good job on the patches and documentation!!

OpenFOAM-1.5 compiles on my Intel MacPro with: OSX 10.5.4, gcc-4.2.1, and openmpi-1.2.3 (in /usr/lib/openmpi).

I've run through a few serial and parallel test cases, and all seems to be working OK.

Eric

gschaider July 21, 2008 04:55

Hi! Back from the weekend a
 
Hi!

Back from the weekend and I'm bringing a new patch with me. This one helps to run paraFoam (some workarounds are needed with the plugins otherwise paraview chokes on the "regular" OpenFoam-libraries):

http://www.cfd-online.com/OpenFOAM_D...hment_icon.gif OpenFOAM-1.5-Mac-v2.patch

Compiling of the PV-plugin should work as described in the Release notes. Compilation of paraview worked without bigger problems. Just some remarks on compiling paraview:
- I used the last Release of QT 4.3.x from Trolltech as this was recommended (didn't feel liker trying 4.4 since paraview seems to be very sensitive about versions)
- Propably compilation will fail at 66% (something about a missing QtAssisent-stuff missing). Go to the platforms/darwinYourArch-directory. There do "ccmake ." and look for the QT_QTASSISTANT-settings. Set them by hand (this seems to be a problem with the Trolltech-releases). Go back to the Paraview-directory. There rerun "build_paraview 1". The 1 (or any other argument) is important as it stops the script from clearing what was built so far
- Don't forget to switch on Python before compiling Paraview unless you want to miss the coolest thing about paraview3

@Pierre-Olivier's question about funkySetFields: I'm afraid it is not yet ready for 1.5 and I propably won't have time to port it this week. For the time being you'll have to run its 1.4.1-incarnation

@Pierre-Oliver's reporting of the 32-architecture: s###. I didn't realize that of course that darwin exist in 64 AND 32 bits on intel. That would make all the #ifdefs rather bloated, And there doesn't seem to be a need to distinguish between architectures on Darwin. So unless somebody with a 64-Intel (Eric?) reports problems I think we should stick with darwinPpc/darwinIntel (reverting the patch back to just one darwin-platform would only confuse the general public I think)

Bernhard


Bernhard

podallaire July 21, 2008 15:09

Hi Bernhard, thanks for the
 
Hi Bernhard,

thanks for the patch ! I was able to compile a fresh cvs version of Paraview3. The Paraview 3 app works; however, it crashes when I try to open an OpenFOAM case or with paraFoam. I will try to compile the version provided in "ThirdParty" directory with the "buildParaview3.3-cvs" scipt. Not sure what is the problem with the new PV3Foam libs.

You can comment line 94 in ParaView3.3-cvs/CMakeLists.txt to be able to use QT 4.4.

It's a really good thing to have both darwinppc and darwinintel. This way, I can compile both architecture on the same disk image.

Best regards,

PO

gschaider July 22, 2008 09:07

Hi PO! Concerning the archi
 
Hi PO!

Concerning the architectures: the Apple-compiler allows to specifiy multiple architectures "-arch ppc -arch i386". According to the man-page it then produces a universal binary that runs on both architectures. You'll only have to compile once, but the binaries will be a bit bloated

@paraview crash: make sure that the PV_PLUGIN_PATH points to a directory where only the two libPV3*.dylib-files reside (all other OF-dylibs will make paraview crash). Try loading the two dylibs by hand from the Plugin-Manager (if they fail you should get an error message)

Bernhard

podallaire July 22, 2008 09:28

Good morning Bernhard (is it t
 
Good morning Bernhard (is it the morning fo you ?),

Yes, you are right, an universal binary can be compiled - never tried with OF but it's a very good idea.

Since I built a "bundle" of paraview (paraview.app), my PV_PLUGIN_PATH variable was not set properly because I was not launching the app from a shell (double-click on icon). I tried from the shell and it worked. I found the PV3FoamReader unstable - I'll stick with the native reader developed by Takuya for now which is pretty much the same thing but really more stable.

Thanks and have a good day !

PO

xiaohezhu July 22, 2008 10:25

Hello everyone, this is the f
 
Hello everyone,
this is the first time for me to use message board,I hope someone can help me .
I want to download openfoam-1.5,but I tried many times and failed.I can't link the source pack and binary pack.Could any one send me this software?I just need the source pack and binary pack double precision.Thanks.

podallaire July 22, 2008 10:48

Hi Zhanting, you need to do
 
Hi Zhanting,

you need to download two files available from OpenFOAM website :

- OpenFOAM-1.5.General.gtgz
- ThirdParty.General.gtgz

Follow the instructions to unpack those files. After, you can apply the patches provided by Bernhard - just follow the instructions in this thread. As mentionned, you need to create a case-sensitive image file to run OpenFoam on a Mac; use DiskUtility to do so. You'll need to move the *.gtgz file in the image before decompressing.

Good luck !

PO

lin July 22, 2008 11:03

Hi Zhanting If I got y
 
Hi Zhanting
If I got your meaning correctly,it's because some kind problems internet connection.You fail to download the files. I have downloaded the files and upload to a file-share server. If you left your email address,I could send you the link.

gschaider July 22, 2008 11:06

Thanks for mentioning it, PO:
 
Thanks for mentioning it, PO: paraview ALWAYS builds itself as a bundle. To get the paraFoam script to work one has to put a symbolic link to the actual binary (which is in paraview.app/Contents/MacOSX/paraview or so) in the paraview-bin-directory

Bernhard

xiaohezhu July 22, 2008 21:09

Hi Pierre,linzhenhua, Thank y
 
Hi Pierre,linzhenhua,
Thank you!

Now my problem is that I can't link the following files
- OpenFOAM-1.5.General.gtgz
- ThirdParty.General.gtgz

so I can't unpack those files .Maybe there is some problem with my internet.

my email box is zhangting198642@163.com. I just need the source pack OpenFOAM-1.5.General.gtgz
and binary pack double precision OpenFOAM-1.5.linuxGccDPOpt.gtgz .Thanks .

podallaire July 22, 2008 22:23

Bernhard, is there a way to
 
Bernhard,

is there a way to "bundle" with paraview.app the 3 libs (libvtkPV3Foam.dylib, libPV3FoamReader_SM.dylib and libPV3FoamReader.dylib) in order to have a standlone paraview.app ? The doc says that plugins can be loaded automatically from paraview.app/Contents/MacOS/plugins but I'm not sure where libvtkPV3Foam.dylib should be copied - in paraview.app/Contents/MacOS ? I tried without success ...

Here is what I tried tonight :

1) sh Applications/Client/CreateBundle.sh to create the final paraview.app
2) After moving my paraview.app in /Applications, I created /Applications/paraview.app/Contents/MacOS/plugins where I copied the PV3 libs.
3) When trying to launch paraview.app (double-click), it crashes ...
4) I moved /Applications/paraview.app/Contents/MacOS/plugins/libvtkPV3Foam.dylib to /Applications/paraview.app/Contents/MacOS
5) Crashes again when trying to launch the app

Thanks

PO

kjmaki July 22, 2008 22:51

Dear FOAMers, I am trying t
 
Dear FOAMers,

I am trying to build 1.5 on my mac (10.5.4), and the build process stops on the OpenFOAM library. I have applied the 3 patches supplied by Bernard above in this thread. It appears that pointFields is dependent upon cpuTime.H, and is looking for it in the OpenFOAM/lnInclude directory, but I see that cpuTime.H resides in the OSspecific/Unix directory. Here is the output from the compile log:

+ wmake libo OSspecific/Unix
'/Users/kjmaki/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libOSspecific.o' is up to date.
+ wmake libso OpenFOAM
make: *** No rule to make target `/Users/kjmaki/OpenFOAM/OpenFOAM-1.5/src/OpenFOAM/lnInclude/cpuTime.H', needed by `fields/GeometricFields/pointFields/pointFields.dep'. Stop.

Then, a little further down the line, I get the all-to-familiar "library not found" errors such as:

+ wmake libso dynamicFvMesh
ld: library not found for -ltriSurface
collect2: ld returned 1 exit status
make: *** [/Users/kjmaki/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libdynamicFvMesh.dylib ] Error 1
+ wmake libso topoChangerFvMesh
ld: library not found for -lfiniteVolume
collect2: ld returned 1 exit statusmake: *** [/Users/kjmaki/OpenFOAM/OpenFOAM-1.5/lib/darwinIntelDPOpt/libtopoChangerFvMesh.d ylib] Erro
r 1

Has anyone else had this problem, or could someone suggest how I might fix this?

Thanks for your help!

Kevin

podallaire July 23, 2008 00:19

Kevin - are you compiling in a
 
Kevin - are you compiling in a case-sensitive image (just want to make sure) ?

gschaider July 23, 2008 04:28

@the bundling issue: one of th
 
@the bundling issue: one of the plugin-dylibs needs the OF-Libraries. Usually the won't be in the DYLIB_LIBRARY_PATH for applications started from the GUI (and I DON'T RECOMMEND ADDING THEM). Therefor they will only work for a paraview started from a shell with the correct paths set

@kevins compilation problem: what is strange is that it looks for cpuTime.H in the OpenFOAM/lnInclude when it has moved to OSspecific/Unix/lnInclude in 1.5. You're sure that there are no residuals from a pre-1.5-installation? Just to make sure remove all dep-files with
find $FOAM_SRC -name "*.dep" -exec rm {} \;
and recompile (check the command before using it, the message board software is surly going to do something very ugly to it)

Bernhard

kjmaki July 23, 2008 06:56

Dear PO and Bernard, Thanks
 
Dear PO and Bernard,

Thanks for your help!

I think the issue was that I had some remnants from my 1.4.1 installation.

Kevin

fra76 July 23, 2008 14:49

Hi all, After a couple of fai
 
Hi all,
After a couple of failed attempts, I've carefully followed the steps suggested by Pierre-Olivier, with Bernhard's patches, but I'm still having the same problem when wmake tries to resolve dependencies. For example:

Making dependency list for source file solidBodyMotionFvMesh/solidBodyMotionFunctions/solidBodyMotionFunction/newSolidB odyMotionFunction.C
could not open file lduMesh.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file fvBoundaryMesh.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file surfaceInterpolation.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file DimensionedField.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file volFieldsFwd.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file surfaceFieldsFwd.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file slicedVolFieldsFwd.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file slicedSurfaceFieldsFwd.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file fvPatchFvMeshTemplates.C for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file solidBodyMotionFunction.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file addToRunTimeSelectionTable.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file volFields.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file mathematicalConstants.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C
could not open file transformField.H for source file solidBodyMotionFvMesh/solidBodyMotionFvMesh.C


When it compiles, however, the -I options seem correct:

SOURCE=solidBodyMotionFvMesh/solidBodyMotionFunctions/solidBodyMotionFunction/ne wSolidBodyMotionFunction.C ; g++-4.2 -DdarwinIntel -DDP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -O3 -DNoRepository -ftemplate-depth-40 -I/Volumes/OpenFOAM/OpenFOAM-1.5/src/triSurface/lnInclude -I/Volumes/OpenFOAM/OpenFOAM-1.5/src/meshTools/lnInclude -I/Volumes/OpenFOAM/OpenFOAM-1.5/src/dynamicMesh/lnInclude -I/Volumes/OpenFOAM/OpenFOAM-1.5/src/finiteVolume/lnInclude -IlnInclude -I. -I/Volumes/OpenFOAM/OpenFOAM-1.5/src/OpenFOAM/lnInclude -I/Volumes/OpenFOAM/OpenFOAM-1.5/src/OSspecific/Unix/lnInclude -fPIC -Ddarwin -c $SOURCE -o Make/darwinIntelDPOpt/newSolidBodyMotionFunction.o



The compilation is still going, but I'm afraid it will fail again. I guess I have something wrong in some environment variable, but I cannot find anything strange...

Any suggestion?

podallaire July 23, 2008 15:00

Hi Francesco, I'm not sure
 
Hi Francesco,

I'm not sure what is the problem. Here are some thoughts ...

A) Did you "link" the OpenFOAM-1.5 and Thirdparty directories in your ~/OpenFOAM/ ?

Here is what I made before compiling :

1) mkdir ~/OpenFOAM (might already exists in your case)
2) ln -s /Volumes/OpenFOAM/OpenFOAM-1.5 ~/OpenFOAM/OpenFOAM-1.5
3) ln -s /Volumes/OpenFOAM/ThirdParty ~/OpenFOAM/ThirdParty

Bernhard - if those links are not set, can it affect the compilation ?

B) Did you extract the *.tgz in /Volumes/OpenFOAM directly (case-sensitive) ?

PO

fra76 July 23, 2008 15:17

Hi Pierre Olivier, what I'm u
 
Hi Pierre Olivier,
what I'm used to do, in order to have multiple installations on the same (linux, up to now) machine, is to create specific files to be sourced when needed.
In this case, I've created a file containing:

export FOAM_INST_DIR=/Volumes/OpenFOAM
export WM_PRECISION_OPTION=DP
export WM_NCOMPPROCS=2
. /Volumes/OpenFOAM/OpenFOAM-1.5/etc/bashrc

and the I've sourced it.

Now, for example, FOAM_INST_DIR is /Volumes/OpenFOAM, FOAM_SRC is /Volumes/OpenFOAM/OpenFOAM-1.5/src, WM_THIRD_PARTY_DIR is /Volumes/OpenFOAM/ThirdParty and so on.

I extracted the *.gtgz files directly in that directory, from the command line, to avoid any possible case problem in the file names.

Francesco

podallaire July 23, 2008 15:24

... hey, in fact, those "Makin
 
... hey, in fact, those "Making dependency list" and "could not open file" messages are ok - it's just "getting" the needed source files to compile.

everything is fine !

fra76 July 23, 2008 16:49

Just to say that I was a bit p
 
Just to say that I was a bit pessimistic.
It works!
I'll do some tests as soon as possible...

Thanks mate!

egp July 23, 2008 17:04

I can confirm PO's observation
 
I can confirm PO's observation. I got the same messages, and everything compiled and appears to be running just fine.

Eric

fra76 July 24, 2008 14:52

Paraview compiled as well! Tha
 
Paraview compiled as well! Thanks for all the suggestions above!

The only issue I've found is that I don't have the time step selection. I can only visualize the first saved time step, but not the others. I've tried only on the simpleFoam/pitzDaily tutorial, but it should not make any difference.

Does anyone else have the same problem?

Francesco

podallaire July 24, 2008 15:18

I don't have this problem.
 
I don't have this problem.

I tried with a case where I have 0, 300, 500 and 800 as my time steps and it worked.

Regards,

PO

fra76 July 25, 2008 14:06

Found, time selection is there
 
Found, time selection is there, it's simply different from previous releases...

Thanks,
Francesco

kjmaki July 28, 2008 00:48

Dear FOAMers, I am close to
 
Dear FOAMers,

I am close to being able to use paraFoam on my mac, but still no cigar. I applied Bernard's patch. I installed qt 4.3.4. I have built paraview3.3-cvs with no failure. Then I went to $FOAM_UTILITIES/postProcessing/graphics/PV3FoamReader and did the Allwclean and Allwmake. Finally, I placed a link in the OpenFOAM/OpenFOAM-1.5/bin directory to the location of the paraview executale.

When I launch paraFoam from a case directory, it fails giving me the message

"terminate called after throwing an instance of 'std::length_error'"

After sifting through the forums, I have investigated the following items.

1. I have only one PV library

ls lib/darwinIntelDPOpt/*PV*
lib/darwinIntelDPOpt/libvtkPV3Foam.dylib

I should have one other paraview 3 library, right?

2. I have tried to load this library via the plugin loader in paraview, and it says no because it is not a valid Qt plugin.

Does anyone have any suggestions?

Thanks!

Kevin


All times are GMT -4. The time now is 08:23.