| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
howto:visit [2017/12/01 11:07]
ccrosby |
howto:visit [2022/05/23 11:52] (current)
ccrosby [Running VisIt] |
| ====== Running VisIt ====== | ====== Running VisIt ====== |
| There are two versions of VisIt installed on Lengau. Visit-2.10.2 is installed in ''/apps/chpc/compmech/CFD/VisIt/visit2.10.2/src/bin''. Visit-2.13.2 is installed in ''/apps/chpc/compmech/visit2_12_3.linux-x86_64''. Both versions are available as modules. Use the command ''module avail'' to find it. Please refer to the [[https://wci.llnl.gov/simulation/computer-codes/visit/|VisIt web site]] for more information on VisIt. For interactive graphics, an OpenGL-enabled environment will be required, therefore refer to the page on [[howto:remote_viz|Remote Visualization]] for instructions on setting up a connection to the visualization node, and running VisIt with the VirtualGL wrapper. VisIt is an extremely versatile post-processor, and can be used as the primary visualization tool for a very wide range of applications and file formats. | |
| | There are three versions of VisIt installed on Lengau: |
| | - Visit-2.10.2 |
| | - Visit-2.13.3 |
| | - Visit-3.1.1 |
| | |
| | |
| | All three versions are available as modules. Use the command ''module avail 2>&1 | grep VisIt'' to find the module names. Please refer to the [[https://wci.llnl.gov/simulation/computer-codes/visit/|VisIt web site]] for more information on VisIt. For interactive graphics, an OpenGL-enabled environment will be required, therefore refer to the page on [[howto:remote_viz|Remote Visualization]] for instructions on setting up a connection to the visualization node, and running VisIt with the VirtualGL wrapper. VisIt is an extremely versatile post-processor, and can be used as the primary visualization tool for a very wide range of applications and file formats. |
| |
| ===== Running VisIt on a visualization node ===== | ===== Running VisIt on a visualization node ===== |
| It is possible to run a VisIt client on your local workstation, with the data and render processing happening on a cluster node. However, is is easier to use one of the visualization nodes (chpclic1 or chpcviz1) to run the interface. In order to do this, load the module ''chpc/compmmech/VisIt/2.12.3-VNC'', and start VisIt with the command ''vglrun visit''. This will get you a serial version of VisIt, which is adequate for processing smaller data sets. | It is possible to run a VisIt client on your local workstation, with the data and render processing happening on a cluster node. However, is is easier to use one of the visualization nodes (chpclic1 or chpcviz1) to run the interface. In order to do this, load the module ''chpc/compmech/VisIt/2.12.3-VNC'', and start VisIt with the command ''vglrun visit''. This will get you a serial version of VisIt, which is adequate for processing smaller data sets. |
| |
| ==== VisIt on a viz node with the compute engine on a compute node ==== | ==== VisIt on a viz node with the compute engine on a compute node ==== |
| In order to visualize large data sets effectively, add one or more compute nodes. For VisIt to be able to start the remote compute engine on a compute node, two modules need to be loaded by default, which is most easily achieved by inserting these two lines in your ~/,bashrc file: | In order to visualize large data sets effectively, add one or more compute nodes. For VisIt to be able to start the remote compute engine on a compute node, three modules need to be loaded by default, which is most easily achieved by inserting these three lines in your ~/,bashrc file: |
| ''module load gcc/6.1.0'' | <code> |
| and | module load gcc/6.1.0 |
| ''module load chpc/compmech/mesa/17.0.1'' | module load chpc/compmech/mpich/3.2/gcc-6.2.0 |
| | module load chpc/compmech/mesa/17.0.1 |
| | </code> |
| |
| However, the mesa module will clash with the VNC implementation of VisIt, therefore you will need to unload it in your VNC session before starting VisIt. | However, the mesa module will clash with the VNC implementation of VisIt, therefore you will need to unload it in your VNC session before starting VisIt. |
