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

0 jsph_inc over 2 years ago

Hi All,

The sensor is used to stop the simulation.

The sensor uses a state variable that sums the contact force of two contact pairs in the global X-direction.

When the value of this state variable goes to zero the simulation ends.

The value of this state variable is fairly constant until the end of the simulation when it goes to zero.

Perhaps using contact to define the sensor significantly slows the simulation? I should point the sensor to a different channel and rerun...

joe.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 jsph_inc over 2 years ago

Hi All,

The sensor is used to stop the simulation.

The sensor uses a state variable that sums the contact force of two contact pairs in the global X-direction.

When the value of this state variable goes to zero the simulation ends.

The value of this state variable is fairly constant until the end of the simulation when it goes to zero.

Perhaps using contact to define the sensor significantly slows the simulation? I should point the sensor to a different channel and rerun...

joe.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data