{"id":380,"date":"2022-07-14T21:08:43","date_gmt":"2022-07-15T01:08:43","guid":{"rendered":"http:\/\/localhost:8080\/?p=380"},"modified":"2024-04-16T09:53:22","modified_gmt":"2024-04-16T13:53:22","slug":"using-star-ccm","status":"publish","type":"post","link":"https:\/\/knowledgebasev.kinsta.cloud\/?p=380","title":{"rendered":"STAR-CCM+"},"content":{"rendered":"<h4>\u00a0<img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1875\" src=\"\/wp-content\/uploads\/screen_shot-star.jpg\" alt=\"screen_shot-star\" width=\"695\" height=\"424\" \/><\/h4>\n<h4>Introduction<\/h4>\n<p><span style=\"color: #ff0000;\"><em>Note: As of v17.*, the batch options have changed.\u00a0<\/em><\/span><\/p>\n<p>Running STAR-CCM+\u00ae on Sabalcore\u00a0Computing&#8217;s HPC Cloud Service is\u00a0easy. You can run\u00a0STAR-CCM+\u00ae \u00a0interactively or in batch mode. You can even work with\u00a0the GUI using the Sabalcore&#8217;s <a title=\"Remote Graphical Interface and rg3d\u2122\" href=\"\/?p=270\">Remote Graphical Interface<\/a>.<\/p>\n<p>Sabalcore supports three licensing options for\u00a0running STAR-CCM+\u00ae:<\/p>\n<ul>\n<li>Power On Demand<\/li>\n<li>Power Session &#8211; You can also use a power session license through a <a title=\"License Server Tunnel\" href=\"\/?p=406\">License Tunnel<\/a><\/li>\n<li>Dedicated license &#8211; Host your license on Sabalcore.<\/li>\n<\/ul>\n<p>Sabalcore does not provide the license. Please contact\u00a0your Siemens sales representative\u00a0for more information on purchasing a\u00a0license.<\/p>\n<p>Before continuing, you should have an understanding of the <a title=\"2) Getting Information About Processors, Compute Nodes, and Your Jobs\" href=\"\/?p=156\">compute clusters<\/a>, <a title=\"4) The PBS script \u2013 Defining Your Job\" href=\"\/?p=233\">how to setup and submit a job<\/a>, and how to <a title=\"5) Running Jobs \u2013 Batch and Interactive\" href=\"\/?p=223\">run a batch or interactive job<\/a>.<\/p>\n<p>In this article you will find:<\/p>\n<ul>\n<li>Run\u00a0STAR-CCM+\u00ae Interactive Sessions via Remote desktop<\/li>\n<li>Run STAR-CCM+\u00ae Batch Jobs via the Command-line<\/li>\n<li>Connect the GUI to an already running Job<\/li>\n<li>STAR-CCM+\u00ae and Java process performance consideration<\/li>\n<\/ul>\n<h4>STAR-CCM+\u00ae Interactive Sessions via Remote Desktop<\/h4>\n<p>To run STAR-CCM+\u00ae in graphical mode follow these simple steps.<\/p>\n<p><a title=\"Transferring Files\" href=\"\/?p=353\">Upload<\/a> your sim files and open a <a title=\"Remote Graphical Interface and rg3d\u2122\" href=\"\/?p=270\">Remote desktop<\/a>\u00a0session.<\/p>\n<p>Select STAR-CCM+\u00ae from the Sabalcore menu (located at the bottom of the screen) . The Launcher will appear.<\/p>\n<p style=\"padding-left: 5px;\"><img decoding=\"async\" class=\"style1\" src=\"wp-content\/uploads\/fds-launcher1.jpg\" alt=\"\" \/><\/p>\n<p>Choose the the <a title=\"2) Getting Information About Processors, Clusters, and Your Jobs\" href=\"\/?p=156\">node type<\/a>, number of nodes and the number of cores per node. This is already filled in by default but should be modified to suit your needs.<\/p>\n<p>Enter your Power-On-Demand license key. Select the check box if you want your key saved to your account profile. Once it&#8217;s saved, you do not have to re-enter the key for interactive OR batch jobs.<\/p>\n<p>Click &#8220;OK&#8221;<\/p>\n<p>After a few moments the STAR-CCM+ GUI should be visible. The system will automatically configure the\u00a0execution nodes so there is no need to specify a hostfile.<\/p>\n<figure id=\"attachment_398\" aria-describedby=\"caption-attachment-398\" style=\"width: 708px\" class=\"wp-caption aligncenter\"><a href=\"wp-content\/uploads\/screen_shot-star.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-398 \" src=\"wp-content\/uploads\/screen_shot-star.jpg\" alt=\"STAR-CCM+ and Remote Graphics\" width=\"708\" height=\"438\" \/><\/a><figcaption id=\"caption-attachment-398\" class=\"wp-caption-text\">STAR-CCM+ and Remote desktop<\/figcaption><\/figure>\n<div class=\"st-alert st-alert-info \">Note: You will continue to be charged if you leave the GUI open. You must close the STAR-CCM+ GUI to stop the charge. Closing the session will not end your job. You must end or kill the job.<\/div>\n<h4>STAR-CCM+\u00ae Batch Jobs via the Command-line<\/h4>\n<p>To run STAR-CCM+\u00ae in batch mode from the command-line create a pbs file with the necessary parameters. You can copy and past this example into a text file to edit.\u00a0This example specifies 128 cores on the onyx cluster.<\/p>\n<pre><span style=\"font-family: Consolas, Monaco, monospace; font-size: 12px; line-height: 18px;\">#PBS -l nodes=8:onyx:ppn=16\r\n# Add the latest version of STAR-CCM+ to your run-time environment.\r\nmodule load starccm\r\n# Put your Power-On-Demand license key here.\r\nexport LM_PROJECT=QXXXVVVXXX\r\n# Change to your working directory where you sim file is located\r\ncd $PBS_O_WORKDIR\r\n# Start starccm versions prior to v17\r\n# starccm+ -power -mpi openmpi -fabric UCX -xsystemlibfabric -xsystemucx -batch model.sim\r\n\r\n# Start starccm+ with the machinefile for version v17+\r\nstarccm+ -power -mpi openmpi -fabric IBV -machinefile machinefile -np $NP -batch myfile.sim<\/span><\/pre>\n<p>Save the script, e.g. starccm_run.pbs<\/p>\n<p>Submit the job to the cluster:<\/p>\n<pre>[user@sci ~]$ qsub starccm_run.pbs<\/pre>\n<p>Use the \u201c<a title=\"2) Getting Information About Processors, Clusters, and Your Jobs\" href=\"\/?p=156\">qstat<\/a>\u201d command to view your job&#8217;s current status.<\/p>\n<pre>[user@sci ~]$ qstat\r\nJob id \u00a0 \u00a0 \u00a0 \u00a0 Name \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0  User \u00a0 \u00a0 \u00a0 \u00a0\u00a0 \u00a0Time Use S \u00a0Queue\r\n------------------------- ---------------- ------ -------- - -----\r\n306417.jman \u00a0 \u00a0starccm_run \u00a0 \u00a0 \u00a0 \u00a0 user \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 00:00:18 R dque<\/pre>\n<p>&nbsp;<\/p>\n<h4>Connect the GUI to an already running Job<\/h4>\n<p>You can connect the GUI to a running batch job. After your batch job has started, you will need to use the &#8220;qstat -n&#8221; command to determine the head node for the job. The first node in the list is the job&#8217;s head node. For example:<\/p>\n<pre>[user@sci ~]$ qstat -n 574693.jman\r\n\r\njman:\r\nJob ID      Username Queue Jobname SessID NDS TSK Memory Time S Time Req'd Req'd Elap\r\n----------------------- ----------- -------- ---------------- ------ ----- ------ ---\r\n574693.jman USER     dque   star.pbs   0      2    8 -- --       R           00:00:00\r\n <strong>n824006<\/strong>\/0+n824006\/1+n824006\/2+n824006\/3+n824005\/0+n824005\/1+n824005\/2+n824005\/3<\/pre>\n<p>This indicates that n824006 is the head node of this job.<\/p>\n<p>Then open a new interactive STAR-CCM+ job. When the STAR-CCM+ GUI starts, select File -&gt; Connect to server. Then enter the hostname of the head node (e.g. n824006) in the &#8220;Host&#8221; field. Then the &#8220;Scan &#8221; to the right of the host field. It should say &#8220;One server found running on [head node]&#8221;. Finally click on &#8220;OK&#8221; to connect.<\/p>\n<h4>STAR-CCM+\u00ae and Java Process Performance Issue<\/h4>\n<p>In some cases, StarCCM+ runs an extra Java process on the head node of the job. The Java process could use a significant portion of one of the processor cores which is also running a STAR-CCM+ process and \u00a0will slow it down, which in turn, will slow the whole job. To counter this, dedicate 1 core on the head node of the job for the Java process. \u00a0For example, a job that uses 48 cores, 47 will be used for starccm+ and 1 will be used for Java. \u00a0Here\u2019s an example PBS script that does just that:<\/p>\n<pre>#PBS -l nodes=2:ppn=24:copper\r\n#PBS -l nodes+=3:ppn=16:onyx\r\n#PBS -l nodes++=4:ppn=12:red\r\n\r\n# Add the latest version of STAR-CCM+ to your run-time environment.\r\nmodule load starccm\r\n\r\n# Put your Power-On-Demand license key here.\r\nexport LM_PROJECT=XXXYYYZZZ\r\n\r\n# Change to your working directory and start STAR-CCM+\r\ncd $PBS_O_WORKDIR\r\n\r\n# Create a machinefile with N-1 hostname (reserves 1 core for java, do not edit)\r\ntail -n +2 $PBS_NODEFILE &gt; machinefile\r\n\r\n# Count the number of worker processes (do not edit)\r\nNP=$(cat machinefile | wc -l)\r\n\r\n# Start starccm+ with the machinefile prior to v17\r\n#starccm+ -power -mpi openmpi -fabric UCX -xsystemlibfabric -xsystemucx -machinefile machinefile -np $NP -batch myfile.sim\r\n\r\n# Start starccm+ with the machinefile for version v17+\r\nstarccm+ -power -mpi openmpi -fabric IBV -machinefile machinefile -np $NP -batch myfile.sim<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>\u00a0 Introduction Note: As of v17.*, the batch options have changed.\u00a0 Running STAR-CCM+\u00ae on Sabalcore\u00a0Computing&#8217;s HPC Cloud Service is\u00a0easy. You can run\u00a0STAR-CCM+\u00ae \u00a0interactively or in batch mode. You can even work with\u00a0the GUI using the Sabalcore&#8217;s Remote Graphical Interface. Sabalcore supports three licensing options for\u00a0running STAR-CCM+\u00ae: Power On Demand Power Session &#8211; You can also [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[85],"tags":[122,119,88],"class_list":["post-380","post","type-post","status-publish","format-standard","hentry","category-software-specific-guides","tag-java","tag-poor-performance","tag-star-ccm-starccm"],"_links":{"self":[{"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=\/wp\/v2\/posts\/380","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=380"}],"version-history":[{"count":44,"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=\/wp\/v2\/posts\/380\/revisions"}],"predecessor-version":[{"id":1828,"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=\/wp\/v2\/posts\/380\/revisions\/1828"}],"wp:attachment":[{"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=380"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=380"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/knowledgebasev.kinsta.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}