Jump to content
Sign in to follow this  
nipundahra

Error in topology optimization with modal analysis as input

Recommended Posts

Hi,

Can i get to now in which version do you plan to patch the following error :

 

The SUBCASE ID in ATT1 field of DRESP1 does not refer to a modal FRF subcase.

 

which occurs while performing modal analysis  with the analysis type as "normal modes" and a optimization resaponse as "frequency" . I am facing  the error in both HM 17 and 17.1!

Share this post


Link to post
Share on other sites

Hi Prakash,

 

I did a topology optimization and now i wanted to validate my design  using OSSmooth. I was using the FEA reanalysis option in OSSmooth panel.But when i select the "Keep smooth narrow layer around"option and choose a threshold value of less then ~0.1 (desired threshold is around 0.04),I am facing a segmentation error while running OSSmooth.I am not getting this error when i choose a value greater or equal to around 0.15 (But those values are undesirable as the optimisation results are discontinuous in space for higher threshold values which are expected as i have to use global mises stress as a optimisation constraint). Also i don't get this error when i switch off the "Keep smooth narrow layer around" option.

 

I am using Linux and tried deleting some files created in the working directory to avoid this error but with no luck. I am using HM V2017.1.If required,you can find the corresponding .fem and .sh files below. I request you to please guide me through to solve my problem.

Thanks and Regards,

Nipun

 

 

Share this post


Link to post
Share on other sites
Guest

Hi,

 

There is no workaround for segmentation other than deleting setting files and temp folders. If you access to any other machine please try on that and check if that helps.

 

Share this post


Link to post
Share on other sites

Hi,

 

I tried it on other machine but was getting the same error.Since I don't have any access to HM 14 or other older versions can you please try running it on HM 13/14?.

Attached below are the required .fem and .sh files and two pictures showing the required setting in ossmooth.Also attached is the terminal output generated while trying to run ossmooth

SegmentationError_Nipun.zip

settings_ossmooth

settings_ossmooth_parameters

terminal_output

Share this post


Link to post
Share on other sites

Hi. Thanks for trying at your end.

 

As seen in the terminal output ,it shows  some "self intersection" which i think is because the software is unable to generate correct mesh for reanalysis.For me a crash file is generated after the segmentation eror in which a 2D surface mesh is generated.When i open the crash file separately and try to convert that 2d mesh to 3D,i get the same segmentation error at the % progress as observed in the status bar.

Can you suggest some solution based on this observation?

 

regards,

Nipun

Share this post


Link to post
Share on other sites
Guest

Hi,

 

Can you change the parameters in OSSmooth panel?

 

Remove split quads and check keep Smooth narrow layer around. 

Share this post


Link to post
Share on other sites

Hi,

I checked with split quads option  which didn't give me an error.I get the error only if i check and use the Smooth narrow layer option.I attached 2 pictures for which i wanted you to check.Can you please try for those settings?

 

I meant please try using the threshold of 0.04 and check keep smooth layer option on.This is the required setting and giving the error!

 

I don't get any error when -

1) i switch off the smooth layer option and use any threshold value

2) i switch on the smooth layer option and use the threshold value above 0.15

 

Share this post


Link to post
Share on other sites
Guest
34 minutes ago, nipundahra said:

 

I meant please try using the threshold of 0.04 and check keep smooth layer option on.This is the required setting and giving the error!

No segmentation error or crash except a meshing error but over all works fine at my end on HW 2017.1

Capture.PNG

Share this post


Link to post
Share on other sites
Guest

Well the only better way is to get the geometry and mesh it for your case suits. There are few areas where mesh is not seen which is not good for further analysis. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
You are posting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...