AbaqusScripting package

This subpackage allows the user to use inPy directly in abaqus, to use the scripting mode, you need to copy the inPy folder in $SIMULIA\Abaqus614\6.14-1\tools\SMApy\python2.7\Lib it should also work with $SIMULIA\Abaqus614\6.14-1\tools\SMApy\python2.6\Lib)

AbaqusScripting.inPy_Abq_Classes module

class AbaqusScripting.inPy_Abq_Classes.ASBeamMesh(Namestr, ElemType, Radius, TypeStr, PosStr, NodeList=[], ElemList=[], Node0=1, Elem0=1)

Bases: inPy.Classes.FEM.BeamMesh

This class is the inPy.AbaqusScripting equivalent of the BeamMesh class in inPy. All the attributes are similar and the methods are herited from the inPy.node class

A new method is introduced to generate a beam directly in abaqus

Generate()

class AbaqusScripting.inPy_Abq_Classes.ASnode(X, Y, Z, ID)

Bases: inPy.Classes.FEM.node

This class is the inPy.AbaqusScripting equivalent of the node class in inPy. All the attributes are similar and the methods are herited from the inPy.node class

A new method is introduced to generate a node directly in abaqus

Generate()

AbaqusScripting.inPy_Abq_Classes.random() → x in the interval [0, 1).

AbaqusScripting.inPy_Abq_Functions module

AbaqusScripting.inPy_Abq_Functions.FrameGen(step, odb)

RAM, RAM never changes, The end of the program occurred pretty much as we had predicted. Too many steps, too many nodes, not enough space or resources to go around. The details are trivial and pointless, the reasons, as always, purely computational ones.

AbaqusScripting.inPy_Abq_Functions.GatherCoordinatesInTable()

The coordinates are stored in a numpy array with the structure: | Instance_Node | Node ID | X(t = 0) | Y(t = 0) | Z(t = 0) | … … … | X(t = i) | Y(t = i) | Z(t = i) |

AbaqusScripting.inPy_Abq_Functions.random() → x in the interval [0, 1).

AbaqusScripting.inPy_Abq_Functions.toFile(odb, stepName, FieldName, Filename, InitFrame=True)

Module contents