Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Q.Nguyen-Dai

  1. In fact, I used "manual correction" sometime on 2D mesh before make 3D TET mesh. Localize the "bad" area and try to simplify the geometry.
  2. Simplify & make correction on your geometry Change (decrease) the size of TET mesh
  3. Check quality of 2D before making 3D Remesh with smaller size Manual correction
  4. Important thing to know: STL is suitable format for surface presentation only. So for solid, you got only external surface presentation, not volume.
  5. Maybe try "userpage.mac" ? Here's from my userpage.mac *createbutton(5,"NASTRAN", 5, 0, 5, GREEN,"Export to Nastran",EvalTcl,"HM2Nastran.tcl") *createbutton(5,"SAMCEF", 5, 5, 5, GREEN,"Export to Samcef ",EvalTcl,"HM2Samcef.tcl") All my scripts found in the directory defined in environment variable "TCL_INCLUDE"
  6. Here's the script found on Altair site: #-------------------------------------------------------------------------------------------- #This script deletes assemblies recursively, optionally comps will be deleted # steenbock@altair.de, 20141008 # V. 01 #-------------------------------------------------------------------------------------------- proc run {} { *clearmarkall 1 *createmarkpanel assems 1 "select assems 2 delete" #delete comps or not set answer [tk_dialog .owd "Selected Assems: [hm_getmark assems 1]" "Delete Components in Assems?" "question" 0 "No" "Yes" "Cancel"] switch $answer { 0 {set delComps 0} 1 {set delComps 1} 2 {tk_messageBox -message "Misson abort!" -type ok -icon warning; return;} } # loop whole assem tree foreach ass [hm_getmark assems 1] { deleteSubAssems $ass $delComps } *clearmarkall 1 } proc deleteSubAssems {assem delComps} { set output 1 if {[hm_entityinfo exist assem $assem] == 1} { set sub_ass [hm_getentityarray assemblies $assem assemblies] # part where comps will be deleted if {$delComps != 0} { set sub_comps [hm_getentityarray assemblies $assem components] if {[llength $sub_comps] > 0} { eval *createmark comps 1 $sub_comps if {$output ==1} {puts "\t\tdelete comps: $sub_comps"} *deletemark comps 1 } } # delete assem *createmark assems 1 $assem if {$output==1} {puts "\tdelete assem id=$assem ([hm_getentityvalue assemblies $assem name 1])"} *deletemark assems 1 if {[llength $sub_ass] > 0} { foreach a $sub_ass { deleteSubAssems $a $delComps } } } } #----------------------------------------------- run
  7. Make a test with Nastran profile? A very small model and export to BDF.
  8. I think that do automatically in Hypermesh. When you create new set, the ID will be "maxID + 1"
  9. Agreed with @GAJENDRA KUMAR NHAICHANIYA, different temperature can make stresses, but not always! If you have only ONE material and you have no Mechanical constraints, you can not have stresses due to different temperature. You have only deformation due to different temperature, but never stresses!
  10. Depending to your solver, your quality criteron would be different. But in general of 2D mesh, you can check: Jacobian Aspect For 3D mesh, you can add: skew, tet collapse,... Of course, don't forget to check: connectivity & duplicates
  11. When you have set name, you can get set ID by following command: set set_id [hm_getvalue sets name="E_1" dataname=id] When you have set ID, you can get set name by following command: set set_name [hm_getvalue sets id=2 dataname=name]
  12. Theoretically, when you make a Thermal Analysis, you need ONLY Thermal Boundary conditions. In this case, all Mechanical Boundary Conditions are not needed.
  13. Firstly, do you use which FE Solver of Hyperworks? Secondary, is there a "card" to enter these data into your solver?
  14. You can begin your work by looking for keyword "How to read CSV file with TCL" in Google.com
  15. To combine two or several surfaces, just turn off their internal boundaries (F11)
  16. My example code gives you nothing? This is help forum, so please try & try & try & give us error message or somethoing you have tried. If you do nothing you can wait for "One-click" solution, it's your choice.
  17. If you does not show your script code, nobody could help.
  18. Two different things to know: The message "One or more features of the license ...." is just a warning about expiration of your licenses in some days. But for this moment you got valid license. When you run in batch mode, instead of output to "stdout" (command console in Hypermesh session) you can write to a file. Try this method? So the warning message of license can not be the cause of error of your script.
  • Create New...