hexagon logo

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

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
  • Here is a version that functions in later versions of Adams (2021 -> ). Format changed a bit from earlier version.
    If you have a standalone version of python, you can run this with
    python solver_stat_from_debugmsg.py run.msg run.stat
    where "run.msg" is the name of your message file.
    If you don't have a standalone python use
    "C:\Program Files\MSC.Software\Adams\2022_4_904865\common\mdi.bat" python solver_stat_from_debugmsg.py run.msg run.stat
     
    The output file ("run.stat" in this case) might look a bit strange, but can be opened in any text editor. Copy and paste into Excel should show better formatting.
Reply
  • Here is a version that functions in later versions of Adams (2021 -> ). Format changed a bit from earlier version.
    If you have a standalone version of python, you can run this with
    python solver_stat_from_debugmsg.py run.msg run.stat
    where "run.msg" is the name of your message file.
    If you don't have a standalone python use
    "C:\Program Files\MSC.Software\Adams\2022_4_904865\common\mdi.bat" python solver_stat_from_debugmsg.py run.msg run.stat
     
    The output file ("run.stat" in this case) might look a bit strange, but can be opened in any text editor. Copy and paste into Excel should show better formatting.
Children
No Data