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

How do I stop the message window from echoing out the pcl commands issued from the utility ( in order to speed up the time patran takes to complete all the commands). Seems like it would go faster if not every command was echoed out in the message window

jason.melonas
How do I stop the message window from echoing out the pcl commands issued from the utility ( in order to speed up the time patran takes to complete all the commands). Seems like it would go faster if not every command was echoed out in the message window
Parents
  • 0
    How is your "utility" structured?
    Patran echoes out the necessary commands to the session so that a rerun of the session file would rebuild the model.
    Therefore if your "utility" is a session file that you are "playing" Patran will echo all the PCL commands in it. However if you were to wrap a function around the commands, before the commands insert a "Function myfunc()" line and at the end insert a "END FUNCTION" line followed be calling the function with a line that is "myfunc()", then the only command Patran has to document is myfunc(). The compilation that occurs between the Function to END Function lines is not echoed. There will still be some echo of the IDs of created items but not all the PCL commands.
     
    If you utility is being called as a "session play " of a file then you could also try using the command line !!input yourfile.
    This is a bit like making it a function, the command history stores the !!input yourfile in the session file so that means it does not need to record any of the PCL commands in that file in the session file (echo them to the command window)
     
    With regards to speeding up by not doing any graphics whilst the utility runs; as well as unposting the current viewport you can also use the commands:
    gm_viewport_refresh_off()
    gm_viewport_refresh_on()
    appropriately at the start and end of your utility to minimise graphics update delays.
    Even perhaps test gm_graphics_off() gm_graphics_on() in the same way.
     
    best regards
    Arthur
Reply
  • 0
    How is your "utility" structured?
    Patran echoes out the necessary commands to the session so that a rerun of the session file would rebuild the model.
    Therefore if your "utility" is a session file that you are "playing" Patran will echo all the PCL commands in it. However if you were to wrap a function around the commands, before the commands insert a "Function myfunc()" line and at the end insert a "END FUNCTION" line followed be calling the function with a line that is "myfunc()", then the only command Patran has to document is myfunc(). The compilation that occurs between the Function to END Function lines is not echoed. There will still be some echo of the IDs of created items but not all the PCL commands.
     
    If you utility is being called as a "session play " of a file then you could also try using the command line !!input yourfile.
    This is a bit like making it a function, the command history stores the !!input yourfile in the session file so that means it does not need to record any of the PCL commands in that file in the session file (echo them to the command window)
     
    With regards to speeding up by not doing any graphics whilst the utility runs; as well as unposting the current viewport you can also use the commands:
    gm_viewport_refresh_off()
    gm_viewport_refresh_on()
    appropriately at the start and end of your utility to minimise graphics update delays.
    Even perhaps test gm_graphics_off() gm_graphics_on() in the same way.
     
    best regards
    Arthur
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement