{"id":3572,"date":"2019-02-18T12:17:16","date_gmt":"2019-02-18T20:17:16","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Simcenter-Blog\/STAR-CCM-v11-06-Building-a-better-sim-file-part-1-of-2\/ba-p\/569329"},"modified":"2026-03-26T06:08:57","modified_gmt":"2026-03-26T10:08:57","slug":"star-ccm-v11-06-building-a-better-sim-file-part-1-of-2","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/simcenter\/star-ccm-v11-06-building-a-better-sim-file-part-1-of-2\/","title":{"rendered":"STAR-CCM+ v11.06: Building a better sim file – part 1 of 2"},"content":{"rendered":"\n

Please note: Original publication date 10-18-2016<\/strong><\/em><\/p>\n\n\n\n

A well organized workshop, purposely conceived to build and revise things of interest, is truly appealing with its array of tools, carefully ordered, in a familiar and comfortable environment. Now you\u2019ve probably heard the expression \u201cUse the right tool for the right job.\u201d That works when you know what tools you have in your workshop, what they are supposed to do and exactly where you can find them. With the STAR-CCM+\u00ae<\/sup> v11.06 release, we\u2019re adding and upgrading tools that will improve your ability to productively build and revise your simulations. You\u2019ll be able to set up your simulations more comprehensively and consistently with a reduced likelihood of errors. And you\u2019ll be able to more efficiently conduct critical reviews in the deeper details of your simulations with your colleagues and your customers. In part one of this blog, I\u2019ll be talking about Simulation Parameters and Global Tagging.<\/p>\n\n\n\n

Before STAR-CCM+ v11.06, when you wanted to specify a constant for use in multiple locations, or as a part a more complex expression, you created a field function – a simple scalar, vector or tensor. But there\u2019s an overhead \u2013 a field function is evaluated and stored at every cell. That can become expensive when all you need to store is a single constant. This is perhaps the key difference between simulation parameters and field functions – the former objects, being \u201cspatially invariant,\u201d only need to be stored once. Here are a few other things you need to know about simulation parameters: they can be defined as either scalars or vectors; referenced by other simulation parameters; be used in field functions. You can use them in our 3D-CAD tool to modify geometry, or anywhere that you can use either a field function or type-in expression now. Let\u2019s consider a biomedical application, where we have a notional drug delivery catheter in place near a stenosis in an artery (shown below).<\/p>\n\n\n\n

\"artery_catheter_sim_params.png\"A tracer released at the catheter inlet and exiting from the holes in the catheter is shown using volume rendering. The artery inlet flow speed (left axis) versus time is shown in the plot (lower right). Expression reports which calculate the bulk tracer concentration are set up for six planes (A thru F) along the axis of the artery and are also plotted versus time (right axis). Per-part reporting (also introduced with STAR-CCM+ v11.06) simplifies the creation of the expression reports used in this quantitative assessment of drug delivery.<\/span><\/span><\/p>\n\n\n\n

At the upstream inlet, the annular space between the artery wall and the catheter outer wall, we can use an analytical equation [<\/strong>1]<\/strong> to apply a fully developed flow profile. We define simulation parameters (X<\/strong>s<\/em>) for the artery wall radius, the outer catheter wall radius and the mean flow rate and use them in a field function (fx<\/strong>s<\/em>) for the steady velocity profile. Now, the arterial flow rate also changes in response to the cardiac rhythm. Again, there is an analytical equation available [<\/strong>2]<\/strong> that takes this into account. We define simulation parameters for the pulse rate, BPM (beats per minute), and the value of PI . A second time varying field function (fx<\/strong>s<\/em>) for the unsteady velocity profile incorporates the steady velocity profile and these additional simulation parameters (X<\/strong>s<\/em>). Taking this one more step, we\u2019re going to consistently set the time step for our Implicit Unsteady solver by encapsulating our BPM simulation parameter within another simulation parameter – when we change the flow rate, as defined by BPM, the time step can be automatically changed. <\/p>\n\n\n\n

\"use_simulation_parameter.png\"Use a simulation parameter BPM to set the time-step size used by the solver.<\/span><\/span><\/p>\n\n\n\n

We\u2019ve now built a simulation ready to study a range of flow rates in the most physiologically realistic way that also lets us explore a broad combination of patient physiologies and catheter sizes. It\u2019s handy to be able to get an overview as you work on a simulation effort. That starts with good organization, and this is where tagging comes into our discussion. Tags aren\u2019t new; they\u2019ve been around for a while. But they\u2019ve gotten a major upgrade in this release \u2013 they are now available for nearly every object on the simulation tree. Tags give you a way to connect objects that might not otherwise be easily or logically associated. Let\u2019s go back to our biomedical application. First, we\u2019ve created tags called \u201cproblem_setup<\/strong>\u201d and \u201cinstrumentation<\/strong>\u201d with the intent of identifying objects on the tree that are associated with either the setup of the problem, or are needed for quantitative and qualitative assessments of the results. Some objects are associated with both, and multiple tags are allowed. This exercise is something that can be ideally done while you are building your sim file.<\/p>\n\n\n\n

\"multiple_tag_usage_in_custom_trees.png\"<\/figure>\n\n\n\n

<\/span><\/p>\n\n\n\n

Next, we create a Custom Tree (one of our top features in STAR-CCM+ v11.04) directly for each tag. This makes it easier to see the connection between our simulation parameters, field functions, and where they are actually used. We can easily check that our simulation is properly instrumented before we start our transient run. These tag-based custom trees let us efficiently review our simulation with other colleagues to potentially catch any errors or omissions. In the end. We expect that being able to efficiently scrutinize a problem setup before submitting it will increase the confidence in our analysis setup and any conclusions that we\u2019re able to draw from the results.  <\/p>\n\n\n\n