Node and element number coincidence during import
I have a problem with hypermesh during import. Whenever I try to import a model which is not built in hypermesh, I get multiple node and element coincidence warning. The model got messed up after the update. I probably caused by node and element numbering systems in hypermesh, since other solver preprocessor (Eg. Abaqus and patran) has seperated numbering systems for every part, hypermesh has one numbering system for hole model. When I openned the .inp file that I tried to import, I realized that there are multiple elements with same element ID for different parts. You can also check attached screenshow for better understanding of how it looks like after the import. I know what causes this warnings, but don't know the solution. I would be greatful if you can share the solution or some tips.
A section of warning Message:
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Warning: nodes id 4038 was found more than once in the import file
Resolution: Original id's maintained. Renumbering the database recommended.
Warning: elements id 1 was found more than once in the import file
Resolution: Original id's maintained. Renumbering the database recommended.
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Regards,
Mehmet
Answers
-
Yes, it's typically the issue with 'including' meshing of Abaqus.
Workaround: import each including mesh and rebuild assemble with Hypermesh.
0 -
Thank you for the response.
By 'including' did you mean abaqus include option which is used to call different models with include keyward within .inp file. If I understood correctly, I are suggesting that to impart all model files seperately. However, my inp file does not have any include keyword. All mesh data is in one file. However numbering starts from 1 for every part within this file.
0 -
- Edit your .INP file to extract one .INP file for each part.
- Import each .INP into Hypermesh => You got one .HM model for each part
- Build assembly in Hypermesh: open 1st model and then 'Import model' for others.
0 -
Q.Nguyen-Dai, thank you for the suggestion.
You suggestion sure is a solution for small models, however it would take too much time for bigger models (while saying bigger I mean models with many comonents)
Is there any other way? Something like make abaqus renumber all elements and nodes with one series before export?
0 -
'since other solver preprocessor (Eg. Abaqus and patran) has seperated numbering systems for every part,'
When you create model in above preprocessor, can you renumber id before exporting?
I want to see format of inp file created by abaqus, patran.
0 -
Altair Forum User said:
Q.Nguyen-Dai, thank you for the suggestion.
You suggestion sure is a solution for small models, however it would take too much time for bigger models (while saying bigger I mean models with many comonents)
Is there any other way? Something like make abaqus renumber all elements and nodes with one series before export?
If you can not modify manually, write a script to do the job /emoticons/default_tongue.png' srcset='/emoticons/tongue@2x.png 2x' title=':P' width='20' />
0 -
Altair Forum User said:
'since other solver preprocessor (Eg. Abaqus and patran) has seperated numbering systems for every part,'
When you create model in above preprocessor, can you renumber id before exporting?
I want to see format of inp file created by abaqus, patran.
Here is a sample .inp from abaqus. Two seperate parts have their own numbering system starting from 1. No error while importing it back to Abaqus.
0 -
Abaqus has a special mechanism to assembly parts. That why it works with Abaqus, but not with others.
0 -
It is a shame that hypermesh can't handle simply such a easy thing. It can be done by a script as you mentioned. I hope new version provide this option.
I was hoping that maybe abaqus can renumber as every node and element has a unique ID.
0 -
Try my tool:
Executable file for Windows. Within command line terminal:
inp_tool.exe Job-1.inp
You will got one INP file for each part. Then import them into Hypermesh.
0