Disconnect from server<\/em>. This will leave the simulation running on the CSF but it won’t update in the GUI. You can close the StarCCM GUI at this point.<\/li>\n<\/ol>\nCo-Simulation with Abaqus<\/h2>\n
It is possible to have STAR-CCM+ perform some calculations with Abaqus, exchanging data between the two applications. For example, in mechanical co-simulation STAR-CCM+ passes traction loads to Abaqus (pressure + wall shear stress), and Abaqus passes displacements to STAR-CCM+. In Abaqus, the traction loads are applied to the surface of the solid structure. In STAR-CCM+, the displacements are used as an input to the mesh morpher. Data is exchanged via the Co-Simulation module of STAR-CCM+.<\/p>\n
You will need to set up the co-simulation in your STAR-CCM+ input file and also have available an Abaqus input file. You should also ensure the input files, when run in their respective applications, converge to solutions otherwise the co-simulation will not converge.<\/p>\n
More information is available in the STAR-CCM+ user guide, available on the login node by running the following command after you’ve loaded the starccm modulefile:<\/p>\n
evince $STARCCM_UG\r\n<\/pre>\nExample 40-core co-simulation job<\/h3>\n
In this example we will run a single-node 40-core job with 32 cores used by StarCCM and 8 cores used by Abaqus.<\/p>\n
Create a directory structure for your co-simulation:<\/p>\n
cd ~\/scratch\r\nmkdir co-sim # Change the name as requried\r\ncd co-sim\r\nmkdir abaqus starccm # Two directories to hold the input and output files from each app\r\n<\/pre>\nNow copy your input files to the respective directories. For example:<\/p>\n
cp ~\/abq_cosim.inp ~\/scratch\/co-sim\/abaqus\r\ncp ~\/ccm_cosim.sim ~\/scratch\/co-sim\/starccm\r\n<\/pre>\nNow make some changes to the STAR-CCM+ input file to enable co-simulation. You can do this on your local workstation if you prefer but it is useful to be able to do this on the CSF when you want to change the settings before submitting a job – you will avoid transferring the input file back and forth between your workstation:<\/p>\n
# Load the required version of starccm, for example:\r\nmodule load starccm\/15.02.009-mixed\r\n\r\n# Start an interactive job to run the starccm GUI:\r\ncd ~\/scratch\/co-sim\/starccm\r\nsrun --pty starccm+ ccm_cosim.sim\r\n<\/pre>\nWhen the GUI starts, open the Co-Simulations<\/code> node in the tree viewer, expand Link1<\/code> then look for the following attributes and set their values as follows:<\/p>\nCo-Simulation Type = Abaqus Co-Simulation # Choose from the drop-down menu\r\n...\r\n### Note there are several simulation settings (e.g., ramping parameters) that control\r\n### the simulation. You will need to set these but they are beyond the scope of this\r\n### web-page. Please refer to the starccm user guide.\r\n...\r\nAbaqus Execution\r\n Current Job Name = my-abq-cosim<\/em> # Any name, used to name abaqus output files\r\n Input file = ..\/abaqus\/abq_cosim.inp # See directory structure created above\r\n Executable name = abq2020 # The Abaqus command used on the CSF (choose version)\r\n Number of CPUs = 8 # This MUST match the jobscript (see below)\r\n Remote shell = ssh # The default - leave set to this\r\n<\/pre>\nSave the input file and exit the STAR-CCM+ GUI.<\/p>\n
Now create a jobscript to load the starccm and abaqus modulefiles, and run starccm with the correct number of cores:<\/p>\n
cd ~\/scratch\/co-sim\/starccm\r\ngedit cosim.sh\r\n<\/pre>\nThe jobscript should contain the following:<\/p>\n
#!\/bin\/bash --login\r\n#SBATCH -p multicore # Single-node parallel job\r\n#SBATCH -n 40 # 40-cores in total for StarCCM and Abaqus to use\r\n\r\n## Load the modulefiles in the jobscript so we always know which version we used\r\nmodule load starccm\/15.02.009-mixed\r\nmodule load abaqus\/2020\r\n\r\n## We will use 32 (out of 40) cores for starccm and 8 (out of 40) cores for abaqus.\r\n## Manually set the special SLURM_NTASKS variable to these numbers so the license check\r\n## scripts test for the correct number of licenses. If there are not enough licenses\r\n## then the job will requeue.\r\nexport SLURM_NTASKS=8\r\n. $ABAQUS_HOME\/liccheck.sh\r\n\r\n## NOTE: We will leave SLURM_NTASKS set to the number needed for starccm after this license check\r\nexport SLURM_NTASKS=32\r\n. $STARCCM_HOME\/liccheck.sh\r\n\r\n# Create a file listing the nodes to use\r\nNODEFILE=nodes.$SLURM_JOB_ID.txt\r\nscontrol show hostnames $SLURM_JOB_NODELIST > $NODEFILE\r\n\r\n## Now run starccm with 32 cores. It runs the 'abq2020' command with 8 cores (set in input file)\r\nstarccm+ -batch ccm_cosim.sim -mpi openmpi -machinefile $NODEFILE -np $SLURM_NTASKS\r\n<\/pre>\nSubmit the job using<\/p>\n
sbatch cosim.sh<\/pre>\nWhen the job runs you will see output files written to the ~\/scratch\/co-sim\/abaqus<\/code> and ~\/scratch\/co-sim\/starccm<\/code> directories. For example, to see what is happening in each simulation:<\/p>\ncd ~\/scratch\/co-sim\/abaqus\r\ntail -f my-abq-cosim<\/em>.msg # The abaqus output file name was set in the starccm input file above\r\n #\r\n # Press CTRL+C to exit out of the 'tail' command\r\n\r\ncd ~\/scratch\/co-sim\/starccm\r\ntail -f slurm-123456<\/em>.out # Replace 123456<\/em> with the job id number of your starccm job\r\n #\r\n # Press CTRL+C to exit out of the 'tail' command\r\n<\/pre>\nThe simulation should run until it is converged.<\/p>\n
Further Information<\/h2>\n
Further information on StarCCM+ and other CFD applications may be found by visiting the MACE CFD Forum<\/a>.<\/p>\nThe STAR-CCM+ user guide is available on the CSF using the following command after<\/em> you have loaded the starccm modulefile:<\/p>\nevince $STARCCM_UG\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"Overview StarCCM+ is a computation continuum mechanics application which can handle problems relating to fluid flow, heat transfer and stress. See below for the available versions on CSF. Please note that the CSF Team do not supply copies of STARCM+ for laptops\/desktops, you will need to request that via the Research Applications Team. Restrictions on Use Only users who have been added to the StarCCM group can run the application (run groups to see your.. Read more »<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"parent":49,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-362","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/pages\/362","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/comments?post=362"}],"version-history":[{"count":20,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/pages\/362\/revisions"}],"predecessor-version":[{"id":1457,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/pages\/362\/revisions\/1457"}],"up":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/pages\/49"}],"wp:attachment":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf4\/wp-json\/wp\/v2\/media?parent=362"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}