User Tools

Site Tools


howto:starccm

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
howto:starccm [2019/02/07 08:56]
ccrosby [** WARNING: Choice of MPI implementation **]
howto:starccm [2020/01/30 12:33] (current)
ccrosby [CHPC Installation]
Line 2: Line 2:
  
 ==== WARNING: Choice of MPI implementation ==== ==== WARNING: Choice of MPI implementation ====
-** Although we have obtained best scaling to large core counts when using "​platform"​ MPI, we are currently experiencing an incompatibility ​between STAR-CCM+ and platform MPI.  While we get to the bottom of this, please revert to intel MPI. **+** Although we have obtained best scaling to large core counts when using "​platform"​ MPI, we experienced incompatibilities ​between STAR-CCM+ and platform MPI.  While we get to the bottom of this, please revert to intel MPI. **  Our latest experience is that the current MPI implementations work with Version 14.04.011:​ 
 +  * intel 
 +  * platform 
 +  * openmpi
  
-==== CHPC Installation ====+Please let us know if you experience any difficulties related to the choice of MPI implementation.
  
-The CHPC has an installation of STAR-CCM+, but with no license. ​ Approved users can use the software on the CHPC cluster, but need to work off their own licenses. ​ We have retired versions older than 11.06.010, but continue to offer 11.06.010, 12.02.011, 12.04.010, 12.04.011, 12.06.010, 12.06.011, 13.02.011, 13.02.013, 13.04.010, 13.06.010, 13.06.011 and 13.06.012 in mixed and double precision versions. ​ If you need a different version, please contact CHPC support through the CHPC website.+==== CHPC Installation ====
  
 +The CHPC has an installation of STAR-CCM+, but with no license. ​ Approved users can use the software on the CHPC cluster, but need to work off their own licenses. ​ We have retired versions older than 12.04.011, but continue to offer 12.04.011, 12.06.010, 12.06.011, 13.02.011, 13.02.013, 13.04.010, 13.06.010, 13.06.011, 13.06.012, 14.02.010, 14.04.011, 14.06.012 and 14.06.013 in mixed and double precision versions. ​ If you need a different version, please contact CHPC support through the CHPC website.  ​
  
 ===== Installation ===== ===== Installation =====
  
-Find the different versions under '''/​apps/​chpc/​compmech/​CFD/​CD-adapco/'''​. ​ Note that from version 11.06.010 the structure of the installation path has changed, so that the 11.06.010 software versions are installed under the directories 11.06.010 and 11.060.010-R8 respectively,​ and not directly under the CD-adapco ​directory.  ​The CHPC acknowledges that STAR-CCM+ is now a Siemens product, ​but will keep the current ​installation directory name in order to avoid unnecessary confusion.+Find the different versions under '''/​apps/​chpc/​compmech/​CFD/​Siemens/'''​. ​ Note that from version 11.06.010 the structure of the installation path has changed, so that the 11.06.010 software versions are installed under the directories 11.06.010 and 11.060.010-R8 respectively,​ and not directly under the Siemens ​directory.  ​Although the CHPC acknowledges that STAR-CCM+ is now a Siemens product, the existing ​installation directory name '''/​apps/​chpc/​compmech/​CFD/​CD-adapco/'''​ will be kept in order to prevent breaking existing scripts A symbolic link has been added, so that all versions are available under '''/​apps/​chpc/​compmech/​CFD/​Siemens'''​
  
  
Line 41: Line 45:
 #####  Set up path.  ​ #####  Set up path.  ​
 #####  Drop the "​-R8"​ part if you want to use the mixed precision version of the code. #####  Drop the "​-R8"​ part if you want to use the mixed precision version of the code.
-export PATH=/​apps/​chpc/​compmech/​CFD/​CD-adapco/​13.06.011-R8/​STAR-CCM+13.06.011-R8/​star/​bin:​$PATH+export PATH=/​apps/​chpc/​compmech/​CFD/​Siemens/​13.06.011-R8/​STAR-CCM+13.06.011-R8/​star/​bin:​$PATH
 ####  Tell solver where to look for the license.  ​ ####  Tell solver where to look for the license.  ​
 ####  chpclic1 is correct here, there are ssh tunnels from chclic1 to the Siemens license servers.  ​ ####  chpclic1 is correct here, there are ssh tunnels from chclic1 to the Siemens license servers.  ​
