Translations:Star-CCM+/5/en: Difference between revisions

Jump to navigation Jump to search
Importing a new version from external source
(Importing a new version from external source)
(Importing a new version from external source)
 
Line 1: Line 1:
When submitting jobs on a cluster for the first time, you must set up the environment to use your license. If you are using CD-adapco's online <i>pay-on-usage</i> server, simply create a <code>~/.licenses/starccm.lic</code> file as shown in the <b>POD license file</b> section above and license checkouts should immediately work.  If however you are using an internal license server, then after creating <code>~/.licenses/starccm.lic</code> you must submit a problem ticket to [[technical support]] so we can help co-ordinate the necessary one time network firewall changes required to access it.  If you still have problems getting the licensing to work then try removing or renaming file <code>~/.flexlmrc</code> since previous search paths and/or license server settings maybe stored in it which conflict with your current <code>starccm.lic</code> settingsNot e that files from previous may have accumulated a significant amount of disc space in hidden directories named <code>.star-version_number</code> if you have run many long jobs in the past using older slurm scripts or if you regularly run starccm+ in gui mode.  These can be removed periodically by carefully running <code>rm -ri ~/.starccm*</code> and replying yes as prompted.
When submitting jobs on a cluster for the first time, you must set up the environment to use your license. If you are using Siemans remote <i>pay-on-usage</i> license server then create a <code>~/.licenses/starccm.lic</code> file as shown in the <b>Configuring your account- POD license file</b> section above and license checkouts should immediately work.  If however you are using an institutional license server, then after creating your <code>~/.licenses/starccm.lic</code> file you must also submit a problem ticket to [[technical support]] so we can help co-ordinate the necessary one time network firewall changes required to access it (assuming the server has never been setup to be accessed from the Alliance cluster you will be using).  If you still have problems getting the licensing to work then try removing or renaming file <code>~/.flexlmrc</code> since previous search paths and/or license server settings maybe stored in it.  Note that temporary output files from starccm jobs runs may accumulate in hidden directories named <code>~/.star-version_number</code> consuming valuable quota space.  These can be removed by periodically running <code>rm -ri ~/.starccm*</code> and replying yes when prompted.
38,897

edits

Navigation menu