Summary of Abaqus Scripting Interface changes between Abaqus 6.14 and Abaqus 2016

This section summarizes the changes and the additions that have been made to the Abaqus Scripting Interface between Abaqus 6.14 and Abaqus 2016. SIMULIA makes every attempt to have the Abaqus Scripting Interface be backward compatible, and Abaqus can execute most Abaqus Scripting Interface scripts from previous versions of Abaqus. However, backward compatibility is not guaranteed beyond two versions of Abaqus, and it is recommended that you upgrade your commands to the most recent version.

To help you determine the status of your scripts, Abaqus displays a dialog box listing the deprecated commands when you execute the script from the main menu using FileRun Script. You are advised to upgrade scripts that contain deprecated commands as soon as possible. To run the upgrade utility, type the following command at the system prompt:

abaqus python -m upgradeScript [options] scriptName [scriptName ...]

scriptName can be either a file or a directory. You can also enter a wildcard (*) rather than a directory to upgrade all scripts within the current working directory. The options for the upgrade utility are:

`-fileNames` fileName	Read a list of file names from the file specified.
`-logfileName` logFileName	Specify the name of the log file.
`-backup`	Whether to make backup versions of the upgraded files. By default, no backup versions are created.
`-preview`	Preview the changes to the file instead of changing the file.
`-diffExecutable` application	The application used to display the differences between the script and the upgraded script. By default, the differences are displayed by a web browser.

The upgrade utility upgrades your scripts to the most recent version of Abaqus, regardless of when they were created. The upgrade utility upgrades both kernel commands and GUI commands. If scriptName is a directory, the upgrade utility upgrades each script in the directory. For example,

abaqus python -m upgradeScript -preview tireSlip.py tireWear

would preview all of the upgrades to the tireSlip.py script and to all of the scripts in the tireWear directory.

More options are available if you use the upgradeScript method in an Abaqus Scripting Interface script to upgrade your scripts. For more information, see “Upgrade script commands,” Section 53.10. In addition, an Abaqus plug-in is available that provides a graphical interface to the upgradeScript method. For more information, see “Upgrading a script,” Section 82.5 of the Abaqus/CAE User's Guide.

Alternatively, you can run the following upgrade utilities from the command line interface. The same options are available as for the upgradeScript function.

The upgradeScriptM_N utility allows you to upgrade a kernel script from one version to another (where M and N are general release numbers without any punctuation); for example,
```
abaqus python –m upgradeScript614_2016 filenames
```
The upgradeGuiScriptM_N utility allows you to upgrade a GUI script from one version to another (where M and N are general release numbers without any punctuation); for example,
```
abaqus python –m upgradeGuiScript614_2016 filenames
```

In the following list of modified commands, objects and methods are listed along with the required and optional arguments. Arguments enclosed within angle brackets, “< >”, are optional arguments. The syntax of the commands is as follows:

(Blue bold text)	New method or argument.
(Red italic text)	Removed method or argument.
(Green italic text)	Changed argument; for example, the argument type has changed or the possible values of the SymbolicConstant have changed.

You can click on an entry to view its description in the command reference. Refer to the Abaqus Scripting Reference Guide for Abaqus 6.14 for a description of items that have been removed.

Abaqus/CAE Display Preferences commands

No changes.

Adaptivity commands

No changes.

Amplitude commands

No changes.

Animation commands

No changes.

Annotation commands

Text(<font>)

Assembly commands

Assembly.getMassProperties(<regions>)

Basic geometry commands

CellArray(cells)

Edge.isTangentFlipped

EdgeArray(edges)

FaceArray(faces)

VertextArray(vertices)

Beam section profile commands

No changes.

Boundary condition commands

No changes.

Calibration commands

Behavior.compute_E(dataSet)

Behavior.compute_elasticModulus(yieldPoint)

Behavior.compute_nu(dataSet)

Behavior.compute_plasticPoints(dataSet, slider_val, start_index, end_index<, yp>)

Behavior.compute_ultimatePoint(dataSet)

Behavior.mapToMaterial(materialName)

Behavior.setValues(<E, nu, ds1Name, ds2Name, materialName, yieldPoint, ultimatePoint, plasticPoints, PoissonsRatio, elasticModulus, plasticPointsRange, name, uniaxialName, biaxialName, interpolation, uniWeight, biWeight, uMullinsReload, uMullinsUnload, uPYieldPoint, uPermSet, uPrimary, bMullinsReload, bMullinsUnload, bPYieldPoint, bPermSet, bPrimary>)

Behavior.xyDataDissect(dsName, modelName, calibrationName<, biaxial>)

DataSet.setValues(<data>)

ElasIsoBehavior(name, typeName)

ElasIsoBehavior.setValues(<E, nu, ds1Name, ds2Name, materialName>)

ElasPlasIsoBehavior(name, typeName)

ElasPlasIsoBehavior.setValues(<yieldPoint, ultimatePoint, plasticPoints, PoissonsRatio, elasticModulus, ds1Name, ds2Name, materialName, plasticPointsRange, name>)

FeFpBehavior.FeFpBehavior(name, typeName)

FeFpBehavior.setValues(<uniaxialName, biaxialName, interpolation, uniWeight, biWeight>)

Canvas commands

No changes.

Connector commands

No changes.

Constraint commands

No changes.

customKernel module

No changes.

Datum commands

No changes.