Using the Abaqus PDE with custom applications

Custom applications are scripts created to modify or add functionality to Abaqus/CAE. They typically use a combination of the Abaqus Scripting Interface commands and the Abaqus GUI toolkit commands to extend the user interface and the underlying kernel commands. Custom applications are launched concurrent with the start of an Abaqus/CAE session, and they are integrated into the existing functionality.

Context:

If the application contains both kernel and GUI functions, you must trace them separately. Tracing the kernel and GUI functions separately prevents problems that can occur in Abaqus/CAE as the Abaqus PDE attempts to switch between kernel and GUI modes while the code is running. Separating the functions also provides a logical approach to locating problems in the kernel code versus ones in the GUI code.

  1. Enter the following at a command prompt to start the Abaqus PDE and the custom application:

    abaqus pde -pde [args]

    where abaqus is the command you use to start Abaqus and args are the arguments required to start the custom application. For example, if you enter abaqus cae -custom xxx.py to start Abaqus/CAE and your application, enter abaqus pde -pde -custom xxx.py.

    Note:

    You cannot start the custom application and launch the Abaqus PDE from within Abaqus/CAE since the initial startup processes would already be complete.

  2. Open the file that you want to debug.

  3. Position the cursor where you want to add a breakpoint. Click mouse button 3, and select Add Breakpoint. (For more information, see Using breakpoints.)

  4. Click Start CAE at the top right of the Abaqus PDE to start Abaqus/CAE with the custom startup commands.

  5. The application code appears in the Abaqus PDE window, stopped at a breakpoint.

  6. Use the Abaqus PDE controls and options described in the previous sections to step through the execution of the custom application.