HyperStudy Tips and Tricks: #15 – Top 5 Guide of the HyperStudy-FluxMotor User

Diana_38240

The guide below is intended to help you improving your exploration and optimization studies based on FluxMotor solver, and to figure out and fix eventual errors you may encounter.

 

1. For the first use of HyperStudy with FluxMotor, user needs to define the solver installation path to the FluxMotors.exe (otherwise you will see the message “Path isn't provided for solver ...” when you click on Import Variables).

 

 

2. User is recommended to run System Bounds Check (3 evaluations) rather than Nominal run only to verify the parameters ranges. If you run to failures, it means that some lower and/or upper bounds are too low/high and you need to review them.

 

 

3. User is recommended to add constraints on the input variables to avoid/reduce the number of failures due to unfeasible designs (inability to update the geometry due to defects such as line intersections). At minima, user is recommended to define, on HyperStudy side, the constraints available within the FluxMotor Part Factory.

 

 

4. If you see this message when you click Run Definition,

 

it means that some model resource files cannot be copied under the run folder because of the path length to the location where your HstConnector is located. This is a Windows limitation on the path length (number of characters). To avoid this behavior, user is suggested to use shorter paths (save your files at an upper directory).

 

5. Be aware that HstConnectors exported from FluxMotor versions anterior to version 2022 are version limited. For instance, if you set a FluxMotor connection defined with HstConnector exported from FluxMotor v2020 you can run it with FluxMotor v2020 only (solver script should be defined with FluxMotors.exe in v2020 installation). Similarly, if someone share with you an archive with FluxMotor setup, you need to check the version of the HstConnector and use the “right” solver version to run the study on your side (otherwise the evaluations will fail). A turn around solution is to re-export the HstConnector from the FluxMotor version you want to use.

 

Was this helpful? Let us know your feedback!

 

 

1_fxm_blog_6.PNG

Altair_CommunityBlog_Default-20.jpg

fxm_blog_3.PNG

Ahmed jasim

Hi Diana

can you explain in more detail about point 4

Best regards