You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run WBD at 1khz. As discussed in ami-iit/robots-configuration#10 I increased the rate of all the devices used by wbd.
In the context of xprize I wrote a simple time profiler for wbd e44b223. Running the profiler with wbd at 1khz I obtain the following result
timer name
average time (s)
deadline misses
last deadline miss time (s)
publish
0.000395487473
0
0
compute forces
0.000179018516
0
0
calibration
4.18783e-07
0
0
kinematics
2.4863994e-05
0
0
remove offset
0.000285472475
0
0
contact points
1.5841566e-05
0
0
read sensors
2.9965689e-05
0
0
all
0.000937095005
8351
0.001013504
Accordingly to the table there seems that wbd spends considerably amount of time in publishing and removing offsets (low pass filtering).
Checking with @prashanthr05 we noticed that a a possible bottleneck is due to yarp-to-idyntree copy
I'm trying to run WBD at 1khz. As discussed in ami-iit/robots-configuration#10 I increased the rate of all the devices used by wbd.
In the context of xprize I wrote a simple time profiler for wbd e44b223. Running the profiler with wbd at 1khz I obtain the following result
Accordingly to the table there seems that wbd spends considerably amount of time in publishing and removing offsets (low pass filtering).
Checking with @prashanthr05 we noticed that a a possible bottleneck is due to yarp-to-idyntree copy
whole-body-estimators/devices/wholeBodyDynamics/WholeBodyDynamicsDevice.cpp
Lines 2183 to 2292 in bf7d5ff
To avoid these copies we could replace the yarp vectors in ctrLibRT filters with eigen refs/vectors.
cc @prashanthr05 @HosameldinMohamed @traversaro @isorrentino @S-Dafarra
The text was updated successfully, but these errors were encountered: