Changes between Version 6 and Version 7 of ParaView/SampleVNCParaViewSessionJURECA


Ignore:
Timestamp:
06/01/16 13:19:39 (8 years ago)
Author:
Sonja Habbinga
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ParaView/SampleVNCParaViewSessionJURECA

    v6 v7  
    1919 * large memory
    2020 * no batch job needed
    21  * no accounting
    22  * pvserver may run in parallel on JURECA's compute nodes or visualization nodes
     21 * no accounting (unless you start a parallel pvserver)
     22 * pvserver may run in parallel on JURECA's [#SampleParaViewSessionJURECAComputeNodes compute nodes] or [#SampleParaViewSessionJURECAVisualizationNodes visualization nodes]
    2323}}}
    2424{{{#!td
     
    3737 * rendering on GPU
    3838 * large memory
    39  * pvserver may (should!) run in parallel on JURECA's visualization nodes
     39 * pvserver may (should!) run in parallel on JURECA's visualization nodes as described [#SampleParaViewSessionJURECAVisualizationNodes here].
    4040 * ParaView GUI client and pvserver running on the same node, => connect to localhost:11111
    4141}}}
     
    4444}}}
    4545
    46 == Start !ParaView on the remote desktop
     46== Starting the !ParaView GUI on the remote desktop
    4747In case you startet the VNC server with the option '-profile vis', your VNCViewer should look like this:
    4848
     
    5151Now, just double-click on the ParaView-Icon to start the ParaView client.
    5252
     53== [=#SampleParaViewSessionJURECAComputeNodes] Starting a pvserver on JURECA's compute nodes
    5354
     55In this section we show how to use ParaView's server side rendering capabilities on JURECA's '''compute nodes''' in a sample session step by step.
     561. Open a terminal and load the modules providing the ParaView software
     57{{{
     58bash-4.2$ module load Stages/Current intel-para ParaView/5.0.1-OSMesa
     59}}}
    5460
     612. Next, we allocate some resources for our ParaView server, and run the ParaView server (in this example session on 1 node, using 24 tasks)
     62{{{
     63bash-4.2$ salloc --partition=devel --nodes=1 --time=00:20:00
     64salloc: Pending job allocation 1711109
     65salloc: job 1711109 queued and waiting for resources
     66salloc: job 1711109 has been allocated resources
     67salloc: Granted job allocation 1711109
     68bash-4.2$ srun --nodes=1 --ntasks=24 pvserver
     69}}}
     70
     71 which will produce the following output from the ParaView server:
     72{{{
     73Waiting for client...
     74Connection URL: cs://jrc0036:11111
     75Accepting connection(s): jrc0036:11111
     76}}}
     77 where
     78{{{
     79jrc0036:11111
     80}}}
     81 is the hostname and portnumber on JURECA the server will listen to.
     823. As a next step, click the Connect button in the ParaView GUI and configure a server with the corresponding hostname and portnumber as described [wiki:SampleParaViewSessionJURECA#connectToServer here]
     83
     84== [=#SampleParaViewSessionJURECAVisualizationNodes] Starting a pvserver on JURECA's visualization nodes
     85
     86In this section we show how to use ParaView's server side rendering capabilities on JURECA's '''visualization nodes''' in a sample session step by step.
     871. open a terminal and load the modules providing the ParaView software
     88{{{
     89bash-4.2$ module load Stages/Current intel-para ParaView
     90}}}
     91and set the DISPLAY environment variable as follows
     92{{{
     93bash-4.2$ export DISPLAY=:0.0
     94}}}
     952. Next, we allocate some resources for our ParaView server (this step has to be omitted in case you started a VNC session on the visualization batch nodes via strudel, since strudel allready allocated some resources for you)
     96{{{
     97bash-4.2$ salloc -N 2 -p vis --gres gpu:2 --start-xserver     
     98}}}
     99 and run the ParaView server (in this example session on 2 nodes, using 48 tasks):
     100{{{
     101bash-4.2$ srun --cpu_bind=none --ntasks=48 --gres=gpu:0 vglrun pvserver --use-offscreen-rendering
     102}}}
     103
     104 which will produce the following output from the ParaView server:
     105{{{
     106Waiting for client...
     107Connection URL: cs://jrc1391:11111
     108Accepting connection(s): jrc1391:11111
     109}}}
     110 where
     111{{{
     112jrc1391:11111
     113}}}
     114 is the hostname and portnumber on JURECA the server will listen to.
     1153. As a next step, click the Connect button in the ParaView GUI and configure a server with the corresponding hostname and portnumber as described [wiki:SampleParaViewSessionJURECA#connectToServer here]
     116