I have compiled Paraview on Cray XC40 (SahasraT at SERC in India) for Haswell compute nodes.
Following are the compile options used: config.sh (2.0 KB) paraview-cray-serc.cmake (3.0 KB)
After a successful compilation I submitted an interactive job script as follows: qsub -I -N PARAVIEW_VIS -l select=2:ncpus=24:mpiprocs=24,walltime=24:00:00,place=scatter,accelerator_type="None"
Once inside the assigned node, I executed the following:
@cory.quammen You have provided me with a lot of help on compiling Paraview but now the compiled binary cannot setup a Paraview server. Can you help me with this issue?
Sure. Take a look at this presentation on how to connect to a remote server. It covers the basics and dealing with more advanced topics such as reverse connections and SSH tunneling.
@cory.quammen
On submitting a job script to my Cray system I don’t get the expected output (the ip of pvserver waiting for client). Instead it almost immediately stops with the following output in connection_info.out file :
@cory.quammen
If you see my config.sh script, I used that for compiling Paraview after loading the modules. I am now loading exactly the same version of the modules as in the config.sh script before trying to run pvserver. I’m absolutely stuck and any help will be a real lifesaver.
@cory.quammen
Thanks for helping me out. Your suspicion was right. It seemed to be a problem how Cray was configured in my institute by the admins. I have no idea why they installed mvapich2 and even added that to path. As a result, Paraview compile scripts were detecting that making the binaries generated incompatible with aprun. Adding -DMPIEXEC_EXECUTABLE=$(which aprun) to cmake argument and also in genericio.cmake file in paraview-superbuild solved the issue. Thanks a lot once again.