HyperWorks Solvers

Types of User-Written Subroutines

Types of User-Written Subroutines

 Previous topic Next topic No expanding text in this topic  

Types of User-Written Subroutines

 Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

To facilitate the creation of solver extensions, MotionSolve provides you with a well-defined interface and a well-defined methodology for creating user subroutines. This is explained in Table-2 below.

Subroutine Type

Purpose

Driver Subroutines

These are user-written subroutines that allow you to create and execute your own types of analyses. These analyses are typically composed of level analyses that are provided to you by MotionSolve.

For more information about Driver subroutines, see the topic Driver Subroutines.

Utility Subroutines

These are functions that are useful when writing user-written subroutines. There are three types of Utility subroutines:

•Data Access subroutines, which are built-in subroutines provided by MotionSolve that allow a user-written subroutine to access model parameter or information state.
•Analysis control subroutines, which are built-in subroutines provided by MotionSolve that allow a user-written subroutine to perform various types of analysis, generate output and modify the model defined in the XML input file.
•General utility functions that aid in the creation of user-subroutines.

These subroutines are packaged within MotionSolve and their interface is documented, so that you can simply use the functions you need. You need not recreate these.

For more information about Utility subroutines, see the topic Utility Subroutines.

Modeling Subroutines

These are user-written subroutines that allow you define the run-time behavior of a modeling element via a user subroutine.

For more information about Modeling subroutines, see the topic Modeling Subroutines.

Table-2: The subroutine interface provided by MotionSolve