HyperStudy 2017.1 & FLUX 2018.1.1

Can you please upgrade to HyperWorks Desktop 2017.3 and try this feature.

Unable to find an attachment - read this blog

Hello Rahul,

My issue is not with FluxMotor. I am using Flux software for my simulation.

Could you please help me with the configuration?

I just tried to drag and drop the .F2G component from FLUX the same way as the FluxMotor component is in the video, and the same error was shown.

Can you please upgrade to HyperWorks Desktop 2017.3 and try this feature.

Unable to find an attachment - read this blog

Did you try this in HyperStudy 2017.3?

I requested that version to the software resource administrators, and I am currently waiting to their response. I am still using version 2017.1. As far as I am concerned, it is suposed that this version allows FLUX to be linked to HyperStudy.

I managed to enter the solver script settings, and it seems that there is no solver file specified for FLUX.

I have FLUX installed in C:/Program Files/Altair/2018/flux/ Do I need to set the path to a file in the empty dialog?

<?xml version="1.0" encoding="UTF-8"?>

I guess this is because of version compatibility. Flux 2018.1 was released in September 2018 & HyperWorks 2017.3 in December 2018.

Could you share the screenshot of the system and update the information?

Please also refer to the attached pdf note section to define the solver installation path.

Unable to find an attachment - read this blog

Hello Rahul, 

It took me a while to find the information. Concerning the solver installation path, which is the file of the solver that I have to set in the dialog? 

I guess this is because of version compatibility. Flux 2018.1 was released in September 2018 & HyperWorks 2017.3 in December 2018.

Could you share the screenshot of the system and update the information?

 

Please also refer to the attached pdf note section to define the solver installation path.

Unable to find an attachment - read this blog

Please check for the below file.

Hello Rahul,

I got  an error when trying to evaluate a nominal run. Shouldn't I try with Flux.exe instead? Isn't there any tutorial on how to set up both applications in order  to optimize FEM models?

   36 Message: Imported variables from model ( Model 1 (m_1) )

                   Number of design variables ( 6 )

                   Number of responses        ( 1 )

   37 Message: Generating design for ( Setup (nom_1) ) - ( Nominal Run )

   38 Message: Saved study ( LSM_OptimizazioaHutsean (lsmoh) )

   39 Error  : Could not run model ( C:\Simulaketak\a_LSM\a_Hutsean\d_HyperStudy_Konponentea\LSM_OptimizazioaHutsean.F2G )

               WindowsError: [Error 740] La operación solicitada requiere elevación

   40 Error  : File not found:  C:/Simulaketak/a_LSM/a_Hutsean/d_HyperStudy_Konponentea/approaches/nom_1/run__00001/m_1/hst_output.hstp

   41 Error  : Subcase (  ) not found in file ( C:/Simulaketak/a_LSM/a_Hutsean/d_HyperStudy_Konponentea/approaches/nom_1/run__00001/m_1/hst_output.hstp )

   42 Error  : Failed to extract ( FEM (v_1) )

                Subcase:(  )

                Type:( Output )

                Request:( FEM )

                Component:( Value )

                Reader:(  )

               Does not exists ( C:/Simulaketak/a_LSM/a_Hutsean/d_HyperStudy_Konponentea/approaches/nom_1/run__00001/m_1/hst_output.hstp )

   43 Error  : Cannot evaluate expression ( v_1[0] ), Unknown symbol 'v_1'

               Check if all expressions, preference files, sources and other components are valid.

   44 Message: Saved study ( LSM_OptimizazioaHutsean (lsmoh) )

<?xml version="1.0" encoding="UTF-8"?>

Yes please try with flux.exe.

Now it seems that it runs the model but it fails when extracting the results.

<?xml version="1.0" encoding="UTF-8"?>

57 Error : File not found: C:/Simulaketak/a_LSM/a_Hutsean/d_HyperStudy_Konponentea/approaches/nom_1/run__00001/m_1/hst_output.hstp

 58 Error  : Subcase (  ) not found in file ( C:/Simulaketak/a_LSM/a_Hutsean/d_HyperStudy_Konponentea/approaches/nom_1/run__00001/m_1/hst_output.hstp )

 59 Error  : Failed to extract ( FEM (v_1) )

                Subcase:(  )

                Type:( Output )

                Request:( FEM )

                Component:( Value )

                Reader:(  )

               Does not exists ( C:/Simulaketak/a_LSM/a_Hutsean/d_HyperStudy_Konponentea/approaches/nom_1/run__00001/m_1/hst_output.hstp )   60 Error  : Cannot evaluate expression ( v_1[0] ), Unknown symbol 'v_1'

               Check if all expressions, preference files, sources and other components are valid.

Try by changing the model folder directory from C drive to D drive. My final suggestion to you is to try the same setup after registering solver script in HyperStudy 2017.3

Hello Rahul, I do not have any D drives in my computer.

Is there any other person I can contact with in order to solve this issue?

Hi,

You will find attached a PPT file explain different steps that you need to follow to make the optimization. I think it is better if you update your HyperStudy version (download the version 2017.3).

Best regards.

Unable to find an attachment - read this blog

Hello Abdessamed,

Thank you for your answer, I will give it a go.

BR,

Imanol

In the end I installed the 2019 versions of both FLUX and HyperStudy and now it seems to work.

Thank you for your help!

Best regards,

Imanol

Hi @Rahul R,  @Abdessamed  !

I followed the video tutorial on FluxMotor-HyperStudy coupling. 

At the step of running definition I get the error attached below.

Regards,

Rok

Unable to find an attachment - read this blog

Which version of HyperStudy and Flux you are using?

AltairFluxMotor 2019.0.2 with hotfix_win64

HyperStudy 2019

Can you try this with the latest version of HyperStudy 2019.1.

<?xml version="1.0" encoding="UTF-8"?>

Already have hotfix hwDesktop2019.1.1_hotfix_win64

Could you please share the screenshot of message log of HyperStudy?If possible please share .xml or .hstudy file.

12 Warning: Execute errors (stderr) logged to file ( \forhyperstudy1\approaches\setup_1-def\run__00001\m_1\task__exe_stderr.txt ).

13 Error  : Execute task failed For more information see ( \forhyperstudy1\approaches\setup_1-def\run__00001\m_1\task__exe_err.txt )

When saving runs from HyperStudy in FluxMotor catalog, the name of the HyperStudy approach is used in the motor name, and since HyperStudy 2019.1 version, this approach name can contain dash, which is a forbidden character in motor names, causing a failure when the motor is saved in the catalog dedicated to the current optimization project.This seems to be an issue and may get resolved in upcoming version of Fluxmotor.

If it too urgent then I would recommend you to use HyperStudy 2019 to bypass this issue.

Thanks for answer.

very useful the information