Get back results in FluxMotor
1. Introduction
All the motors resulting from the operations performed with Altair® HyperStudy® can be used back in Motor Catalog of Altair® FluxMotor®, and then these can be edited in Motor Factory very quickly.
|
|
Motor Catalog – Visualization of results got from HyperStudy® | |
1 | A catalog is automatically built by using the name of the connector defined by the user |
2 | All the operations from HyperStudy® are stored in the dedicated catalog |
3 | Each motor can be selected, visualized and edited in the Motor Factory, to be evaluated more in depth |
2. Connection between FluxMotor® and HyperStudy®
Before starting new studies in HyperStudy® by using connectors exported from FluxMotor®, FluxMotor must be registered as a new solver script in HyperStudy®.
This must be defined only while using the coupling for the first time.
|
|
Connection between FluxMotor® and HyperStudy® | |
1 | Open the area in HyperStudy® to register FluxMotor 2024.1 script |
2 | Path where FluxMotor.exe must be selected to be registered as a new
solver in HyperStudy®. Note: FluxMotor
s .exe with a “s” at the end of FluxMotor
s. This must be defined only while using the
coupling for the first time Note: Since the
version 2022.1 of HyperStudy, the FluxMotor solver script is
automatically registered, when the default path installation is selected
while installing Flux and FluxMotor. |
The connectors used in HyperStudy must be synchronized with the FluxMotor solver version.
An error message (inside the log files) is generated while performing HyperStudy studies with a connector provided with a former version of FluxMotor solver.
A connector provided with FluxMotor version N-1 (or older) cannot be used in HyperStudy where the FluxMotor Solver Version N (or newest) is selected.
Since the FluxMotor 2022.3 version, each time a connector is generated, a ConnectorUpdater.py file is provided and located in the same folder as the connector
Thanks to this script, the user can update an older HyperStudy connector generated with a former version of FluxMotor.
Please refer to the document MotorFactory_2024.1_Introduction.pdf for additional information in the section dedicated to HyperStudy.
|
Path to HyperStudy – Needed for HyperStudy export – It must be defined in the user preferences (Supervisor of FluxMotor) |