ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2022-11-29 17:19:40 -0500 | received badge | ● Guru (source) |
2022-11-29 17:19:40 -0500 | received badge | ● Great Answer (source) |
2022-07-22 06:09:16 -0500 | received badge | ● Great Answer (source) |
2022-07-22 06:09:16 -0500 | received badge | ● Guru (source) |
2020-12-01 10:53:48 -0500 | received badge | ● Good Answer (source) |
2020-02-20 17:38:15 -0500 | received badge | ● Necromancer (source) |
2019-10-25 04:18:14 -0500 | received badge | ● Nice Answer (source) |
2019-08-28 07:09:44 -0500 | received badge | ● Good Answer (source) |
2018-09-06 15:48:18 -0500 | received badge | ● Nice Answer (source) |
2018-07-25 08:03:20 -0500 | received badge | ● Guru (source) |
2018-07-25 08:03:20 -0500 | received badge | ● Great Answer (source) |
2018-05-02 03:56:48 -0500 | received badge | ● Necromancer (source) |
2018-03-14 13:17:25 -0500 | received badge | ● Great Answer (source) |
2018-03-14 13:17:25 -0500 | received badge | ● Guru (source) |
2018-01-01 02:14:03 -0500 | received badge | ● Good Answer (source) |
2017-08-30 05:23:31 -0500 | received badge | ● Nice Answer (source) |
2017-07-21 09:36:37 -0500 | received badge | ● Good Answer (source) |
2017-04-19 02:18:29 -0500 | received badge | ● Good Answer (source) |
2017-03-02 04:42:01 -0500 | received badge | ● Good Answer (source) |
2016-04-28 15:05:12 -0500 | received badge | ● Good Answer (source) |
2016-04-11 15:21:35 -0500 | received badge | ● Good Answer (source) |
2016-04-11 15:21:01 -0500 | received badge | ● Great Answer (source) |
2016-04-11 15:21:01 -0500 | received badge | ● Guru (source) |
2016-03-30 14:50:25 -0500 | received badge | ● Nice Answer (source) |
2016-03-17 10:12:14 -0500 | received badge | ● Great Answer (source) |
2016-03-17 10:12:14 -0500 | received badge | ● Guru (source) |
2016-01-16 17:22:36 -0500 | received badge | ● Guru (source) |
2016-01-16 17:22:36 -0500 | received badge | ● Great Answer (source) |
2016-01-15 04:21:24 -0500 | received badge | ● Good Answer (source) |
2015-12-10 02:58:24 -0500 | received badge | ● Nice Answer (source) |
2015-10-28 06:43:31 -0500 | received badge | ● Good Answer (source) |
2015-10-24 20:21:18 -0500 | received badge | ● Nice Answer (source) |
2015-10-22 03:45:36 -0500 | received badge | ● Good Answer (source) |
2015-07-27 20:19:50 -0500 | received badge | ● Good Answer (source) |
2015-03-21 08:49:46 -0500 | received badge | ● Nice Answer (source) |
2015-02-21 15:49:17 -0500 | answered a question | generating boxes from octomap::octree error There is no function |
2015-02-21 15:40:21 -0500 | answered a question | how to improve maps from octomap? According to your config in the launch file, you are mapping in the As mentioned in the comment above that line in the launch file, you need to switch to mapping in your actual map frame when using a localization source or SLAM. |
2014-10-20 07:31:53 -0500 | received badge | ● Good Answer (source) |
2014-10-11 07:05:18 -0500 | answered a question | How can I have access to values in the octomap datasets The end points and scans with poses are stored in a format proprietary for OctoMap. The OctoMap tool "graph2tree" can read them, so your best starting point would be to have a look at the file graph2tree, specifically However, there is no color information stored in them. |
2014-10-10 12:08:07 -0500 | commented question | Error with octomap_server: "process has died, exit code -6" Instead, use the octomap_rviz_plugins package. It will directly create a visualization in RViz out of the serialized octomap. |
2014-10-10 12:07:17 -0500 | commented question | Error with octomap_server: "process has died, exit code -6" Most of the memory consumed by octomap_server is actually for the different kinds of visualizations, not for the octomap itself. You can reduce the memory usage by not subscribing to the PointCloud and voxel visualizations (they thus won't be created). |
2014-09-29 01:13:52 -0500 | received badge | ● Guru (source) |
2014-09-29 01:13:52 -0500 | received badge | ● Great Answer (source) |
2014-09-24 04:44:39 -0500 | received badge | ● Good Answer (source) |
2014-08-01 06:20:25 -0500 | received badge | ● Nice Answer (source) |
2014-07-15 04:04:42 -0500 | commented answer | Pre-release build failure to source setup.sh for 3rd party package Actually, it was the devel job that started failing recently: http://jenkins.ros.org/job/devel-hydro-octomap/ |
2014-07-15 04:01:51 -0500 | commented answer | Pre-release build failure to source setup.sh for 3rd party package Do you suggest that cmake-style packages should be removed from the prereleases then? E.g. the "octomap" repo started to fail only recently but was working before. If that's as intended then it should be communicated somewhere, e.g. by refusing "cmake" jobs outright. |
2014-07-04 08:11:47 -0500 | received badge | ● Nice Answer (source) |
2014-07-04 07:26:57 -0500 | answered a question | Decay Octomap in MoveIt? There is an OcTreeStamped class in OctoMap that can be used for this purpose (but you will have to implement it). In fact, the decaying was implemented just like that in the collider package (by now superseded by MoveIt and octomap_server). |
2014-07-04 07:18:25 -0500 | commented question | odometry not correctly working with humanoid_localization Odometry usually comes from wheel encoders or kinematics, that's the assumption in humanoid_localization. A LRF is not an odometry source but with a fixed map will give you absolute references in the world (in addition to odometry that is subject to drift and only used incrementally). |