Rakshit Soni

Seems reasonable approach. If you could test it and find if something more could be considered, suggest some changes, then it will be great. I will try to test the...

Nice, but have you done some testing with it. Is it giving reasonable outputs?@mgonzs13

For the immobile/stactic objects, it should show nearly zero m/s. Thats the way we can verify it atleast for static one. For moving objects we can try on on some...

I tried to test it with just simulation and I have attached he gif for the same. Also providing the topic echo for `detections_speed topic` ![Screenshot from 2024-01-24 16-02-42](https://github.com/mgonzs13/yolov8_ros/assets/85680564/936789bb-e9e1-45ae-a8b5-142 ![Screencastfrom24-01-24161011-ezgif...

Yeah, that what I am trying but some how the gazebo guys don't provide to set the actor's speed. so that we can have some groundtruth

I have my stack build up with the new gazebo (https://gazebosim.org/docs/garden/actors) not with gazebo 11. I am finding something similar in the new one but for actor I couldn't find...

Yes, I am using Gazebo but have the same setup for ignition as well with actors, robot mounted with simulated RGB-D camera and objects that's the same one which I...

I am working with speed stuff. However I found that the callback in speed estimation node sometimes running twice which is making the timestamp difference double and ultimately wrong values....

I have added logger to the speed estimation node. Yes, it will be same when talking about magnitude but if vectors then I believe it should be `crr_x - old_x,...

I am just detecting person class. So it should be only one object. But how that will going to effect time stamp difference to change? @mgonzs13 Could you try on...