Line 73: Line 77:
 #PBS -o /​home/​jblogs/​lustre/​DMExample/​dm.out #PBS -o /​home/​jblogs/​lustre/​DMExample/​dm.out
 #PBS -e /​home/​jblogs/​lustre/​DMExample/​dm.err #PBS -e /​home/​jblogs/​lustre/​DMExample/​dm.err
-export STARCCMHOME=/​apps/​chpc/​compmech/​CFD/​CD-adapco/​12.04.011/​STAR-CCM+12.04.011+export STARCCMHOME=/​apps/​chpc/​compmech/​CFD/​Siemens/​12.04.011/​STAR-CCM+12.04.011
 export PYTHONHOME=$STARCCMHOME/​designmanager/​Ver2017.04/​Python27 export PYTHONHOME=$STARCCMHOME/​designmanager/​Ver2017.04/​Python27
 export HEEDS_ROOT=$STARCCMHOME/​designmanager/​Ver2017.04/​LX64/​solver export HEEDS_ROOT=$STARCCMHOME/​designmanager/​Ver2017.04/​LX64/​solver
Line 111: Line 115:
 ===== Monitoring a STAR-CCM+ Job ===== ===== Monitoring a STAR-CCM+ Job =====
  
-There are different ways of monitoring your solution. ​ Please refer to the page on [[howto:​remote_viz|Remote Visualization]] for instructions on how to get a VNC session on the visualization server. ​ Add the path to the VirtualGL installation with the environment setting: '''​export PATH=$PATH:/​opt/​VirtualGL/​bin'''​ Use qsub -f <job number> to find the actual compute node being used as master node for your simulation. ​ Start up the STAR-CCM+ GUI in your VNC session with the command line '''​vglrun starccm+ -rsh ssh -mesa'''​. ​ The vglrun wrapper and the -mesa command line option are both required to ensure that OpenGL works in the VNC session, unless you simply started up your X-session with vglrun. ​ Once you have the GUI open, you can connect to the solver process on your compute node, and you will be able to monitor your run and generate images.+There are different ways of monitoring your solution. ​ Please refer to the page on [[howto:​remote_viz|Remote Visualization]] for instructions on how to get a VNC session on visualization server ​or on a compute node.  Add the path to the VirtualGL installation with the environment setting: '''​export PATH=$PATH:/​opt/​VirtualGL/​bin'''​ Use qsub -f <job number> to find the actual compute node being used as master node for your simulation. ​ Start up the STAR-CCM+ GUI in your VNC session with the command line '''​vglrun starccm+ -rsh ssh -mesa'''​. ​ The vglrun wrapper and the -mesa command line option are both required to ensure that OpenGL works in the VNC session, unless you simply started up your X-session with vglrun. ​ Once you have the GUI open, you can connect to the solver process on your compute node, and you will be able to monitor your run and generate images.
  
 Be careful of leaving an idle GUI open, especially when using a Power on Demand license, where the license is wallclock hour based. ​ We have set up a 1 hour inactive time limit in order to try and limit the damage. Be careful of leaving an idle GUI open, especially when using a Power on Demand license, where the license is wallclock hour based. ​ We have set up a 1 hour inactive time limit in order to try and limit the damage.
Line 130: Line 134:
  
 === Getting a graphics-capable session on a compute node === === Getting a graphics-capable session on a compute node ===
-There are two ways of doing this:+There are three ways of doing this.  As of 14 May 2019, the preferred method is to use a VNC session on the compute node: 
 +  * **VNC session on the compute node**. ​ Please read the [[http://​wiki.chpc.ac.za/​howto:remote_viz?&#​getting_a_virtual_desktop_on_a_compute_node|instructions]]
   * X-forwarding by means of a VNC session   * X-forwarding by means of a VNC session
   * X-forwarding in two stages   * X-forwarding in two stages
Line 156: Line 161:
 Obviously set the path to the version that you are using: Obviously set the path to the version that you are using:
 <​code>​ <​code>​
-export PATH=/​apps/​chpc/​compmech/​CFD/​CD-adapco/​12.04.010-R8/​STAR-CCM+12.04.010-R8/​star/​bin:​$PATH+export PATH=/​apps/​chpc/​compmech/​CFD/​Siemens/​12.04.010-R8/​STAR-CCM+12.04.010-R8/​star/​bin:​$PATH
 </​code>​ </​code>​
  
/var/www/wiki/data/attic/howto/starccm.1549522606.txt.gz · Last modified: 2019/02/07 08:56 by ccrosby