Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rqt_bag doesn't publish all messages in the bag file #38

Open
meghakadole opened this issue Apr 1, 2019 · 3 comments
Open

rqt_bag doesn't publish all messages in the bag file #38

meghakadole opened this issue Apr 1, 2019 · 3 comments

Comments

@meghakadole
Copy link

I have to replay a bag file, which contains 15000 messages over a duration of 66seconds. I wrote a subscriber node to this topic. On the subscriber side, I count the number of messages received. I notice that not all messages are received. And the number of messages received is not fixed every time. I need to replay this bag file in real-time and without data loss. How can I achieve this?

I tried replaying the same bag with rosbag play (command line) the performance of command line is much better when compared to rqt_bag, but there is still some data loss. How can I ensure that all messages are received on subscriber end?
Your help is much appreciated. Thanks in advance.

@Dyson-Ido
Copy link

I've same issue , anyone can give some hints, thanks~

@kekeliu-whu
Copy link

I have 2 similar problems when opening a bag file (link) with 500hz imu data:

  1. Only 100hz is shown in rqt_bag;
  2. When i play topic /imu_correct in the rqt_bag, rosbag hz /imu_correct show that the frequency is only 25hz.

@nguyenlam185
Copy link

I am facing the same issue here.
I have a bag file which contains over 80,000 messages, duration is about 40s. The rqt_bag can only publish the topics at ~50Hz whereas the rosbag play command can do that at ~2000Hz.
Are there any parameters that need to be set before starting the rqt_bag in order to speed it up?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants