[keepfit]

Hi Foamers,

I just downloaded the latest version of OpenFOAM v2106. No problem for compilation of OpenFOAM, but for ThirdParty-v2106, after doing $./Allwmake, a lot of error in the process of $./makeParaView, mainly due to VTK source files.

Note that Qt 5.12.8 is already installed in Ubuntu 20.04. Paraview 5.9.1 seems need "VTK-8.2.0" as I tried $./makeVTK. In this case, should I download vtk 8.2 source code, or the code is already included in the paraview folder?

If ./makeParaview just loads the system vtk library (Ubuntu 20.04: only libvtk-7.1 available), then should we try to install the libvtk8.2 instead?

Update 1:

After downloading vtk 8.2.0 source code and successfully compiled it in the ThirdParty folder, still could not run "makeParaView", some of the errors shown below (mostly VTK related):

makeParaView errors


Update 2:

Instead of installing Paraview 5.9.1 which is not possible for me at the moment, old ThirdParty-v2012.tgz can be used for the new OpenFOAM-v2106: unzip it and change ThirdParty-v2012 to ThirdParty-v2106. Then in the ThirdParty-v2106 folder we need to change ParaView-v5.6.3 to ParaView-v5.9.1 as well. "makeParaView" will compile! One minor issue is that you might need to do "paraFoam -vtk" to visualize your OF results.

Download ThirdParty-v2012.tgz here.

Update 3:

In order to run "paraFoam" (paraview 5.6.3) without any error for the new OpenFOAM:

cd $WM_PROJECT_DIR/modules/visualization/src/paraview-plugins
./Allwclean
./Allwmake

then set PV_PLUGIN_PATH in "~/.bashrc". Here"USER" is the name of your home folder (user name).

export PV_PLUGIN_PATH=/home/USER/OpenFOAM/USER-v2106/platforms/linux64GccDPInt32Opt/lib/paraview-5.6

Conclusion:

For those who have issues on compiling ThirdParty-2106 at the moment, the old version ThirdParty-2012 can be still used for the OF-v2106 with some tricks. Later on if there are some easy solutions for the paraview 5.9.1, we can still switch back to the lastest version of ThirdParty-v2106.

As olesen mentioned, you can also use binary version of paraview (5.9.1), with a xxx.foam file created at the case folder. Because OpenFOAM (*.foam) file is supported. Nevertheless, in ubuntu OS, binary version is a bit slow to open, and font size is too small when you open the menu, compared to compiled version.

[olesen]

Originally Posted by keepfit

Conclusion:

For those who have issues on compiling ThirdParty-2106 at the moment, the old version ThirdParty-2012 can be still used for the OF-v2106 with some tricks. Later on if there are some easy solutions for the paraview 5.9.1, we can still switch back to the lastest version of ThirdParty-v2106.

Will need to take a look. But can also simply use the system paraview (I really don't know why everyone wants to compile paraview themselves).

[olesen]

Originally Posted by keepfit

...

Note that Qt 5.12.8 is already installed in Ubuntu 20.04. Paraview 5.9.1 seems need "VTK-8.2.0" as I tried $./makeVTK. In this case, should I download vtk 8.2 source code, or the code is already included in the paraview folder?

The compilation of VTK and ParaView are two completely different things. Can override the version defaulted inside of the makeVTK script, either from the command-line and/or by changing the corresponding etc/config.sh entry.


You do not need to compile a separate VTK for ParaView, it's already part of the ParaView sources. The separate VTK library is for more special applications where you want a particular LLVM pipeline with MESA and a specific MPI etc. Consider it to be an "advanced" item.


Since you are on Ubuntu, I would suggest that you use the precompiled packages anyhow. Can still sort out your ParaView requirements after that.

[keepfit]

Originally Posted by olesen

Will need to take a look. But can also simply use the system paraview (I really don't know why everyone wants to compile paraview themselves).

Only way is to convert foam results to VTK if binary paraview is used. When you link binary paraview to ParaFoam, it seems you can NOT "play" the results in paraview. It will crash.

Plus, compiled one seems a bit faster to open, and font size in paraview menus is consistent, not like in the binary version.

[olesen]

Originally Posted by keepfit

Only way is to convert foam results to VTK if binary paraview is used. When you link binary paraview to ParaFoam, it seems you can NOT "play" the results in paraview. It will crash.

If you touch a file with the extension '.foam' (eg "touch case.foam") opening that with paraview uses the native ParaView/VTK reader for OpenFOAM data - you don't really need "paraFoam" at all.


https://discourse.paraview.org/t/i-w...uld-i-use/7232


What type of "crash" are you seeing? The term is pretty generic.

[keepfit]

Originally Posted by olesen

If you touch a file with the extension '.foam' (eg "touch case.foam") opening that with paraview uses the native ParaView/VTK reader for OpenFOAM data - you don't really need "paraFoam" at all.


https://discourse.paraview.org/t/i-w...uld-i-use/7232

What type of "crash" are you seeing? The term is pretty generic.

Hate to create a *.foam file every time when you run a new case.

Paraview crashes when I make a link in system bin folder:

sudo ln -s /path_binary_paraview/bin/paraview /usr/bin/paraview

You could run paraFoam in this case, but when you press the "play" button, a lot of error info pop up, and paraview just crashes.

[olesen]

Originally Posted by keepfit

Hate to create a *.foam file every time when you run a new case.

I have

alias parafoam='touch case.foam; paraview case.foam'

works even without having an OpenFOAM environment

[olesen]

Originally Posted by keepfit

Paraview crashes when I make a link in system bin

I remember something like that too. Might need to check with the discourse forum too, but you should note the the binaries ship with a "paraview" and "paraview-real" that tries to resolve the sibling lib directories. Your link is very likely breaking all of that.
As a first step, try just adding the paraview/bin directory into your PATH (and remove the link).

When trying out different combinations, I've also just used an alias for paraview too:

alias paraview='/install/path/xxx/bin/paraview'

[keepfit]

Originally Posted by olesen

I remember something like that too. Might need to check with the discourse forum too, but you should note the the binaries ship with a "paraview" and "paraview-real" that tries to resolve the sibling lib directories. Your link is very likely breaking all of that.
As a first step, try just adding the paraview/bin directory into your PATH (and remove the link).

When trying out different combinations, I've also just used an alias for paraview too:

alias paraview='/install/path/xxx/bin/paraview'

I had no success with this method ever . I remembered we still need parameters behid the path.

alias ParaView59='HOME_PATH/Tools/ParaView59/bin/paraview'

$ ParaView59

double free or corruption (out)

Loguru caught a signal: SIGABRT

Same error pops out when you navigate to the parview's bin folder in Terminal and run

$ cd /HOME_PATH/Tools/ParaView59/bin
[bin] $ ./paraview

But when you double-click "paraview" in the binary paraview's "bin" folder, no issues at all.