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/05/14 11:08]
ccrosby [Meshing on a compute node]
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, 13.06.012 and 14.02.010 in mixed and double precision versions. ​ If you need a different version, please contact CHPC support through the CHPC website. ​ We will shortly retire the older minor versions, such as 12.04.010, 12.060.010, 13.02.011, 13.04.010 and 13.06.011.+==== 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 =====
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.
/var/www/wiki/data/attic/howto/starccm.1557824895.txt.gz · Last modified: 2019/05/14 11:08 (external edit)