Allows user-solution subroutines to be activated or deactivated.
Rnam3, . . . ,
User-defined solution subroutine names to be activated. Up to nine may be defined on one
command or multiple commands may be used. If
Rnam1 = ALL, activate
all valid user subroutines. If
Rnam1 = NONE, deactivate all valid
user subroutines. All characters are required:
Allows user defined scalar field (body force) loads.
Allows user defined convection (surface) loads.
Allows user defined pressure (surface) loads.
Allows user-defined heat flux (surface) loads.
Allows user-defined charge density (surface) loads.
Computes the complex load vector for the frequency domain logic.
Allows user supplied element output.
Allows user control of the hygrothermal growth.
Allows user access before each solution.
Allows user access before each load step.
Allows user access before each substep.
Allows user access before each equilibrium iteration.
Allows user access after each equilibrium iteration.
Allows user access after each substep.
Allows user access after each load step.
Allows user access after each solution.
Allows user access at end of run.
Allows user access to element matrices and load vectors.
Allows a user-defined time step, overriding the program-determined time step.
Allows user-defined convergence checking, overriding the program-determined convergence.
Allows certain user-solution subroutines to be activated or deactivated (system-dependent). This command only affects the subroutines named. Other user subroutines (such as user elements, user creep, etc.) have their own activation controls described with the feature.
UAnBeg subroutine that allows user access at
the start of a run does not require activation by this command; it is automatically activated
when the program is started.
The routines are commented and should be listed after performing a custom installation from the distribution media for more details. See also the Advanced Analysis Guide for a general description of user-programmable features.
Users must have system permission, system access, and knowledge to write, compile, and link the appropriate subroutines into the program at the site where it is to be run. All routines should be written in FORTRAN. (For more information on FORTRAN compilers please refer to either the ANSYS, Inc. Windows Installation Guide or the ANSYS, Inc. Linux Installation Guide for details specific to your platform or operating system.) Issue USRCAL,STAT to list the status of these user subroutines. Since a user-programmed subroutine is a nonstandard use of the program, the verification of any ANSYS run incorporating these commands is entirely up to the user. In any contact with ANSYS customer support regarding the performance of a custom version of the ANSYS program, you should explicitly state that a user programmable feature has been used.
This command is also valid in PREP7.