Changing the Assessment Type or XML Definition File Contents

If you change the Assessment Type of your Design Assessment system, or if you change the location or contents of the XML definition file, the Mechanical application will evaluate the existing Design Assessment objects in your project and modify those objects as indicated below. If no content changes are found in the XML definition file (even if the file location changes), or if only the Solve or Evaluate script locations change, no changes are made in the Design Assessment objects in the tree.

If you change the Assessment Type of the Design Assessment system:

From Solution Combination Only to BEAMCHECK

All existing Attribute Group and DA Result objects will be refreshed based on certain criteria.

From Solution Combination Only to FATJACK

All Mechanical results inserted under the Solution object will be deleted and existing Attribute Group and DA Result objects will be refreshed based on certain criteria.

From FATJACK to BEAMCHECK

All existing Attribute Group and DA Result objects will be refreshed based on certain criteria.

From FATJACK to Solution Combination Only

All Attribute Group objects will be deleted and DA Result objects will be refreshed based on certain criteria.

From BEAMCHECK to FATJACK

All Mechanical results will be deleted and Attribute Group and DA Result objects will be refreshed based on certain criteria.

From BEAMCHECK to Solution Combination Only

All Attribute Group objects will be deleted and DA Result objects will be refreshed based on certain criteria.


Note:  The behavior described above also corresponds to the settings of the DAData and CombResults properties in the DAScripts section of the XML definition file. For BEAMCHECK, DAData=1 and CombResults=1; for FATJACK, DAData=1 and CombResults=0; for Solution Combination Only, DaData=0 and CombResults=1. So, for example, if you have the DAData and CombResults properties both set to 1 in a user defined XML file, and you change the DAData property to 0, the behavior would be that described in the From BEAMCHECK to Solution Combination Only entry above.


If the contents of any Design Assessment XML definition file change, the Mechanical application refreshes the existing Design Assessment objects as follows:

When the Group Type in use is not present in the file

The affected Attribute Group or DA Result is initialized to default values. Default values are the values which you get when an Attribute Group or DA Result is inserted in the tree.

When the Group Sub Type in use is not present in the file

The affected Attribute Group or DA Result is initialized to default values. Default values are the values which you get when an Attribute Group or DA Result is inserted in the tree.

When the Attribute IDs present for a Group Type and Sub Type combination in use are changed (IDs added or removed)

The affected Attribute Group or DA Result is initialized to default values. Default values are the values which you get when an Attribute Group or DA Result is inserted in the tree.

Group Type not in use is changed/added/removed

No existing Design Assessment objects are affected.

Group Sub Type not in use is changed/added/removed

No existing Design Assessment objects are affected.

Attribute IDs are changed/added/removed for a Group Type and Sub Type combination which is not in use

No existing Design Assessment objects are affected.

Validation/Default Value/Attribute Name/Geometry Application/Property type is changed

Design Assessment object is modified as indicated.


Note:  For any above mentioned change, the state of the system becomes obsolete, forcing the user to solve again.



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