hexagon logo
Register Sign in
  • State Not Answered
  • Replies 12 replies
  • Subscribers 11 subscribers
  • Views 310 views
  • Users 0 members are here
Options
Related

ADAMS Python, more in-depth examples?

christopher.churchill
​I am very excited about opening up the python interface for ADAMS 2017, but as I dig into the language, I'm finding lots of ways to crash view, and not much documentation.
 
The 2017 documentation is good at giving a very short introduction, showing how to create and modify objects, but these are frankly trivial examples and don't actually use much of the python language.
 
For example, if I want to iterate through all the parts in my model, I imagine I would do something like
 
prtNames=list()
for prt in Adams.getCurrentModel().Parts.iteritems():
  prtNames.append(prt.name)
 
I have tried several iterations of this, and most of them either throw an error or crash Aview (this one then crashes). Can anyone point me to some more complex examples, which take advantage of python coding patterns?
 
Crashing suggests the code is fragile, so I need more guidance than the help() command in how to do things as help() reveals things that are broken, like the iteritems function.
Parents
  • 0
    Why "renaming" everything just for the sake of renaming and nuking experienced users to a less than rookie level ? Reminds me of that <insert curse here> ribbon GUI that nobody wanted except your bosses in order to sell something "new" to the people.
    Why not keeping the old names in order to at least keep some of the experience gathered over decades ?
     
    I prefer stuff like this to stay consistent with the command language pendants:
     
    def db_exists(entity):
     elements_exist = 0
     expression = "DB_EXISTS(\"%s\")" % entity
     elements_exist = aview_main.evaluate_exp(expression)
     return elements_exist
     
    and later use as:
      if db_exists(req_name):
        cremod = 'modify'
      else:
        cremod = 'create'
     
      command = "output_control %s request request_name = %s" % (cremod,req_name)
     
    I could easily do this in my own little universe for the two dozen functions I mostly use, but you know what ? In my opinion that's your homework you guys get paid for.
    My wishlist would be to have all ADAMS functions available under the same names and arguments.
     
     
Reply
  • 0
    Why "renaming" everything just for the sake of renaming and nuking experienced users to a less than rookie level ? Reminds me of that <insert curse here> ribbon GUI that nobody wanted except your bosses in order to sell something "new" to the people.
    Why not keeping the old names in order to at least keep some of the experience gathered over decades ?
     
    I prefer stuff like this to stay consistent with the command language pendants:
     
    def db_exists(entity):
     elements_exist = 0
     expression = "DB_EXISTS(\"%s\")" % entity
     elements_exist = aview_main.evaluate_exp(expression)
     return elements_exist
     
    and later use as:
      if db_exists(req_name):
        cremod = 'modify'
      else:
        cremod = 'create'
     
      command = "output_control %s request request_name = %s" % (cremod,req_name)
     
    I could easily do this in my own little universe for the two dozen functions I mostly use, but you know what ? In my opinion that's your homework you guys get paid for.
    My wishlist would be to have all ADAMS functions available under the same names and arguments.
     
     
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement