Jump to content

tinh

Members
  • Content Count

    2975
  • Joined

  • Last visited

  • Days Won

    260

Everything posted by tinh

  1. Sorry, i remember that i wrote it in a post but for a long time...
  2. Use 'split' Or 'string range' Ex: lassign [split {Z Vector - M8_xx8585/xx8584} /] temp P1 lassign [split $temp _] temp P2 lassign [split $temp -] temp P3 puts "$P3\n$P2\n$P1"
  3. Yes, it is. You have to break connection But i don't think it is a good idea. We can make a script to split quad strips, like a function in ansa Are you working with Japanese regulation? I know that jp regulation does not permit quad strips. I wrote a script to find them.
  4. Sorry, could you test it on hm2017? I don't have v2019 so i need to confirm the bug comes from new version or something else
  5. Logic to find them is: 1 row element will have 2 free-edge rows. Just search every element that have 2 free edges.
  6. Put the frame in a text box (hwtk text has scrollbars) And then get hull of textbox, use this hull as a frame to be added to hm panel
  7. In nastran, PID is equal EID by default if you don't assign property to element Don't use *commands in long 'for' loops, use 'puts' to write property cards to a file then import that file, it just takes a few seconds.
  8. With solid element, constraint 1 node is not enough.
  9. Yes, it is unneccesary. We can even select inside without masking/exploding/X-section.
  10. Did you confirm unit of force and material parameters?
  11. It just detects holes but not bolts. You need a script to detect bolts. A simple case of bolt has 'hexagon head' that you can use to detect.
  12. Could you share *.fem file? Can you estimate displacement theorically?
  13. Could you show your geometry? Use 'mask' panel to be able to view inside a part
  14. If you constraint 6 dofs of solid element you will see a warning message says that it affects to only 3 dofs. If nodes are shared among solid elem and shell/beam elem, it will affects to 6 dofs. Hypermesh is designed that in order to be useful in many situations.
  15. Hi Did you tr *createmark surfs 1 "by adjacent" ?
  16. Cannot reflect a ref system because its x,y,z will be changed from right hand rule to left hand rule
  17. Hyperview should have an option to plot them in resolved system. Or you have to try creating derived results before plotting
×
×
  • Create New...