Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by Gnokrojam

  1. When importing a FEA input deck into Hypermesh the menu offers some options that are not explained.  I have searched the Altair Documentation and the internet and cannot find any guidance.


    Perhaps some of you have figured it out.


    I could mess around a long time using trial and error to figure it out myself.


    What does "ID Rules" do?  What are the rules?

    What does "FE Overwrite" do?  It doesn't sound good. I imagine it depends on the situation.


    Thank you very much, good people.


    Phil Brown



  2. I have been using Inspire 2019.2. I checked and found that 2019.3.1 is available to me. I installed it and now I can select the features as your video shows.

    I can also now select features in my own geometry.

    I still have problems, but I think they are related to the bad geometry as you mention. In one instance I found a bushing that was at an angle to the hole it was in. It was off so much that there was an interference between the parts.

    Anyway, you have got me going again. Thank you again for your invaluable assistance.

    Best Regards,


  3. Thank you for all the information.

    I exported the geometry you provided as a STEP file and read it into Inspire.

    I cannot select the surfaces in the holes. Or any surfaces for that matter.

    It's just point and click left mouse button, right?

    I've been doing other things with Inspire. If I use Autofind I can click on discovered joints and change their settings and activate them. 

    I'm stumped. I don't know what setting would keep me from selecting surfaces.


    I appreciate your assistance.

    Phil Brown

  4. Some time ago I worked with a different FEA program and that company provided as part of the documentation a list of known errors. As bugs were fixed they were removed. As bugs were found they were added.

    It was a very useful tool to us users. We could quickly tell if a problem was something we were doing or a shortcoming of the software. Knowledge is power!

    Is a list of known bugs or known errors available for Optistruct?

    Thank you,


  5. I found it!

    In the MotionView User's Guide, in the Tutorials, in the Contact Simulation tutorials.

          MV-1010: 3D Mesh to Mesh Contact Simulation

    It outlines the mesh requirements and has a link to best practices for contact modeling.

    The link takes you to:

           MotionSolve > User's Guide > Analysis Tips: Best Practices for Running 3D Contact Models in MotionSolve.


    Have fun with it colleagues!




  6. I had two Components appear in my model and I do not know why or how they were created.


    The component name is in the form: ^HM_autoskin_2


    The components are made of Quad elements that are the surfaces of 3-D Hex element meshes. They are the same colors of the Hex mesh components.


    When I export to a solver deck, the "autoskin" components do not appear in any form.


    I don't know if I "fat-fingered" a button without realizing it or what. I'm not doing anything I haven't done a lot before this.


    I am using HM v14.0 on a Windows 7 HP 8570w laptop.


    Thank you.



  7. I found the Tools>Features panel of which you spoke. I didn't know about it, and it can be helpful.

    It doesn't help with vertex angles.

    I appreciate your help, and feeling like I'm really being dense about this, but I'm not getting it.

    I have attached a screen shot of a model I am working on now. I have shown the features. Maybe you can point out or describe vertex angle from it.

    Thank you.


  8. Do I understand correctly that it is the angle between the edges of two different elements?


    If one had a mesh of all equilateral triangles it would be a very good mesh. All of the angles will be 60 degrees. The panel came up with a default vertex angle of 30 degrees. That would require that all of those equilateral triangles be divided again. That doesn't make sense to me. Either I don't understand the vertex angle, or it should be set to something greater than 60 degrees.

  9. I am creating a triangle shell mesh for tet-meshing. When using Automesh to mesh elements with QI optimize, one can specify a feature angle and a vertex angle. The feature angle is the angle between element normals.

    What about the vertex angle? The manual says: " Whenever an element vertex exceeds this angle while adhering to features, the element will be split into two elements with correspondingly smaller vertices." The default angle in the field is 30 degrees. Triangles will always have an angle that is greater than 30 degrees. Someone else in the manual it is described as being similar to the feature angle. I can't find an illustration or more detailed explanation of vertex angle. Can someone clarify this for me, please?

    Thank you.


  10. Good questions, Rahul.


    I took a simple model and started doing the same things to it that I've done to the real model.


    The model was written out of HM into an Abaqus input file. Since I do not know how to set everything up in HyperMesh for an Abaqus run, I sometimes make changes with a text editor. Then, I later sometimes read the edited input file back into HyperMesh. This morning I realized the obvious. Each time I read the file back into HM there are prefixes being added.


    I attached a .bmp. In the left column is the file the first time I wrote it out from HM. In the right column is the file the second time I wrote it out. 


    Knowing what is happening, I went back to the import input file menu, but I still don't see what I have done to cause this prefix to be added.


    I hope this clarifies my question. Again, if you can point me to where in the documentation this is explained, I will appreciate it.


    Thank you.




  11. I'm using HyperMesh 12.0 and Abaqus 6.12-4.


     I've been away from FEA for a couple of years. My entities are now getting names like:


      NSET = S2;S2;S2;S2;S2;PreTensNodes






    Then I run Abaqus and get errors that a certain surface doesn't exist. It doesn't exist because its name got a new prefix in the model data, but not in the history data.


    Somewhere in the documentation I saw how names are organized between the semi-colon and colon. I can't find it now. I've looked and looked.

    Can someone please point me to where in the manual this naming convention is explained.

    Is there a way of turning it off so that I can use names like: plate, gusset, door, Fred, Wilma, Moe, Larry, CurlyJoe?


    Thank you.



  • Create New...