Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

Python Batch Mode Difference in GUI vs no-GUI

When I run my python script in batch mode through the console, it crashes when I use import hm. It works fine when I run it through the python console in GUI. Why is there this discrepancy?

Code that doesn't output anything when I check it through batch_log.txt:

Code that works when I check it through batch_log.txt:

What batch_log.txt says when it works:

The command I run:

runhwx.exe -client HyperWorksDesktop -plugin HyperworksLauncher -profile HyperworksLauncher -l en -startwith HyperMesh -b -f C:\hypermesh_batch_test.py

Find more posts tagged with

HyperMesh

v2025.1

Accepted answers

All comments

William Kuo_21386

I found the issue but not a solution. Apparently running hm.Model() without setting the name crashes in batch model. The only way it works is if I use hm.Model(name="name").

However, if I set model = hm.Model(name="name"), I can't run model.deletemodel() without crashing the script in batch mode.

William Kuo_21386

I searched up the dir() of various methods and I found out that some of them have substantial differences between batch mode and GUI.

For example, batch mode for dir(hm.entities) does not have "Component", meaning I can't make components in batch mode.

FYI these are settings I used:

runhwx.exe -client HyperWorksDesktop -plugin HyperworksLauncher -profile HyperworksLauncher -l en -startwith HyperMesh -b -f

William Kuo_21386

I figure out the difference. The -plugin used has to be HyperworksGeneral and not HyperworksLauncher. The -profile used has to be HyperworksGeneral and not HyperworksLauncher. These enable all the properties and methods for the modules that is typically used in the GUI.