Rescale provides several versions of CD-Adapco STAR-CCM+. In general, Rescale will make available the latest version with 4 weeks of its release. If a specific version is not available, it can be requested by contacting email@example.com.
What Command do I use to run STAR-CCM+?
To run STAR-CCM+ on Rescale, the standard STAR-CCM+ command-line interface can be used:
starccm+ -power -np <mpi-ranks> -machinefile $HOME/machinefile -batch <batch-script>
-batch - Run in batch mode (no UI). Commands:
<.java macro file>
-np - Specify the number of parallel processes. By choosing
$RESCALE_CORES_PER_SLOT you are passing in the number of cores you selected for the job, thereby setting up a DMP job.
-power - This option is essential when using the Rescale provided On-Demand License or your own Power Session License
-rsh - Set multinode communication. Commands:
For a job with a script:
starccm+ -power -rsh ssh -np $RESCALE_CORES_PER_SLOT -machinefile $HOME/machinefile -batch macro.java -load input.sim
For a job wihout macro:
starccm+ -power -rsh ssh -np $RESCALE_CORES_PER_SLOT -machinefile $HOME/machinefile -batch run -load input.sim
How do I use STAR-CCM+ POD Licenses?
You will require a valid STAR-CCM+ license when setting up your STAR-CCM+ job on Rescale. A POD license can be referenced on the Software Setup section of the job setup. Having selected STAR-CCM+ as the software you wish to use, in License Options select Provide Existing License and enter the following information into the license fields:
- Enter firstname.lastname@example.org into the License field
- Enter your product code into the Project Code field (Your project code is a set of random characters and can be found on the CD-Adapco Steve Portal)
An example of a STAR-CCM+ POD license setup on Rescale is shown below.
How can I remotely access running STAR-CCM+ Jobs using the client on my desktop?
This tutorial shows you how to remotely connect to your STAR-CCM+ job (running on Rescale cluster) using the STAR-CCM+ client on your personal desktop.
First, you will need to set up and launch a STAR-CCM+ job through Rescale (read here). At the Software Settings page, you will need to include the
-collab flag into the command box. For example:
starccm+ -power -rsh ssh -np $RESCALE_CORES_PER_SLOT -machinefile $HOME/machinefile -collab -batch run -load <input-file>
Once the cluster is up and the job running, please open up the
process_output.log file. At approximately line 20 of the log, you can find the server information.
You can read the file through the live tailing window if the line is still visible, else you will need to download the file first (use the icon on the top right hand corner of the black live tailing window).
Server::start -host ip-10-25-38-85.ec2.internal:47827
Next, launch the STAR-CCM+ client on your desktop and navigate to "File > Connect to Server..."
If you are using Rescale desktops, you can skip the setup of a SSH tunnel and connect to the server directly by entering the server information (extracted above) in the following format, and clicking "OK" (see below). You will now be connected to your running job.
If you are using your personal workstation, you would need to first set up an SSH tunnel to the Rescale cluster. (Note: your SSH key has to be set up on your Rescale account settings BEFORE you launch the job)
plink -ssh <user>@<ip> -L 47827:localhost:47827 -N
ssh -i </path/to/key> <user>@<ip> -L 47827:localhost:47827 -N
Note: you can extract the
<user>@<ip> information under the "Job Logs" section on the Status Page of the Rescale Web UI.
When prompted to trust the host and store the key in cache, enter 'y' or 'yes'.
Lastly, return to the "Connect to Server" popup on the STAR-CCM+ client and enter
localhost into the "Host" field and
47827 into the "Port" field, and click "OK".
You should now be connected to your running job, and you are able to track the job output on the client window:
Note: This only works if the version of the client on your desktop exactly matches the version of STAR-CCM+ you have selected and run on the Rescale platform. If not, you will get the error shown below: