In this section, you will explore a use case demonstrating the Compute Partial Result update strategy.
| This technical practice highlights the strategy used in resilient modelling that computes partial result when a complete computation result is impossible. |
During the design process, computation failures may arise from increased geometric or topological complexity. In such cases, a mechanism that enables the workflow to continue through partial computation becomes essential. The Compute Partial Result strategy provides this capability, ensuring output under partial computational conditions. |
This technical practice outlines the Compute Partial Result strategy as applied across key modelling commands, enabling feature creation in case when only partial geometry can be computed. |
All roles that include the Part Design app, Part Design Plus app, Generative Shape Design app and Generative Shape Design Plus app |
Mechanical Designers, Conceptual Designers, Mechanical Surface Designers |
The computed result is same as the one computed using the Fill twisted areas option in the Sweep command dialog box. The Sweep, Offset, Join, and Mid Surface features can benefit from this command. |
Use Case: Execute Compute Partial Result strategy, on the child feature whose parent feature is in error. It still ignores and generates a partial result.Scenario: In a design, when an offset surface is created from a parent feature which contains a styling blend. Any changes in the reference curve of the styling blend can cause the offset to fail. Using the Compute Partial Result stargey the offset surface is updated partially and remain stable during parent feature changes. |
Play the video to watch how the Compute Partial Result Strategy is used to compute the offset surface. |
To learn more about Compute Partial Result, explore the M3S learning module. |
