HyperStudy 2019.1 Solver Input File & Data Source

Maximilian Paulsen
Maximilian Paulsen Altair Community Member
edited September 2023 in Community Q&A

Hello,
 
I have two questions regarding the HyperStudy 2019.1 application.
I am currently in the process of familiarizing myself with the optimization using the application mentioned.
The kinetic model of the lifting arm mechanism of a wheel loader created in MotionView needs to be optimized with regard to the piston forces that arise.
These forces are measured at the translational joints of the indicated cylinders and are available as output.
The input variables are the coordinates of the respective connection points of the cylinders.
 
Questions:

  •     When defining the model in HyperStudy, I'm not sure which file to put in as solver input file. I tried different inputs: e.g. "m1.xml", "Kinetikmodell.xml". It mostly works fine for the Write, Execute and Extract TestSteps in Test Model, but when optimizing I get the error message shown below. What can I change to fix this error?

image

  •     As mentioned, the piston forces are available as an output. To use this as a data source, I am currently using the mrf-file of the simulation in MotionView. Is this the correct file?

image

Best Answer

  • Diana M._20503
    Diana M._20503
    Altair Employee
    edited September 2023 Answer ✓

    Hello,

    You are the *.xml should be set as Solver input file, and the *.mdl as Resource file.

    I share below a HyperStudy-MotienView tutorial, in case you didn't get the chance to find it.

    https://help.altair.com/hwdesktop/hst/topics/tutorials/hst/tut_hs_1030_t.htm#tut_hs_1030_t

    Yes, the mrf is the correct file to use for the results extraction.

    The error occurs when you click Run Definition in the Optimization approach?

    Are there other messages in the task_exe.txt file you can find under the run folder?

    Which MotionView version are you using?

     

    If the issue remains, it'd be helpful to share your mdl for check.

    Also, if possible for you I'd suggest to upgrade your HyperStudy version. We are currently running with v2022.3.

     

    Best regards,

    Diana

Answers

  • Diana M._20503
    Diana M._20503
    Altair Employee
    edited September 2023 Answer ✓

    Hello,

    You are the *.xml should be set as Solver input file, and the *.mdl as Resource file.

    I share below a HyperStudy-MotienView tutorial, in case you didn't get the chance to find it.

    https://help.altair.com/hwdesktop/hst/topics/tutorials/hst/tut_hs_1030_t.htm#tut_hs_1030_t

    Yes, the mrf is the correct file to use for the results extraction.

    The error occurs when you click Run Definition in the Optimization approach?

    Are there other messages in the task_exe.txt file you can find under the run folder?

    Which MotionView version are you using?

     

    If the issue remains, it'd be helpful to share your mdl for check.

    Also, if possible for you I'd suggest to upgrade your HyperStudy version. We are currently running with v2022.3.

     

    Best regards,

    Diana

  • Maximilian Paulsen
    Maximilian Paulsen Altair Community Member
    edited September 2023

    Hello,

    You are the *.xml should be set as Solver input file, and the *.mdl as Resource file.

    I share below a HyperStudy-MotienView tutorial, in case you didn't get the chance to find it.

    https://help.altair.com/hwdesktop/hst/topics/tutorials/hst/tut_hs_1030_t.htm#tut_hs_1030_t

    Yes, the mrf is the correct file to use for the results extraction.

    The error occurs when you click Run Definition in the Optimization approach?

    Are there other messages in the task_exe.txt file you can find under the run folder?

    Which MotionView version are you using?

     

    If the issue remains, it'd be helpful to share your mdl for check.

    Also, if possible for you I'd suggest to upgrade your HyperStudy version. We are currently running with v2022.3.

     

    Best regards,

    Diana

    Hello Diana,

    thank you for your help.

    I don't know what I did differently, but now everything's working.

     

    Kind regards

    Max