Star-CCM+: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 7: Line 7:


= License limitations = <!--T:2-->
= License limitations = <!--T:2-->
We have the authorization to host STAR-CCM+ binaries on our servers, but we don't provide licenses to users. You will need to have your own license in order to use this software. A remote pod license can be purchased directly from [https://www.plm.automation.siemens.com/global/en/buy/ Siemens]. Alternatively, a local license hosted at your institution can be used, providing it can be accessed through the firewall from the cluster where jobs are to be run.
We have the authorization to host STAR-CCM+ binaries on our servers, but we don't provide licenses. You will need to have your own license in order to use this software. A remote POD license can be purchased directly from [https://www.plm.automation.siemens.com/global/en/buy/ Siemens]. Alternatively, a local license hosted at your institution can be used, providing it can be accessed through the firewall from the cluster where jobs are to be run.


== Configuring your account == <!--T:7-->
== Configuring your account == <!--T:7-->
Line 15: Line 15:
where you change <tt>IP</tt> and <tt>PORT</tt> with the IP address and the port used by the license server at your institution.
where you change <tt>IP</tt> and <tt>PORT</tt> with the IP address and the port used by the license server at your institution.


=== Pod License File === <!--T:261-->
=== POD license file === <!--T:261-->


<!--T:262-->
<!--T:262-->
Researchers who have purchased a pod license from [https://www.plm.automation.siemens.com/global/en/buy/ Siemens] may simply configure the following <tt>$HOME/.licenses/starccm.lic</tt>  file on any cluster Alliance cluster where starccm jobs are to be run :
Researchers who have purchased a POD license from [https://www.plm.automation.siemens.com/global/en/buy/ Siemens] may simply configure the following <tt>$HOME/.licenses/starccm.lic</tt>  file on any of our clusters where Star-CCM+ jobs are to be run.
{{File|name=starccm.lic|contents=SERVER flex.cd-adapco.com ANY 1999
{{File|name=starccm.lic|contents=SERVER flex.cd-adapco.com ANY 1999
USE_SERVER}}
USE_SERVER}}
Line 33: Line 33:


<!--T:4-->
<!--T:4-->
Neither IBM Platform MPI nor Intel MPI are tightly coupled with our scheduler; you must therefore tell <tt>starccm+</tt> which hosts to use by means of a file containing the list of available hosts. To produce this file, we provide the <tt>slurm_hl2hl.py</tt> script, which will output the list of hosts when called with the option <tt>--format STAR-CCM+</tt>. This list can then be written to a file and read by Star-CCM+. Also, because these distributions of MPI are not tightly integrated with our scheduler, you should use options <tt>--ntasks-per-node=1</tt> and set <tt>--cpus-per-task</tt> to use all cores as shown in the scripts.
Neither IBM Platform MPI nor Intel MPI are tightly coupled with our scheduler; you must therefore tell <tt>starccm+</tt> which hosts to use by means of a file containing the list of available hosts. To produce this file, we provide the <tt>slurm_hl2hl.py</tt> script, which will output the list of hosts when called with the option <tt>--format STAR-CCM+</tt>. This list can then be written to a file and read by Star-CCM+. Also, because these distributions of MPI are not tightly integrated with our scheduler, you should use option <tt>--ntasks-per-node=1</tt> and set <tt>--cpus-per-task</tt> to use all cores as shown in the scripts.


<!--T:5-->
<!--T:5-->
You will also need to set up your job environment to use your license. If you are using CD-adapco's online "pay-on-usage" server, the configuration is rather simple. If you are using an internal license server, please [mailto:support@computecanada.ca contact us] so that we can help you set up the access to it.  
You will also need to set up your job environment to use your license. If you are using CD-adapco's online <i>pay-on-usage</i> server, the configuration is rather simple. If you are using an internal license server, please [mailto:support@computecanada.ca contact us] so that we can help you set up the access to it.  


<!--T:8-->
<!--T:8-->
Note that at [[Niagara]] the compute nodes mount the <tt>$HOME</tt> filesystem as "read-only".  Therefore it is important to define the environment variable <tt>$STARCCM_TMP</tt> and point it to a location on <tt>$SCRATCH</tt>, which is unique to the version of StarCCM+.  Otherwise StarCCM+ will try to create such a directory in the <tt>$HOME</tt> and crash in the process.
Note that at [[Niagara]], the compute nodes mount the <tt>$HOME</tt> filesystem as <i>read-only</i>.  Therefore it is important to define the environment variable <tt>$STARCCM_TMP</tt> and point it to a location on <tt>$SCRATCH</tt>, which is unique to the version of StarCCM+.  Otherwise, StarCCM+ will try to create such a directory in <tt>$HOME</tt> and crash in the process.
</translate>
</translate>


Line 199: Line 199:
   
   
# Workaround for license failures.  
# Workaround for license failures.  
# Try up to 5 times to get starccm+ to start by checking exit status (throws 143 when fails, 0 when works).
# Try up to 5 times to get Star-CCM+ to start by checking exit status (throws 143 when fails, 0 when works).
i=1
i=1
RET=-1
RET=-1
Line 222: Line 222:
o To setup your account for remote visualization:
o To setup your account for remote visualization:
# Create <code>~/.licenses/starccm.lic</code> as described above<br>
# Create <code>~/.licenses/starccm.lic</code> as described above<br>
# Users with a Power-on-demand (POD) license should also:
# Users with a POD license should also:
:: set: <code>export LM_PROJECT='CD-ADAPCO PROJECT ID'</code> and
:: set: <code>export LM_PROJECT='CD-ADAPCO PROJECT ID'</code> and
:: add: <b>-power</b> to the other command line options shown below
:: add: <b>-power</b> to the other command line options shown below
rsnt_translations
56,430

edits