hm_jobs_submitOptistructJob
Submits a OptiStruct job to the server.
Syntax
hm_jobs_submitOptistructJob version job_name memory cpu input_file output_path additional_files zip_flag args
Type
HyperMesh Tcl Query
Description
Submits a OptiStruct job to the server.
Returns the job ID upon successful submission, or null on failure.
Always set the current server on which the job needs to be submitted by using hm_jobs_setCurrentServer before submitting a job. To run jobs locally using PBS-sensor, set the current server as "local". Jobs submitted using the local server will run in sequential order. For local job submission, the additional_files and zip_flag arguments can be passed as null strings, and the master file should hold all the information related to the additional files.
Inputs
- app_id
- The application name to which the job has to be submitted to (for example, OptiStruct).
- version
- The OptiStruct version to use (for example, 2017).
- job_name
- The name of the job to submit.
- memory
- The memory required for the job to run.
- cpu
- The number of CPUs to be used.
- input_file
- The full name and path of the input file.
- output_path
- The full path where the output should go.
- additional_files
- A string containing any required additional files that need to be uploaded.
- zip_flag
- Must be set as "true" if any .zip file is passed, "false" otherwise.
- args
- Any additional OptiStruct command line arguments.
Examples
To submit a OptiStruct job on the server:
hm_jobs_submitOptistructJob OptiStruct 14.0 "new_job" 1000 2 "C:/temp/input/MASTER.fem" "C:/temp/output" "{C:/temp/input/slave1.fem} {C:/temp/input/slave2.fem}" false "-maxlen 3000"Errors
if { [ catch {command_name...} ] } {
# Handle error
}Version History
14.0.130