New to Paraview application

(Murdock McCormick, Jr.) #1

Good morning, I am new to ParaView. I am researching it with plans in mind to install a newer version of the sw on a RHEL 6.5 (I think) cluster environment. What version of ParaView will run on RHEL 6.5, v5.6 or should I grab a previous version? Thanks

(Mathieu Westphal (Kitware)) #2

Welcome to the ParaView community !

the release of ParaView is actually builded on a Centos 6, which is quite close.
v5.6 should work fine.

(Murdock McCormick, Jr.) #3

Awesome, thanks.

(Murdock McCormick, Jr.) #4

I was told I needed to build ParaView from scratch, currently the old version is causing issues, ver. 3.x. I plan to build it in a test environment first to work out any issues. Is it recommended to use the ParaView Superbuild option?


(Mathieu Westphal (Kitware)) #5

Unless you need specific options or plan on building custom C++ plugin or application, building is not required.

If you still need to build it, the superbuild is indeed the easiest way to go, especially if you require certains optional depends.

(Murdock McCormick, Jr.) #6

I was told building was required in my case. I’ll have to ask the guys that are requesting this install. My thinking is they recommend building it because of the package dependencies may not be on the existing system.

(Mathieu Westphal (Kitware)) #7

The release comes with all the dependencies built-in.

1 Like
(Walter Alan Scott) #8

Welcome to the community!

I’m wondering if you mean you need to run the ParaView backend in parallel on a cluster (i.e., your first post). This would make sense if you are being told to build ParaView from source. Although I have never tried it, Kitware is now providing binaries that should work here. (I suspect this is what Mathieu is talking about). See the Linux downloads with osmesa in the name. Would that work? If you do need to build, use Superbuild. Version 5.6.0 is a good version to install. 5.5.2 is also being spectacular. Build directions are here: Although a bit rough around the edges, connection setup can be found here:

(Murdock McCormick, Jr.) #9

What we will have in the end will be Windows clients running a version of ParaView, 5.6, and the RHEL6.5 cluster running a version of ParaView, 5.6. So in that scenario, would we need to build the sw on the Linux cluster from scratch?

(Cory Quammen (Kitware)) #10

No, you should be able to use the precompiled binaries from for both the client on Windows and server on Linux.

(Murdock McCormick, Jr.) #11

Sorry, been absent for awhile. Can someone please tell me the difference between the osmesa download vs. the other option available for Linux? What reason would someone build Paraview from scratch?

(Cory Quammen (Kitware)) #12

The osmesa package contains only the ParaView server and uses mesa for rendering. It does not need an X server to generate graphics.

The other download contains the full ParaView suite, including the desktop application. Both client and server require an X server to generate images.

You would build ParaView to use an MPI implementation with support for proprietary communications hardware, for developing ParaView, developing a custom plugin, or providing executables on a system with an OS or hardware not compatible with the precompiled linux binaries.

(Mathieu Westphal (Kitware)) #13

We need to fix that naming issue.

(Cory Quammen (Kitware)) #14

@jourdain How hard would it be to add a description section (maybe an expandable section) under each download on

(Sebastien Jourdain) #15

Not too long… We should also include the server section so EGL/OSMesa could be part of the same group and not mixed with the PV app.

1 Like
(Cory Quammen (Kitware)) #16

Good idea.

(Walter Alan Scott) #17

What Cory said. I like your idea Seb.

(Murdock McCormick, Jr.) #18

That sounds extremely helpful. I installed the Pamela ver. of the app on my RHEL cluster server and win10 client. I am currently waiting on customer testing. I’ll let you know what happens.

(Cory Quammen (Kitware)) #19