HyperWorks Desktop

*RegisterSolver()

Registers a solver in the MotionView window.

*RegisterSolver()

Registers a solver in the MotionView window.

Previous topic Next topic No expanding text in this topic  

*RegisterSolver()

Registers a solver in the MotionView window.

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

Syntax

*RegisterSolver( solver, "label", SOLVER_INPUT_EXT, "ext", [SOLVER_COMMAND_EXT], "ext", [SOLVER_PARAM_EXT], "ext", [GRAPHICS_EXT], "ext", [SOLVER_DLL], "path/file")

Arguments

Name

Description

 

solver

The varname of the solver being registered.

 

"label"

The label of the solver that will show in the Solvers drop down menu.

 

SOLVER_INPUT_EXT

The extension of the solver input file.

 

[SOLVER_COMMAND_EXT]

The extension of the solver command file.

 

[SOLVER_PARAM_EXT]

The extension of the solver parameters file.

 

[GRAPHICS_EXT]

The extension of the solver graphics file.  Can be the same as the solver input file.

 

SOLVER_DLL

The full path of the solver dll.

Example

*RegisterSolver( ABAQUS, "ABAQUS", SOLVER_INPUT_EXT, "inp", SOLVER_DLL, "d:/abaq_writer.dll" )

Application

MotionView.

Context

*BeginMDLDefaults()

*BeginModelDefaults().

Comments

The functionality in *RegisterSolver() can be used in two ways:

The contents of Templex templates of the corresponding type (solver input, solver command, solver param, and graphics) will export to a file with the name determined by the solver base name and extension.

For example, the contents of a Templex template of type GRAPHICS is written to test.inp if the file name in the Run panel is test and the registered extension for GRAPHICS_EXT is inp.  Note: For Templex templates to be written to a solver command file, an instance of the template must occur in an *Event block.

The use of the API where an advanced user writes a "solver writer" in C++ and compiles it into a dll.

See also

 

List of Preference Statements