Using Design Assessment


Note:   Advisory for Users or Prospective Users of Design Assessment. If you are considering creating your own post-processing customization, we recommend that you develop it using the ANSYS Customization Suite. The ANSYS Customization Suite is our customization platform going forward, and offers more powerful post-processing along with pre-processing capabilities. For more information about the capabilities available in the ANSYS Customization Suite, see:

For those Design Assessment users working with ANSYS Beamcheck and/or ANSYS Fatjack, you should continue to use Design Assessment and/or run them stand-alone.


The Design Assessment system provides further options to quantitatively examine the results from other Mechanical application systems by supporting built-in operations, as well as facilities to perform custom computations on the data. For example, a Design Assessment system could be used to obtain solution combinations, to verify a design in relation to a particular standard (e.g. for BEAMCHECK and FATJACK), or to perform custom calculation processes (for example, fragmentation analyses, calling a third-party program to process results data, or running a Mechanical APDL post processing session).

User Workflow

It is useful to understand the user workflow in a Design Assessment system in order to customize its calculation process. A key step in the workflow is to select the upstream system whose results will be examined. This is accomplished using the Solution Selection object. Once specified, there are three considerations that affect the outcome of the calculation process (and can thus be customized):

The user feeds inputs into the Design Assessment system via one or more Attribute Group objects.

The scripts are the workhorse for computation. They are programmed in the Python scripting language and have access, at runtime, to all relevant data in the model, including any inputs collected from the user, along with the mesh and upstream results, through an Application Programmable Interface (API).

The user defines result requests using the DA Result object to prescribe what quantities to plot and where on the model.

Customization

With the exception of Solution Combinations, predefined assessment types such as FATJACK and BEAMST feature Attribute Groups, Scripts, and Result Objects, and can be used as the basis for customization. These three components of the calculation process must be described in the XML definition file before they can be featured in a Design Assessment system.

Collectively, the inputs for the process are described in the AttributeGroups section of the Definition File. Each input is controlled by an individual Attribute indicating the type of data to gather from the user, its scope of application on the model, and its validation, among other details.

The scripts are prescribed in the DAScripts section of the XML definition file and are the workhorse for computation. Distinct scripts for "Solve" and for "Evaluating Results" are possible to respond to the respective user operations in the Mechanical application editor. Example snippets are provided for each class in the scripting API, along with full worked examples in this documentation. There is a section on Developing and Debugging Scripts for more operation details.

The display of results is configured in the Results section of the XML definition file. Individual Attributes are also used here to collect inputs from the user that can be accessed in the script to control what is to be plotted.

Once configured, the XML definition file is imported into Design Assessment as a User Defined type, distinct from all the predefined ones mentioned, and is ready to be used as a custom calculation process. For details, see the section below on configuring the assessment type.

Design Assessment Types

Design Assessment systems offer three predefined types and a user define type (for customization). The predefined types are:

To configure a particular Design Assessment system, you may:

or

For User Defined assessment types, the XML definition file will automatically be copied to your project folder upon selection, to keep as a reference. If you subsequently edit your XML definition file and want the changes to be used in a project, it will need to be re-selected. At this stage the differences between the original and the revised XML definition file will be detected and any defined objects will be updated as detailed in Changing the Assessment Type or XML Definition File Contents


Note:  If you Import a Mechanical database (e.g., a .mechdat file) containing a Design Assessment system you must reselect the Assessment Type (and associated XML definition file for the User Defined type) before opening the project in the Mechanical application. Otherwise, your assessment type will revert to Solution Combination Only and any Design Assessment objects will be lost.


The following sections describe the use of the Design Assessment system.


Release 18.2 - © ANSYS, Inc. All rights reserved.