About Computing and Generating Results

After modifying a model, you can run a local computation of the scenario and update it independently of the whole assembly in which it is inserted. A local PLM Update of a feature is a PLM Update of this feature as a root, with a simplified dependency-graph. The root defines which actors of its global dependency-graph are parts of its local neighborhood.

You can run the Compute and Generate Results with Local update command when:

An update is necessary at the scenario's level only, or the scenario appears as up-to-date, but a Local update may be necessary.	The design modifications of the model, except for hide/show, are not taken into account by the Local update. For example: If the scenario's parameters have been modified since the last computation, the icon is visible in the tree.
No result node corresponds to the selected scenario.	A kinematics or dynamics scenario is created, but no Result Of Scenario node is attached yet. Use the command to create an empty Result Of Scenario node while simulating and checking the scenario.
The scenario is not up-to-date.	A simulation is necessary to update the post-processings (swept volumes, geometric traces), attached to one or several scenarios. Click or Compute and Generate Results with a Global Update to update them all.

When the simulation is complete:

• The Incident Diagnosis dialog box opens if an error is detected during the computation. For more information, see Diagnosing Computation Incidents.
• All the specifications defined under the Scenario category are updated.
• The Kinematics Postprocessing app opens automatically.

If you simulate and generate results for the first time:

• The Result node appears in the tree.
• The Result of Scenario node is created for each simulated scenario.

When the scenario is modified:

• The Scenario node changes into .
• You can click to update the scenario.

If the results were already generated and not updated ( ):

• The content of the Result category is updated.

  Important: Traces and swept volumes are not updated when you use the local update. For more information, see Creating Traces and Creating Swept Volumes.

Tips: Scenario results can be deleted permanently using the context menu. Documents from scenario results can be detached using the context menu. Detached documents are kept in the database. In the 3D area, you can zoom and modify the viewpoint to better monitor the progress of the mechanism's animation. Generating simulation results does not change the nominal position of a mechanism. To change the nominal position, you must preview the simulation results using the Preview option. For more information, see About Specifying a Mechanism's Nominal Position.

When the scenario is computed, the mechanism is animated. For more information about reviewing simulation results, see Viewing the Simulation Results.

After modifying a model, you can update the scenario and the whole assembly in which it is inserted before its simulation. After the simulation of the scenario, the results can be updated all at once. At any time, you can also use a Force update without checking if the scenario needs to be updated or not.

You can run the global update when:

• An update is necessary at the model's level (the Local update does not take the model's modifications into account).

  For example: the model's geometry has been edited (including graphical properties such as hide/show). Or a new product has been added/deleted in the model.

• No result node corresponds to the selected scenario: A kinematics or dynamics scenario has just been created and no Result Of Scenario node is attached yet. Then, no matter which configuration is chosen, you can use (not the preview mode that does not save data) to create an empty Result of Scenario node while simulating and checking the scenario.

  As a consequence, if you simulate and generate results for the first time, the Result node appears in the tree, and the Result of Scenario node is created for each simulated scenario.

• When the scenario's parameters have been modified since the last computation. You can see that an update of the scenario is needed with its node in the tree, and more easily with that is not grayed out.
• When a scenario is not up-to-date, a simulation is necessary to update post-processings (swept volumes, geometric traces), attached to one or several scenarios. Click or to update them all. Then all the post-processings and their representations are updated.

When the simulation is complete:

• If an error is detected during the computation, the Incident Diagnosis dialog box appears to let you understand, analyze, and solve the problem. The diagnosis appears in the tree under Results of Scenario and is stored with the simulation when you propagate the simulation. If you close the Incident Diagnosis dialog box, you can click Incident Diagnosis to open it again, or you can double-click the diagnosis in the tree. See Diagnosing Computation Incidents.
• All the specifications defined under the Scenario category are updated.
• The application automatically switches to the Kinematics Postprocessing app.
• If you simulate and generate results for the first time, Result appears in the tree, and a Result of Scenario node is created for each simulated scenario. For example:
• If the results are already generated, the content of the Result category is updated.

  Important: Traces and swept volumes are updated when you use the global update. See Creating Traces and Creating Swept Volumes.

• Scenario results can be deleted permanently using the context menu.
• Documents from scenario results can be detached using the context menu. Detached documents are kept in database.