As of HyperX version 2026.1.13, you can use the Project Runner to queue and run many concurrent Sizing, Analysis, and/or HyperFEA operations. This can be run with or without a Database/Project open.
You can open the Project Runner from the Run tab of the Ribbon. Click on the "Batch Runs" button and select "Project Runner" from the pop-up menu.
When you are running the Project Runner standalone, i.e. without an open Database/Project, no Runs will be defined. If opened from within a Project, it will automatically include a Sizing Run for the current Database and Project.
Each Run represents an operation (Sizing, Analysis, or HyperFEA) performed on a particular Database and Project. Multiple Runs can be defined to perform operations concurrently - Projects from different Databases can be run in parallel but Projects from the same Database must be run in sequence. The "Concurrent Projects" setting defines how many Projects can be run in parallel and the allowed values are 1 through the max number of CPU resources available. If left blank, all available CPU resources will be used.
Add Runs using the corresponding button and define them with the following fields:
-
Checkbox - Use this checkbox to activate/inactivate Runs.
-
Database - The Database for this Run.
-
Project - The Project for this Run.
-
Run Mode - Define the operation for this Run: Sizing, Analysis, or HyperFEA.
-
HyperFEA Iterations - If the Run Mode is HyperFEA, this field activates, allowing you to define the number of HyperFEA Iterations and access Solver Setup/Batch File settings.
Note
Other HyperFEA settings such as Convergence Criteria and FEA Constraints are defined on the HyperFEA form, and the Project Runner will use whatever Convergence Criteria/FEA Constraints are defined there.
Each Run also features a "Status" field that displays information about this operation as the Runs are processed. This includes “Launching”, “Running”, error messages, color statuses for success/fail, and some HyperFEA logging. You can double-click on this field to open another window with a full log of status messages for this Run.
The top of the form features additional settings that can modify how the Runs' operations are performed and utilities for importing/exporting Run definitions from/to Excel to aid editing and sharing Run definitions.
Excel Utilities
Larger sets of Runs can be more easily edited and/or shared in the form of Excel spreadsheets. The Project Runner features the following Excel-centric utilities:
-
Edit in Excel - Export and open an Excel version of the Runs Table.
-
Read from Excel - After editing the Runs Table in Excel, use this button to reload the table into the Project Runner.
-
Import from Excel - You can import any Runs Table from Excel into the Project Runner. This makes it easier to share many defined Runs between users or Projects.
Note
In the Excel version of the table, you can only set the number of HyperFEA Iterations. You cannot use it to access other HyperFEA settings like you can in the Project Runner.
When you're satisfied with your settings and have defined all necessary Runs, click the blue "Run" button to process them. Recall that Run operations are processed concurrently - Projects from different Databases can be run in parallel but Projects from the same Database must be run in sequence.
Once running, you can press the "Stop" button to terminate the operations were they currently stand. You can use the "Status" field(s) to observe the progress of each Run.
After cancelling, you can see which operation(s) were cancelled via the "Status" field(s). Note that if you cancel during HyperFEA, you should consider toggling "Reset before iterating" before restarting the operation.
When Run(s) are complete, the "Status" field will update to reflect that. Recall that you can double-click on this field to open another window with a full log of status messages for this Run.