Topology Optimization - Reanalysis of intermediate iterations

MaUb

Hi,

I optimised a component through OptiStruct using Topology Optimization. You can perform a static structural analysis on the last iteration by inputting the following Solution Control Parameter directly on optistruct: PAR AM, REANAL, <density threashold>. However, I would like to check the performance of an intermediate iteration. Is there a way to do that? 

Regards,

Yago

Rajashri_Saha

Hi MaUb,

Usually, the last iteration of the optimization is considered as the optimum one and you can open the S.h3d file to review the analysis result which is created by default.

What is your use case of analyzing intermediate result?

Thanks

Rajashri

MaUb

Rajashri Saha_20525 said:

Hi MaUb,

Usually, the last iteration of the optimization is considered as the optimum one and you can open the S.h3d file to review the analysis result which is created by default.

What is your use case of analyzing intermediate result?

Thanks

Rajashri

Hi Rajashri,

Thank you for your reply.

As far as I know, the solver operates in different phases to improve discreteness, increasing the penalty factor if the previous one converges. Sometimes, the second phase does not converge into a feasible design, while the first one does.

In my model, iteration 72 presents a discreteness of 0,72 > 0,5, and the constraint violation % is within the acceptable range.

However, the last iteration presents a considerably higher constraint violation and a lower discreteness index (0,71). All indicates it's a less valid result.

That's why I want to compare it with an intermediate iteration.

Regards,

Yago 

Rajashri_Saha

MaUb said:

Hi Rajashri,

Thank you for your reply.

As far as I know, the solver operates in different phases to improve discreteness, increasing the penalty factor if the previous one converges. Sometimes, the second phase does not converge into a feasible design, while the first one does.

In my model, iteration 72 presents a discreteness of 0,72 > 0,5, and the constraint violation % is within the acceptable range.

However, the last iteration presents a considerably higher constraint violation and a lower discreteness index (0,71). All indicates it's a less valid result.

That's why I want to compare it with an intermediate iteration.

Regards,

Yago 

Hi MaUb,

You can request for OUTPUT, SHRES, ALL to have a single .sh or .grid  file written for every iteration and then use the matching iteration one for OSSMOOTH to create the reanalysis file.

Please check this and see if this works for you.

Thanks

Rajashri