Some Problems with FreeSize Optimization
Altair EmployeeHi,
i got some problems with my composite optimization with free size.
I want to create a 'Constraint' with an upper bound of 4mm refering to a response called 'displacement'.
Therefore i created the 'response' called 'displacement' with the type 'static displacement', selected one node of my surface and chose 'total displacement'.
Now my problem: when i want to create the constraint my software outputs: 'Selected subcase (lastfall) is not compatible with the type of response'.
My loadstep is linear static with a pressure as load and a BC (Constraint, all dof checked) as SPC.
You can find my Altair Hyperworks File in the appendix.
Thank you !
Answers
-
Hi,
If you are creating constraints and responses through entity editor you may see such error sometimes.
Kindly, use Analysis>> Optimization>> dconstraints to create constraints.
0 -
Even if I create constraints and responses in this way, i get the same error message and I can't create the constraint to limit my displacement..
0 -
Can you share the model?
0 -
-
Could you find a solution?
0 -
Hi,
This looks like a known issue in HM.I hope you would have created loadstep using Modelbrowser right click then created loadstep.
Please delete current loadstep and recreate loadstep using analysis page.I checked this workaround at my end in your model & Its working.See attached screenshot for creating loadstep using anaysis page.Please update if it works for you.
Regards
Rahul R
0 -
Nice, thank you very much! It works! I deleted the loadstep and created a new one using analysis --> loadsteps --> create
Seems like a bug in the upper drop down menu like someone said before.
Thanks a lot, great support.
0 -
Thanks for the Update.Always its is advisable to use latest version latest patch.
Regards
Rahul R
0 -
Hello all,
I have tried the OS-5090 Thermal Optimization on Aluminum Fins tutorial, and after following all the steps, when I try to create the Objective I get the same error. I have tried deleting the loadstep that already came created in the model file and made one myself using analysis --> loadsteps --> create but the problem persists. I am using the 14 version wiht the latest update and hotfix. Is there a way to work around it or is there anything wrong with the model? Is this solved in the 2017 version?
Thanks a lot.
0 -
Hi MMarzana,
Follow these steps and try again:
1) Create Load step from Analysis>>LoadStep
2) Create response from Analysis>>Optimization>>Responses and refer load step if required
Run the analysis and check again.
0