• Announcements

    • Rahul Ponginan

      Please click here for a short but important announcement   03/26/17

      Dear Users Our Commercial and Academic users around the world can use these same forums here as before i.e. the Altair Support Forum , Commercial users from India with solver queries can go to the Solver Forum for India Commercial Users , Academic Users from India and AOC India Participants are requested to go to the Forum for India Academic Users and AOC India Participants , We will be tending to all queries in all the forums promptly as before, thank you for your understanding. 


  • Content count

  • Joined

  • Last visited

  • Days Won


Merula last won the day on May 13

Merula had the most liked content!


About Merula

  • Rank
    Advanced User
  • Birthday 07/30/89

Profile Information

  • Gender
  • Interests
    Topology, Thermal Simulation, Optimization
  • Are you University user?

Recent Profile Visitors

1597 profile views
  1. That would be awesome!
  2. Hi @Prakash Pagadala, so just to get this straight: The Volfrac Value is related to the element initial density value. If it is 0.6 (with compliance as the objective), Iteration 0 should have the same as an analysis with 0.6 * E0 ? Best regards, Merula
  3. Hello guys, what exactly is the first (0) Iterations stress contour plot? It differs from the stress output you get when doing an analysis. I am aware, that the topology optimization solver sets the density value euqally distributed over all elements to some start value which is 0.3 I think. But then I would expect to see 3 times the stress in an linear optimization (Iteration0) compared to a linear analysis? Thanks in advance. Best regards, Merula
  4. Hey, lately someone pointed out the possibility to do automated mesh convergence studies within Ansys workbench. Example: Is something similar available for Hypermesh / Optistruct ?? As this is an often executed task I hope to find a way which does not include setting up the mesh entirely new with forces, boundary conditions and such. Thanks so much in advance for your help. Best regards, Merula.
  5. Hey, as help says: *rbe3 mark_id independent_dofs dof_size independent_weights weight_size dependent_node dof weight the last parameter is the weight, which is zero in your case. If you bother, here is my way of creating rbe3: eval *createmark nodes 1 {"by box"} [expr $x-$delta] [expr $y-$delta] [expr $z-$delta] [expr $x+$delta] [expr $y+$delta] [expr $z+$delta] 0 inside 0 0 0 hm_createmark nodes 2 [expr $nodeId] *markdifference nodes 1 nodes 2 set numberOfNodes [hm_marklength node 1] #Arrays set arrI() [lrepeat $numberOfNodes 123] set arrD() [lrepeat $numberOfNodes 1.0] eval *createarray $numberOfNodes $arrI() ; eval *createdoublearray $numberOfNodes $arrD(); eval *rbe3 1 1 $numberOfNodes 1 $numberOfNodes $nodeId 123456 1; Best regards, Merula
  6. Thanks! Much appreciated!
  7. I dont unterstand this, what option do you have in mind? To better illustrate, what the goal in this case is: I have a surface and I know the location of some forces on that surface. I want to fully automate the meshing process with .tcl scripts. Therefore, I search for a way to place mesh Nodes onto the force nodes, because then I can do a simple box select around the force node and have my force mapped to the mesh. Thanks again as always
  8. I cant find the option with the anchor nodes (when the selector is set to surfaces). How can I apply fixed Nodes to a surface for a 2D automesh ? Thanks in advance Prakash. Best regards, Merula
  9. any Updates on this? I would really like to see this functionality in hypermesh. Best regards, Merula
  10. Top! Thanks!
  11. Hi Rob, the purpose of Batch is that it runs without opening the GUI of Hyperworks allowing it to run faster. If you want to "see" your results, you have to run it without the -b. If you write your results to a text file thats something different, but I guess you want to see it graphically ?! Best regards, Merula
  12. For getting the node you can use: hm_getclosestnode x y z For getting the id of the surface you can use hm_getentityinfo nodes [hm_getclosestnode x y z] surfaceid 0 -byid For getting the nodes of the surface you can use: hm_createmark nodes 1 "by surface" [hm_getentityinfo nodes [hm_getclosestnode x y z] surfaceid 0 -byid] Hope this helps Best regards, Merula
  13. push The purpose is to delete every non realized connector because they are the reason why the simulation aborts with errors.
  14. push
  15. found it out myself: you have to plot the tensor like the contour, then tensor.value is available. Not so good documentation though...