Home
Post-Processing
Simcenter STAR-CCM+ allows you to post-process the solution after each iteration or time-step, (while the simulation is running), as well as when the simulation completes. For this reason, you generally create post-processing objects before running the simulation. Post-processing objects are also known as analysis objects.
Triggers and Update Events
Several features of Simcenter STAR-CCM+ require that you define a trigger for when an action takes place. Simcenter STAR-CCM+ provides three built-in trigger types, and one custom trigger type (defined by an update event).
Trigger Types

Share

Link: copied

Breadcrumb: copied

Post-Processing
Simcenter STAR-CCM+ allows you to post-process the solution after each iteration or time-step, (while the simulation is running), as well as when the simulation completes. For this reason, you generally create post-processing objects before running the simulation. Post-processing objects are also known as analysis objects.
- Analysis Workflow
  The key steps in successfully analyzing simulation results are to: (1) be clear on what quantities you want to extract; (2) locate or define surfaces on which to obtain the data; and, (3) present the data in visual scenes or numeric output.
- Data Interpolation
  Most visualization objects such as plots, reports, and scalar displayers allow for smooth and non-smooth values. For example, the contour style for scalar displayers provides a Smooth Filled option (smooth) and a Filled option (non-smooth). The way these values are calculated depends on the discretization method.
- Field Function Interpolation and Interfaces (FV)
  For finite volume meshes, understanding how Simcenter STAR-CCM+ deals with field function data is important for avoiding non-physical results in post-processing at an interface, and to appreciate the difference that smoothing makes when it is applied.
- Accessing Solution Data through Derived Parts
  Although Simcenter STAR-CCM+ can display, analyze, and report simulation data on regions, boundaries, and parts, there are many cases when you want to access data in other entities of the solution space. Derived parts provide a mechanism for defining additional entities on which you can access solution data.
- Visualizing the Solution
  The visualization tools in Simcenter STAR-CCM+ are integrated with the analysis, allowing for the interactive extraction and viewing of solution data from either a running or converged simulation.
- Transient Solution Data
  For transient solutions, Simcenter STAR-CCM+ provides the simulation history file (.simh) to which you can save selected data while a simulation is running. After the simulation completes, you can load this file and query its states for post-processing.
- Sampling Data Values Using Reports and Monitors
  This workflow incorporates the roles of both reports and monitors.
- Accessing Field Data from Previous Time-Steps or Iterations
  A field history is a type of field monitor that stores a finite number of past values (or samples) of a field function, captured at moments defined by its update policy, for a given set of input regions or boundaries (or both).
- Reporting Results
  Reports provide summaries of solution data.
- Monitoring the Solution
  Monitors sample, save, and plot solution data.
- Plots
  The plotting features in Simcenter STAR-CCM+ allow you to create three kinds of two-dimensional plots.
- Exploring Solutions with Data Focus
  This interactive tool lets you extract knowledge of merit -- information that facilitates a correct engineering decision -- from a large volume of data.
- Parametric Positioning for Analysis Surfaces in Turbomachine Domains
  In studies of cases of revolving volumes, such as turbomachinery, a typical requirement for post-processing is to render and plot data on surfaces or profiles that are positioned parametrically in relation to the domain bounding surfaces. For example, you may wish to view the total pressure on a surface located exactly half-way between the hub and shroud, or you may wish to plot pressure across both blade surfaces on a given slice.
- Triggers and Update Events
  Several features of Simcenter STAR-CCM+ require that you define a trigger for when an action takes place. Simcenter STAR-CCM+ provides three built-in trigger types, and one custom trigger type (defined by an update event).
  - Setting the Trigger for an Update
    In general, features that require you to define a trigger expose the Update node. Use the properties of this node, and any child nodes, to define when an update action occurs.
  - Trigger Types
  - Trigger Properties
    Triggers control when an update event occurs.
  - User-Defined Update Events
    User-defined update events are custom triggers that provide you with more flexibility compared to the built-in trigger types. With a user-defined update event, you can trigger an update based on monitor values.
- Signal Processing
  Signal processing applies data set functions to sets of wave data.

Trigger Types

There are four methods of triggering an update event listed in the table below.


Trigger Type	Description
Iteration	Triggers an update every n iterations. Specify the update frequency in the Number of Iterations property field.
Time Step	Triggers an update every n time-steps, where the Number of Time Steps property specifies the update frequency. This trigger type is only appropriate for transient simulations.
Delta Time	Triggers an update when the simulation time advances by the amount you specify in the Delta Time property field. This trigger type is only appropriate for transient simulations.
Update Event	Triggers an update based on a user-defined update event. User-defined update events are based on monitor values and provide you with more flexibility in controlling the updates. See User-Defined Update Events.

Note

For each trigger type, apart from Update Event, you can control the start, end, and update interval in the properties panel of the child node. See Trigger Properties. For Update Event, you can specify these settings in the relevant update event, located under the Automation > Update Events node. See User-Defined Update Events. However, if you step the solution, for example executing a single iteration, updates occur in all affected features (such as scenes, plots, or solution histories) regardless of your specified update settings.