How to install Paraview in personal home directory of a cluster

Hi there,

I am Sahel, a new user of Paraview. Recently, I am trying to install Paraview 5.8 in my personal home directory of the DELL visualization server machine. I have downloaded the tar file and tried to install it. As I am not super user, I can’t softlink
ParaView-5.8.0-MPI-Linux-Python3.7-64bit/bin/paraview to /usr/bin/paraview &
ParaView-5.8.0-MPI-Linux-Python3.7-64bit//lib/paraview-5.8/ to /usr/lib/paraview-5.8
to invoke paraview from terminal. Is it possible to install it this way to use remotely?

 Paraview 5.0 is already installed there for all users with required dependencies but for some reason, the graphical interface is getting hanged every time. Therefore, I am trying to install it in my home space. 

It would be helpful if you can give me some suggestions to resolve this issue.

Thank you.
Best Regards,

Welcome to ParaView, Sahel.

Yes, you can definitely untar the file you downloaded in any directory in which you have access and run it from there, unless for some reason your system disallows running executables from arbitrary directories. Either give the full path to the executable you want to run, or add that directory to your PATH environment variable.

Thanks a lot Cory for your reply. I was trying to set path for invoking Paraview. After setting path, again I am getting some errors. Can you please check it ?

Thank you
( 1.151s) [paraview ]vtkXOpenGLRenderWindow.:637 ERR| vtkXOpenGLRenderWindow (0x249e3b0): Cannot create GLX context. Aborting.

( 1.151s) [paraview ]vtkXOpenGLRenderWindow.:637 ERR| vtkXOpenGLRenderWindow (0x249e3b0): Cannot create GLX context. Aborting.

Loguru caught a signal: SIGABRT
Stack trace:
32 0x407a7d paraview() [0x407a7d]
31 0x7fde47692505 __libc_start_main + 245
30 0x407734 paraview() [0x407734]
29 0x40c502 paraview() [0x40c502]
28 0x408939 paraview() [0x408939]
27 0x7fde4730b4d1 pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) + 1041
26 0x7fde47281ea5 pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) + 293
25 0x7fde47281d14 pqAlwaysConnectedBehavior::serverCheck() + 132
24 0x7fde45e9b8a7 pqObjectBuilder::createServer(pqServerResource const&, int) + 199
23 0x7fde445c7749 vtkSMSession::ConnectToSelf(int) + 105
22 0x7fde43cc7a3e vtkProcessModule::RegisterSession(vtkSession*) + 142
21 0x7fde3e8636c6 /mnt/lustre/phy3/physahel/pencil-code/sahel/ParaView-5.8.0-MPI-Linux-Python3.7-64bit/bin/…/lib/ [0x7fde3e8636c6]
20 0x7fde3e6f6c99 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
19 0x7fde44ac6c7c /mnt/lustre/phy3/physahel/pencil-code/sahel/ParaView-5.8.0-MPI-Linux-Python3.7-64bit/bin/…/lib/ [0x7fde44ac6c7c]
18 0x7fde44ab2947 /mnt/lustre/phy3/physahel/pencil-code/sahel/ParaView-5.8.0-MPI-Linux-Python3.7-64bit/bin/…/lib/ [0x7fde44ab2947]
17 0x7fde4521ac47 QMetaObject::activate(QObject*, int, int, void**) + 1511
16 0x7fde45e3bd09 /mnt/lustre/phy3/physahel/pencil-code/sahel/ParaView-5.8.0-MPI-Linux-Python3.7-64bit/bin/…/lib/ [0x7fde45e3bd09]
15 0x7fde45e37452 pqServerManagerObserver::connectionCreated(long long) + 50
14 0x7fde4521ac47 QMetaObject::activate(QObject*, int, int, void**) + 1511
13 0x7fde45ee89a2 pqServerManagerModel::onConnectionCreated(long long) + 770
12 0x7fde45e362c2 pqServerManagerModel::serverAdded(pqServer*) + 50
11 0x7fde4521ac47 QMetaObject::activate(QObject*, int, int, void**) + 1511
10 0x7fde472ce173 pqDefaultViewBehavior::onServerCreation(pqServer*) + 67
9 0x7fde444e4b62 vtkPVSessionCore::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) + 34
8 0x7fde444e49f3 vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned int) + 115
7 0x7fde3a2acb49 vtkPVRenderingCapabilitiesInformation::CopyFromObject(vtkObject*) + 9
6 0x7fde3a2acb05 vtkPVRenderingCapabilitiesInformation::GetLocalCapabilities() + 405
5 0x7fde4249f46d vtkOpenGLRenderWindow::SupportsOpenGL() + 973
4 0x7fde42542cb2 vtkXOpenGLRenderWindow::WindowInitialize() + 18
3 0x7fde42546491 vtkXOpenGLRenderWindow::CreateAWindow() + 1921
2 0x7fde476a7a28 abort + 328
1 0x7fde476a6337 gsignal + 55
0 0x7fde476a63b0 /lib64/ [0x7fde476a63b0]
( 1.151s) [paraview ] :0 FATL| Signal: SIGABRT
Abort (core dumped)

Since ParaView 5.0 is already installed, I assume that means it is officially supported by your organization. I suggest you contact the system administrators for technical help on getting either 5.0 or 5.8 working.

Thanks Cory. I will try to figure it out with them.