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.
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.
Screenplay Animation
Screenplay is an integrated animation tool in Simcenter STAR-CCM+ that allows you to tell a story about figures of merit in your simulations. The underlying technology used in Screenplay is known as keyframe animation.
Screenplay Workflow
To set up a Screenplay animation, you transfer post-processing properties into the Screenplay editor, and then modify Screenplay objects that will control these properties at specific moments in animation time.
Exporting to an External Video File
Once you have finished setting up your animation, and have prepared your graphics settings for optimum performance, you can save it to a video file.

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.
  - Scenes
    In Simcenter STAR-CCM+, you can visualize the results of your simulation using scenes. Scenes, which are stored within the Scenes node, are compositions of one or more displayers that render solution data on the parts you choose.
  - Visualization Workflow
    Scenes are the central objects that you use for visualizing results in Simcenter STAR-CCM+. In general, scenes are composed of one or more displayers to which you assign parts or regions for rendering. Each displayer is responsible for rendering solution data, geometry surfaces, or mesh surfaces according to your selections.
  - Advanced Rendering
    Advanced rendering provides realistic visual presentation at an economic computational cost through ray tracing. Ray tracing simulates the travel of light as it passes through the domain and comes into contact with objects in that domain.
  - Screenplay Animation
    Screenplay is an integrated animation tool in Simcenter STAR-CCM+ that allows you to tell a story about figures of merit in your simulations. The underlying technology used in Screenplay is known as keyframe animation.
    - Screenplay Concepts and Editor
      A Screenplay must be associated with one primary view object (scene or plot) that is opened along with it. Screenplay comes with a hierarchy of its own objects by which you control the behavior of the scene.
    - Screenplay Workflow
      To set up a Screenplay animation, you transfer post-processing properties into the Screenplay editor, and then modify Screenplay objects that will control these properties at specific moments in animation time.
      - Creating and Editing a Screenplay Animation
        The first step in setting up a Screenplay animation is to create the Screenplay object and select its associated scene, plot, or layout. If you use a layout, you can include more than one display in your Screenplay animation.
      - Animating Post-Processing Properties
        To set up the animation, you drag post-processing properties onto the Screenplay editor. Afterwards specify the keyframe settings to control how those properties change.
      - Controlling the Camera View in the Animation
        You can specify the camera view at multiple moments throughout the animation, so as to create fly-around and zoom effects for assessments of solution data.
      - Animating Transient Data
        Screenplay can control properties of solution history nodes that are connected to .simh files.
      - Exporting to an External Video File
        Once you have finished setting up your animation, and have prepared your graphics settings for optimum performance, you can save it to a video file.
    - Screenplay Reference
      Screenplay nodes are within the Tools > Screenplays node.
  - Annotations
    Annotations are objects that you add to scenes in order to provide extra information or visualization within the same window. For example, you can show the current time-step in a scalar scene or include a numerical value from a report. Possible annotations include report values, 2D or 3D images, and embedded versions of other scenes.
  - Using Transforms
    Displayers use transforms to modify the default position, orientation, or size of the part in the displayer.
  - Obtaining Render Performance Data for a Scene
    You can view a report that provides rendering statistics for a scene that is open in the Graphics window.
  - Visualization Reference
    Visualization tools in Simcenter STAR-CCM+ include a wide range of objects in the UI with which you can control the appearance, scope, and type of data in the display. The controls, documented in the following sections, include a comprehensive set of properties as well as convenient right-click actions.
- 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).
- Signal Processing
  Signal processing applies data set functions to sets of wave data.

Exporting to an External Video File

Once you have finished setting up your animation, and have prepared your graphics settings for optimum performance, you can save it to a video file.

For optimal export performance:

Before launching the export, close all those scene and plot windows that show, or are influenced by, animated post-processing properties.
When derived part updates take most of the time for the export, try again with the file opened in parallel mode.
For a preview export, use low resolution and deactivate the Use Anti-Aliasing option in the Write Animation dialog.
If the scene uses advanced rendering, increase the amount of render threads in the visualization options. For details, see Advanced Rendering Workflow.

For the video to be complete, activate all required actions that you may have deactivated temporarily for faster display rendering.
If you want to change the pace of the animation video, click (Scale) in the Screenplay editor.
1. In the Scale Animation dialog, set either Factor or Total Time and click OK.
To begin the export, click (Record Screenplay Animation), or select the corresponding context menu item of the Screenplay node.
In the Write Animation dialog:
1. Select an export resolution, or specify custom values.
2. Enter a File Name, navigate to the desired location for your video output file, and click Save.
During the movie file export, do not attempt to change interfaced object properties manually.