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

ADAMS/View CPU Time Increase When Using A Sensor To End The Simulation

jsph_inc
Hello,
 
I have an ADAMS/View model which consists of only rigid bodies and a lot of contact. When running the load case with a sensor that kills the simulation the CPU time is 32 hours. When the sensor is removed and rerun to the same end time the CPU time is 8.5 hours. As expected the results from these two runs are line-on-line the same.
 
I wasn't aware that a sensor to end a simulation could have such a large impact on the CPU time. Has anyone seen this as well..is this expected?
Parents
  • 0
    Hi JSlat,
     
    Thanks for the great suggestions. I'll have to dig deeper into the differences in runs as you suggested and delay the activation of the sensor as a short term fix.
     
    That would be great if you could share the python script that can be used to extract the time step statistics from a message file...sounds very helpful.
     
    thanks again,
    joe.
Reply
  • 0
    Hi JSlat,
     
    Thanks for the great suggestions. I'll have to dig deeper into the differences in runs as you suggested and delay the activation of the sensor as a short term fix.
     
    That would be great if you could share the python script that can be used to extract the time step statistics from a message file...sounds very helpful.
     
    thanks again,
    joe.
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement