HyperStudy x HyperForm result
Hello everyone.
I'm using HyperStudy with HyperForm to run the optimization for my stamping model.
i found a problem that the result in HyperStudy report is different from the result that can be seen in HyperView.
Please refer to below images:
The automated report shows that the constraint is 24.69 (thinning percentage), which is lower than the value was setup in the beginning = 25% >> OK
<?xml version="1.0" encoding="UTF-8"?>
However, when looking at the result in HyperView, the thinning percentage is 28 % >> which violated the constraint.
<?xml version="1.0" encoding="UTF-8"?>
i have selected the correct iteration result (no.6).
How can we explain this?
or is it a bug?
Hope to receive help from you.
Thanks in advance!
Answers
-
what folder are you looking for the results in HSt package?
I ask you this because Iter6 in HSt not necessarily is Run_0006 folder, ok?
Optimization runs have plenty of intermediate runs that are not the iteration runs. They're called evaluation runs. Maybe you're looking at the evalualtion #6 folder? Can't tell for sure.
0 -
Altair Forum User said:
what folder are you looking for the results in HSt package?
I ask you this because Iter6 in HSt not necessarily is Run_0006 folder, ok?
Optimization runs have plenty of intermediate runs that are not the iteration runs. They're called evaluation runs. Maybe you're looking at the evalualtion #6 folder? Can't tell for sure.
hi Koga,
Thanks for your response.
Actually, this result is automatically loaded into HyperView by script.I also did the double check. The H3D file is correct with the Run_0006.
'...\approaches\opt_1\run__00006' >> this is the folder path.
i have also run some other examples, this issue always happens.0 -
Junta,
Run_0006 is not necessarily Iteration 6 in the optimizaiton, ok?
'Runs' are internal evaluations performed by HSt in order to perform the optimization process, and they might be related to sensitivities or even fitting response surfaces.
So run_0006 is just evaluation 0006 from the whole process.
I've never run a HF optimization, but I believe it also generates a .hstx file that you could launch from HyperStudy and review in more details what are the final values and discover what is the Iter 6 equivalent run number. (ex...it 6 might be run_0020)
0 -
Altair Forum User said:
Junta,
Run_0006 is not necessarily Iteration 6 in the optimizaiton, ok?
'Runs' are internal evaluations performed by HSt in order to perform the optimization process, and they might be related to sensitivities or even fitting response surfaces.
So run_0006 is just evaluation 0006 from the whole process.
I've never run a HF optimization, but I believe it also generates a .hstx file that you could launch from HyperStudy and review in more details what are the final values and discover what is the Iter 6 equivalent run number. (ex...it 6 might be run_0020)
Hi Koga,
Thanks for your support.
I will check again!0