hm_batchexportenginefile

Exports Radioss engine and starter files.

Syntax

hm_batchexportenginefile type filename export_template

Type

HyperMesh Tcl Query

Description

Exports Radioss engine and starter files.

Inputs

type: The type of file to write:; 1 - Export engine file only; 2 - Export engine file and starter model file separately.; 3 - Export engine file and starter model file as a single file.
filename: The full path and filename of the output file. Paths with spaces must be enclosed in quotes.; This is the starter file name. The engine file name is derived from this name.
export_template: The full path and filename of the export template to be used. Paths with spaces must be enclosed in quotes. Required only for type=2 and type=3.

Examples

To export only the engine file (the engine file name starterD01 is derived from the model file name starterD00. starterD01 will be the name of the engine file that will be exported):

hm_batchexportenginefile 1 "C:/my_files/starterD00" "[hm_info -appinfo SPECIFIEDPATH TEMPLATES_DIR]/feoutput/radioss/radioss110.blk"

To export both the starter and engine files separately (the starter file is named starterD00 and the engine file is named starterD01):

hm_batchexportenginefile 2 "C:/my_files/starterD00" "[hm_info -appinfo SPECIFIEDPATH TEMPLATES_DIR]/feoutput/radioss/radioss110.blk"

To export both the starter and engine files as a single file (named starterD00):

hm_batchexportenginefile 3 "C:/my_files/starterD00" "[hm_info -appinfo SPECIFIEDPATH TEMPLATES_DIR]/feoutput/radioss/radioss110.blk"

Errors

Incorrect usage results in a Tcl error. To detect errors, you can use the catch command:

if { [ catch {command_name...} ] } {
   # Handle error
}

Version History

11.0.130