Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

symmetric model generation

Status
Not open for further replies.

chairats

Geotechnical
Jul 30, 2002
8
My problem is about the modeling in 3-D when I revolve my 2-D plane about the symmetry axis. I use the *symmetric model generation command. The program create duplicate node and element by offset the numbering. The problem is along the symmetry axis. Program recognize nodes at the axis to be the same and doesn't offset the node in the node information, however it does offset the node number in the element connectivity data. Therefore node number using in the element connectivity data doesn't exist in node definition and I would like to ask you for any algolithm to change this number to the node number along the symmetry axis.
 
Replies continue below

Recommended for you

It sounds like you have a bad program with a bug in it. Some programs have a merge facility in them so that near/conincident nodes are merged out and the element connectivity is modified accordingly. This probably wouldn't work in your case as your nodes have been merged but the element connectivity hasn't been altered. This is probably because you have wedge shaped elements in the centre but the program thinks you have brick elements and leaves the node numbers intact although they don't exist in the node definitions. As the program is unable to create wedges then alternatives might be to leave a hole in the centre of the model that you can later fill with wedge elements yourself, or create the shape first then mesh it, rather than trying to sweep a mesh into a 3D shape. The program should be able to mesh 3D solids with brick elements throughout.
 
If you were using the ABAQUS pre processor, this would not be a problem, but, if you intend to use symmetric results transfer, then this needs to work.

This may be a bug, if so, I am sure your local support office would like to get a hold of your input deck so that it could be tested and passed to the developers for correction. In general, anything that worked in 6.2 had better work in 6.3, or it needs to be corrected. You'll find ABAQUS very serious about getting these type of bugs corrected.

Best regards and good luck!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor