12345qiupeng
/
cartographer_ros
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
cartographer_ros/.github/ISSUE_TEMPLATE

26 lines
1.1 KiB
Plaintext
Raw Normal View History

Added an issues template. (#229)
2016-12-19 03:01:55 +08:00
Thank you for filing an issue!
Adds a rosbag_validate binary. (#536) So far it creates statistics over timing information of the sensor data that Cartographer cares about. It also reports if time jumps backwards for a sensor. Also updates the GitHub issue template to ask users to run this binary when reporting issues. I verified that this tool is sufficient to analyze all the timing related issues mentioned in #529.
2017-10-13 23:26:50 +08:00
It would help us tremendously if you run through the following checklist. This
ensures that we have the most information to quickly understand, analyze,
reproduce and eventually resolve your issue.
Added an issues template. (#229)
2016-12-19 03:01:55 +08:00
Adds a rosbag_validate binary. (#536) So far it creates statistics over timing information of the sensor data that Cartographer cares about. It also reports if time jumps backwards for a sensor. Also updates the GitHub issue template to ask users to run this binary when reporting issues. I verified that this tool is sufficient to analyze all the timing related issues mentioned in #529.
2017-10-13 23:26:50 +08:00
Please
Added an issues template. (#229)
2016-12-19 03:01:55 +08:00
Adds a rosbag_validate binary. (#536) So far it creates statistics over timing information of the sensor data that Cartographer cares about. It also reports if time jumps backwards for a sensor. Also updates the GitHub issue template to ask users to run this binary when reporting issues. I verified that this tool is sufficient to analyze all the timing related issues mentioned in #529.
2017-10-13 23:26:50 +08:00
1. run `rosbag_validate` which does some checks on your sensor data. This
tool often finds issues that can explain poor performance and must be fixed
at recording time. Please post the full output of the tool into a
GitHub Gist at https://gist.github.com/, then link it in the issue even if
it does not report anything. You can run the tool like this:
Added an issues template. (#229)
2016-12-19 03:01:55 +08:00
Adds a rosbag_validate binary. (#536) So far it creates statistics over timing information of the sensor data that Cartographer cares about. It also reports if time jumps backwards for a sensor. Also updates the GitHub issue template to ask users to run this binary when reporting issues. I verified that this tool is sufficient to analyze all the timing related issues mentioned in #529.
2017-10-13 23:26:50 +08:00
rosrun cartographer_ros cartographer_rosbag_validate -bag_filename <bag filename>
2. post a link to a Git repository containing a branch of
`cartographer_ros` containing all the configuration, launch, and URDF files
required to reproduce your issue.
3. post a link to a bag file we can use to reproduce your issue. Put it on
Google Drive, Dropbox, any webserver or wherever it is publicly
downloadable.
4. remove this boilerplate text before submitting your issue.
We will likely be unable to help you without all of these points addressed.