Jump to content

Leaderboard


Popular Content

Showing most liked content on 11/26/15 in all areas

  1. 1 like
    Hi, I do not clearly understand your mind... If you have some elems in mark 1, and you want to move it to mark 2, you can do: eval *createmark elems 2 [hm_getmark elems 1] mark 1 still stores those elems. so the two marks are equal But I think you are in this scene: - you have some elems in mark 1, and some others in mark 2 - you want to do some tasks need mark 1 but want to remember elems in mark 1, too There are several ways without affect to mark 2 1) you can store elems in mark 1 into a variable and restore them later, forexample set ElemList1 [hm_getmark elems 1] # do something using mark 1 ... #restore mark 1: eval *createmark elems 1 $ElemList1 2) store elems in mark 1 into usermark, then restore later: *marktousermark elems 1 # do something using mark 1 ... #restore mark 1: *createmark elems 1 retrieve 3) store elems in mark 1 into a table, then restore later: hm_marktotable elems 1 elem_table_name # do something using mark 1 ... #restore mark 1: hm_tabletomark elem_table_name 1 hm_tableclear elem_table_name ; #free memory If you are manipulating on many mark, moving to table is good choice. It's fast, and you can do intersection, union, cut, remove same with mark
  2. 1 like
    Hi Prakash, Thanks for your suggestion. I checked the material model. The problem was with the definition of stress-strain curve. I had previously defined Stress vs. total strain (elastic + plastic) but now I have changed it to Stress vs. Plastic strain and the model is now working fine. Thanks again for your help... You are awesome man. Keep rocking .
×
×
  • Create New...