What's New

View new features for Pulse 2023.

Altair Pulse 2023 Release Notes


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 1.
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 2.
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 3.
  • 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 4.
  • 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 5.
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 6.
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 7.


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 8.

Figure 9.
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.