Run HyperWorks on Windows
The installation process creates an HyperWorks group under All Programs on the Start menu for Windows 7 and under the Apps menu for Windows 10.
The default name of the group can be changed during installation. Most applications can be started using the following instructions.
Run a HyperWorks Product
Run a HyperWorks Product through ConnectMe
ConnectMe provides you with an alternative way to manage and launch installed HyperWorks products, receive notifications of new product updates, download Altair products, and get access to most recent Altair news.
ConnectMe is installed by default with HyperWorks Desktop and HyperWorks Solvers packages.
Change the Default Working Directory on Windows
For Windows 7/10, the default working directory specified by a HyperWorks application is %USERPROFILE%\Documents.
Applications That Run in Batch Mode
The following table provides some examples of batch applications and their input file requirements. The details of how to run an application in batch mode can be found in the help of individual applications.
Application | Script Name | Required Input File |
---|---|---|
Radioss 1 Step | hfsol.bat | Use base name of .parm file |
HyperMesh batch | hmbatch.exe | -cfilename.cmf or -tcl <tcl_filename> |
HyperStudy | hstbatch.exe | <filename>.xml |
MotionSolve | motionsolve.bat | filename.xml or filename.acf (ADAMS command file) |
OptiStruct | optistruct.bat | File in Bulk format (.fem file) |
BatchMesher | hw-batchmesh | CAD input file |
Radioss | radioss.bat | File in Block or Engine format (.rad) |
Launch a Batch Application
HyperWorks/Client Cache Management
The HyperWorks server/client cache management system allows for GUI applications, such as HyperMesh and HyperWorks Desktop, to cache files onto a client’s machine for faster invoke times.
The cache is versioned and the client user should maintain the necessary files for new and old versions.
The cache is supported only for Windows server/client setups. The default behavior of a server/client HyperWorks setup does not cache any files.
On first invoke, the applications will check to see if the environment variable ALTAIR_CACHE_HOME is set. If so, the application will copy over all required files to the specified directory through a background process after the products initialize. There will not be any increase in invoke speed this first time. Once this is completed, subsequent invokes will use the variable to check and find the versioned files and use the files stored locally to the client instead of reading the files over the network.
hw_cachemgr.exe -option
?-silent?
.- -option
-
- -query
- Display a message if the cache is ready for use. Always returns zero.
- -create
- Create the cache if it is not being deleted. Returns zero if successful.
- -delete
- Delete the cache if it is not being used. Returns zero if successful.
- -silent
- Do not display messages.
- The client user is responsible for adding the ALTAIR_CACHE_HOME environment variable to enable this functionality.
- The client user must have write access to the ALTAIR_CACHE_HOME directory.
- The client user must have enough disk space available for the cache, which is approximately 120 MB to 150 MB of storage.
- The client user is responsible for deleting the cached files when no longer needed.
Logging of cache messages can also be enabled via the ALTAIR_CACHE_LOG environment variable.