Commit 7ec0d98f authored by Petr Strakos's avatar Petr Strakos

final

parent 3c0ee0a9
......@@ -90,13 +90,13 @@ $ qsub -IX -q qprod -A PROJECT-ID -l select=2
The issued console commands launche an interactive session on 2 nodes. This is the minimal setup to test that the simulator/adaptor code runs on multiple nodes.
After the interactive session is opened, load the ParaView module
After the interactive session is opened, load the ParaView module.
```console
$ ml ParaView/5.6.0-intel-2017a-mpi
```
When the module is loaded and you run the client-server mode, launch the mpirun command for pvserver as used in description for [ParaView client-server][paraview_it4i] but use also the *&* sign at the end of the command. Then you can use the console later for running the simulator/adaptor code. If you run the VNC session, after loading the ParaView module, setup the environmental parameter for correct keyboard input and then run the ParaView in the background using the *&* sign
When the module is loaded and you run the client-server mode, launch the mpirun command for pvserver as used in description for [ParaView client-server][paraview_it4i] but use also the *&* sign at the end of the command. Then you can use the console later for running the simulator/adaptor code. If you run the VNC session, after loading the ParaView module, setup the environmental parameter for correct keyboard input and then run the ParaView in the background using the *&* sign.
```console
$ export QT_XKB_CONFIG_ROOT=/usr/share/X11/xkb
......@@ -113,7 +113,7 @@ Go to your build directory and run the built simulator/adaptor code from console
mpirun -n 2 ./CxxFullExample 30 30 30 ../feslicescript.py
```
Programs starts to compute on the allocated nodes and prints out the response
Programs starts to compute on the allocated nodes and prints out the response.
![](insitu/img/Simulator_response.png "Simulator/adaptor response")
......@@ -125,7 +125,7 @@ By clicking on it another item called *Extract: input* is added.
![](insitu/img/Extract_input.png "Extract: input")
If you click on the eye icon left to the *Extract: input* item the data finally appears.
If you click on the eye icon left to the *Extract: input* item the data will appear.
![](insitu/img/Data_shown.png "Sended data")
......@@ -133,7 +133,7 @@ To visualize the velocity property on the geometry, go to the *Properties* tab a
![](insitu/img/Show_velocity.png "Show velocity data")
The final result looks like in the image below, where different domains dependent on the number of allocated resources can be seen and progress through the time
The final result will look like in the image below, where different domains dependent on the number of allocated resources can be seen and they willp rogress through the time.
![](insitu/img/Result.png "Velocity results")
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment