What's New
View new features for Pulse 2023.1.
Altair Pulse 2023.1 Release Notes
Highlights
- The Generic, Launch, and Solver Run tasks have been merged into a single, more general block called Application Template.
- Sub-processes can now be created and edited in the Orchestrator profile.
- New functionality has been added to restore inputs to their default value.
New Features
- Application Template
- The Application Template is now the general task block in Pulse. Its
only obligatory parameter is the application itself.
Arguments can be passed through the block for the execution of the application, including a script. The functionality of the Generic task, Launch task, and Solver Run task is now covered by the Application Template.
Figure 1. - Restore Default
- New functionality has been added to restore all input values to their
default state. It can be applied through the RMB context menu to
individual modules or the whole process, and through the InputGUI by
clicking the arrow icon. It is available for all three profiles.
Figure 2.
Enhancements
- Sub-Process can now be created in orchestrator profile
- Orchestrators can now create a sub-process from the
Create ribbon or by grouping tasks together
through the RMB context menu.
Figure 3.The name of the sub-process can be changed through the Study Browser or by the Edit panel in sub-process.
Figure 4. - Enhanced Project Saving
-
- Pulse project content will not be created or updated until you Save As.
- If, when executed, the project is not yet created, you will be prompted to Save As.
- Modifications to the study and project names will now be represented in the Project Directory after saving.
Known Issues
The following 2023.1 Altair applications are not automatically registered. Users will have to register them manually. Right-click in the blank space of the Application Browser, select Create and enter data as seen in the table below. See Applications for more information.
| Name | Version | Location | Argument(s) | Display Image | Publisher |
|---|---|---|---|---|---|
| HyperMesh 2023.1 | 2023.1 | <InstallDir>\hwdesktop\hwx\bin\win64\runhwx.exe | -client HyperWorksDesktop -plugin HyperworksLauncher -profile HyperworksLauncher -l en -startwith HyperMesh | <InstallDir>\hwdesktop\hw\images\win\ productHyperWorksUnity.ico |
Altair |
| HyperView 2023.1 | 2023.1 | <InstallDir>\hwdesktop\hwx\bin\win64\runhwx.exe | -client HyperWorksDesktop -plugin HyperworksLauncher -profile HyperworksLauncher -l en -startwith HyperView -sf plugins/hwd/resources/splashHyperView.png | <InstallDir>\hwdesktop\hw\images\win\ productHyperView.ico |
Altair |
| HyperGraph 2023.1 | 2023.1 | <InstallDir>\hwdesktop\hwx\bin\win64\runhwx.exe | -client HyperWorksDesktop -plugin HyperworksLauncher -profile HyperworksLauncher -l en -startwith HyperGraph -sf plugins/hwd/resources/splashHyperGraph.png | <InstallDir>\hwdesktop\hw\images\win\ productHyperGraph.ico |
Altair |
| MotionView 2023.1 | 2023.1 | <InstallDir>\hwdesktop\hwx\bin\win64\runhwx.exe | -client HyperWorksDesktop -plugin HyperworksLauncher -profile HyperworksLauncher -l en -startwith MotionView -sf plugins/hwd/resources/splashMotionView.png | <InstallDir>\hwdesktop\hw\images\win\ productMotionView.ico |
Altair |
The following known issues will be addressed in a future release as we continuously
improve performance of the software:
- Although it’s possible to monitor a task input through process variables, it is not a recommended use case.
- Block Diagram known issues:
- Occasionally, the Block Diagram is not updated properly. To restore the correct display, save the session and reload.
- Navigating between studies through the window decoration in Block Diagram is only working intermittently.
- For HD graphic cards or monitors, the icon inside the block is displayed offset of the block.
Altair Pulse 2023 Release Notes
Highlights
- Orchestrator Profile
- A new profile, which allows for the build and execution of processes.
- New Variable Handling System
- Supports the creation of modularized tasks to enable building No-Code, Plug and Play processes.
New Features
- Orchestrator Profile
- A new profile (previously Only Author and Analyst), specifically targeting the Method Developer or Orchestrator, has been introduced. In this profile, you can build and execute a process leveraging ready to go modules from the library but will not be able to create new modules or modifying existing ones.
- New Variable Handling System
- Modifications and improvements have been made to the variable definition
and management to ensure the tasks created by the Author are contained
and modularized.
There are now two different types of variables: Task Variables and Process Variables.
Task Variables (Input/Outputs):- Task variables are associated with a specific task within a process.
- Used to collect inputs required for the task to operate and store the outputs generated by the task.
- Task variables can only be queried and edited by the task itself, meaning they are local to that task.
- These variables serve to communicate and exchange data between the task and the process.
Figure 5.Process Variables:- Process variables are associated with a process or a sub-process.
- They are used to control inputs or monitor outputs of tasks within the process.
- Process variables can be accessed and manipulated by multiple tasks within the process.
- In the case of nested processes, process variables are used to control the input/output to the sub-process.
- Process variables are more global in scope compared to task variables, as they can be shared and accessed by multiple tasks within the process.
Figure 6.
In addition to modularization, the motivation behind this improvement was to achieve
and support the following enhancements:
- Multiple task instances in the same process
- Multiple instances of the same module are now allowed in a process,
enabling flexibility and parallel execution.
Figure 7.
- Multiple instances of the same module are now allowed in a process,
enabling flexibility and parallel execution.
- Automatic mapping of inputs/outputs through an expression
- When connecting two tasks in Pulse, congruent outputs will be
automatically linked to inputs. You can modify the linked expression
to incorporate any required mathematical operations. This
flexibility allows for customization and transformation of data
before it is passed as input to the next task.
Figure 8.
- When connecting two tasks in Pulse, congruent outputs will be
automatically linked to inputs. You can modify the linked expression
to incorporate any required mathematical operations. This
flexibility allows for customization and transformation of data
before it is passed as input to the next task.
- Better control of data and its flow
- Process variables will help the orchestrator better control the data
and its flow in the process by controlling tasks inputs and
monitoring task outputs. See Process Variables for more
information.
Figure 9.
- Process variables will help the orchestrator better control the data
and its flow in the process by controlling tasks inputs and
monitoring task outputs. See Process Variables for more
information.
These improvements triggered the following changes:
- Output Value Definition
- Output Values can now exclusively be defined through the Process APIs in
script and execution of the task. It is the responsibility of the Author
to ensure that the generated output is correctly transferred properly to
the Output Variables in Pulse.
Figure 10. - Handle Output Files
- A new way to handle output files, by accessing the value through the
API. In this case, the name is
hardcoded:
set workdir [::pulse::GetWorkingDir] ::pulse::SetVariableValue Linear_solverDeck "$workdir/pressure.fem" - Process Variables Management in the Variable Browser
- Process variables can be managed through the Variable Browser, which is
available for all profiles. Inputs and outputs of tasks can only be
managed through the Task itself and is only exposed to the Author.
Figure 11.
Enhancements
- Provide Required Inputs to Modules before Execution
- Ensure all input is provided before execution to ensure the process.
Once started, it can run without disruptions. This is available for all
profiles and can be found through the Task Context menu. Note: If all input is provided, the Input dialog will not be launched when the task is executed.
Figure 12.
Figure 13. - Unified Sub-process Entity
- Automations and Solutions are now unified under the Sub-Process entity.
Known Issues
The following known issues will be addressed in a future release as we continuously
improve performance of the software:
- Although it’s possible to monitor a task input through process variables, it is not a recommended use case.
- Undo/Redo operations are currently not supported.
- Loops are currently not supported, even though the Block Diagram can be used to create them.
- If Project and Study names are changed in Pulse, the respective Directory names are only updated through Save As.
- Block Diagram known issues:
- The Block Diagram is intermittently not updated properly.
- To restore the proper display, save the session and reload.
- Navigating between studies through the window decoration in a block diagram is intermittently working.
- For HD graphic cards or monitors, the icon inside the block is displayed off-set of the block.
Resolved Issues
- Pulse is now supported on Linux.