2023-03-10 02:10:39 -0500 | received badge | ● Great Question
(source)
|
2022-02-02 23:28:08 -0500 | received badge | ● Famous Question
(source)
|
2021-03-30 17:16:54 -0500 | received badge | ● Popular Question
(source)
|
2021-03-30 17:16:54 -0500 | received badge | ● Notable Question
(source)
|
2021-03-30 17:16:54 -0500 | received badge | ● Famous Question
(source)
|
2020-01-18 16:04:06 -0500 | received badge | ● Taxonomist
|
2019-07-11 03:35:24 -0500 | commented question | amcl not publishing map -> odom under different namespace What does your TF tree look like?
|
2019-07-11 03:33:34 -0500 | commented question | urdf ImportError: No module named 're' Is re installed for python 2?
|
2019-07-11 03:08:34 -0500 | answered a question | Producing an X any Y coordinate from a Lidar sensor Once you have received a LaserScan message you can access it's individual measurement. Because you know the resolution o |
2019-07-11 03:08:34 -0500 | received badge | ● Rapid Responder
(source)
|
2019-03-08 08:20:00 -0500 | received badge | ● Popular Question
(source)
|
2019-03-08 04:21:14 -0500 | commented answer | Strange Grid over SW Registered Depth Image No difference, RViz visualizes images in the same way as image_view
|
2019-03-08 03:33:28 -0500 | asked a question | Strange Grid over SW Registered Depth Image Strange Grid over SW Registered Depth Image
Hello, I recently acquired a D415 camera and tried to use it with the realse |
2018-07-02 03:58:27 -0500 | received badge | ● Notable Question
(source)
|
2018-06-27 09:44:56 -0500 | asked a question | Laser Scanner Gazebo Plugin Crashes on Contact Laser Scanner Gazebo Plugin Crashes on Contact
Hello,
I have the attached urdf and xacro files for a small differential |
2016-06-09 03:32:37 -0500 | received badge | ● Self-Learner
(source)
|
2016-06-09 03:32:37 -0500 | received badge | ● Teacher
(source)
|
2016-03-31 01:44:29 -0500 | received badge | ● Good Question
(source)
|
2016-01-05 08:29:08 -0500 | received badge | ● Nice Question
(source)
|
2015-10-14 04:28:40 -0500 | received badge | ● Popular Question
(source)
|
2015-05-05 09:41:33 -0500 | asked a question | ROS Indigo neo_relayboard Greetings, I am trying to compile the neo_relayboard package from neobotix but it seems to be broken (a missing method). Does anyone have a working version or knows a workaround ?
I am running ROS Indigo in Ubuntu 14. Thank you,
Andreas |
2015-04-15 01:50:08 -0500 | received badge | ● Famous Question
(source)
|
2015-03-26 06:53:32 -0500 | received badge | ● Famous Question
(source)
|
2015-02-03 03:31:52 -0500 | received badge | ● Famous Question
(source)
|
2015-01-12 12:45:47 -0500 | received badge | ● Notable Question
(source)
|
2014-12-13 17:53:30 -0500 | received badge | ● Famous Question
(source)
|
2014-12-08 02:59:04 -0500 | received badge | ● Popular Question
(source)
|
2014-12-05 04:22:02 -0500 | asked a question | Global Costmap Implementation Greetings, I would like to ask if there is a way to create a global costmap for the navigation package from a map that doesnt comply to the 3 color standard ROS expects. This means having a map with extra information, such as elevation and terrain type. Ideally I would like to create the global costmap only once in order to calculate a single global path. |
2014-11-04 23:01:11 -0500 | received badge | ● Notable Question
(source)
|
2014-11-04 23:01:11 -0500 | received badge | ● Popular Question
(source)
|
2014-09-16 17:34:47 -0500 | received badge | ● Notable Question
(source)
|
2014-09-16 17:34:47 -0500 | received badge | ● Popular Question
(source)
|
2014-09-04 06:48:16 -0500 | asked a question | CCNY RGB-D tools Installation Problem Hi, I downloaded the tools from github and followed the instructions to install them. However the installation fails with the message Linking CXX executable bin/global_cloud_align
lib/librgbdtools.so: undefined reference to `boost::filesystem::detail::status(boost::filesystem::path const&, boost::system::error_code*)'
lib/librgbdtools.so: undefined reference to `boost::filesystem::detail::create_directories(boost::filesystem::path const&, boost::system::error_code*)'
lib/librgbdtools.so: undefined reference to `boost::filesystem::detail::create_directory(boost::filesystem::path const&, boost::system::error_code*)'
Other packages can link to boost normally, so in CMakeLists.txt I added the compile flags for filesystem and system but no luck. I have not messed with the package files in any other way. The rest of the stack's packages also seem to isntall fine. EDIT:
Forgot to mention, I am using ROS Hydro, Boost 1.52 on Ubuntu 12.04
Any suggestions ? |
2014-06-24 08:39:46 -0500 | asked a question | Cannot create Simple Action Client Greetings, I am trying to write an action client so I can send goals to move_base. I know that I can send them through messages also, but I would prefer the action client so I can monitor them. So my setup is this. Running Hydro I execute my localisation launch file with move_base included. I want my action client to send goals to move_base, however even when i follow exactly the steps described in http://wiki.ros.org/navigation/Tutori... , although it compiles fine,when I run the node it hangs during this step : MoveBaseClient ac("move_base", true); It just stays there forever. Could it be a threading issue or something ?
For reference here is the file that compiles fine #include <ros/ros.h>
#include <move_base_msgs/MoveBaseAction.h>
#include <actionlib/client/simple_action_client.h>
typedef actionlib::SimpleActionClient<move_base_msgs::MoveBaseAction> MoveBaseClient;
int main(int argc, char** argv){
ros::init(argc, argv, "simple_navigation_goals");
ROS_INFO("STEP 1");
//tell the action client that we want to spin a thread by default
MoveBaseClient ac("move_base", true);
ROS_INFO("STEP 2");
//wait for the action server to come up
while(!ac.waitForServer(ros::Duration(5.0))){
ROS_INFO("Waiting for the move_base action server to come up");
}
ROS_INFO("STEP 3");
move_base_msgs::MoveBaseGoal goal;
//we'll send a goal to the robot to move 1 meter forward
goal.target_pose.header.frame_id = "base_link";
goal.target_pose.header.stamp = ros::Time::now();
goal.target_pose.pose.position.x = 1.0;
goal.target_pose.pose.orientation.w = 1.0;
ROS_INFO("Sending goal");
ac.sendGoal(goal);
ac.waitForResult();
if(ac.getState() == actionlib::SimpleClientGoalState::SUCCEEDED)
ROS_INFO("Hooray, the base moved 1 meter forward");
else
ROS_INFO("The base failed to move forward 1 meter for some reason");
return 0;
}
Thank you in advance |
2014-04-28 21:20:04 -0500 | received badge | ● Notable Question
(source)
|
2014-04-20 13:44:02 -0500 | marked best answer | Openni_tracker crashes with a segmentation fault (core dumped). Any idea on what is causing it ? It is running on Ubuntu 12.04 LTS, ROS Fuerte and an intel graphics card. gbd run output : (gdb) run
Starting program: /opt/ros/fuerte/stacks/openni_tracker/bin/openni_tracker
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff1038700 (LWP 8120)]
[New Thread 0x7ffff0837700 (LWP 8121)]
[New Thread 0x7fffebfff700 (LWP 8122)]
[New Thread 0x7fffeb7fe700 (LWP 8127)]
[New Thread 0x7fffdf623700 (LWP 8133)]
Program received signal SIGSEGV, Segmentation fault.
0x00007fffe8a56e56 in Segmentation::detectionByPoint(bool, std::vector<Vector2D<int>, std::allocator<Vector2D<int> > > const*) ()
from /usr/lib/libXnVFeatures_1_5_2.so
BT output :
#0 0x00007fffe8a56e56 in Segmentation::detectionByPoint(bool, std::vector<Vector2D<int>, std::allocator<Vector2D<int> > > const*) ()
from /usr/lib/libXnVFeatures_1_5_2.so
#1 0x00007fffe8a61b61 in Segmentation::update(Array2D<unsigned short> const&, MotionDetectorByEdges const&, Floor const&, Farfield&, std::vector<Vector2D<int>, std::allocator<Vector2D<int> > > const*) ()
from /usr/lib/libXnVFeatures_1_5_2.so
#2 0x00007fffe8a4769b in SceneAnalyzer::Update(std::vector<Vector2D<int>, std::allocator<Vector2D<int> > > const*, unsigned int) ()
from /usr/lib/libXnVFeatures_1_5_2.so
#3 0x00007fffe8a0f95e in XnVSceneAnalyzer::InitFromSM() ()
from /usr/lib/libXnVFeatures_1_5_2.so
#4 0x00007fffe8a107cb in XnVSceneAnalyzer::UpdateData() ()
from /usr/lib/libXnVFeatures_1_5_2.so
#5 0x00007ffff6d315b7 in ?? () from /usr/lib/libOpenNI.so.0
#6 0x00007ffff6d3173e in ?? () from /usr/lib/libOpenNI.so.0
#7 0x00007ffff6d316b3 in ?? () from /usr/lib/libOpenNI.so.0
#8 0x00007ffff6d31965 in ?? () from /usr/lib/libOpenNI.so.0
#9 0x00007ffff6d31c0a in xnWaitAndUpdateAll () from /usr/lib/libOpenNI.so.0
#10 0x000000000040346b in WaitAndUpdateAll (this=<optimized out>)
at /usr/include/ni/XnCppWrapper.h:9347
#11 main (argc=1, argv=<optimized out>)
at /tmp/buildd/ros-fuerte-openni-tracker-0.1.3/debian/ros-fuerte-openni-tracker/opt/ros/fuerte/stacks/openni_tracker/src/openni_tracker.cpp:190
It also usually happens after I run it once succesfully. The first time it always runs OK, after that it may work once more, but the next will always segfault. After a reboot the same procedure occurs. |
2014-04-20 06:56:08 -0500 | marked best answer | AMCL + Laser Scan Matcher Crashing Greetings, I am using AMCL for localisation purposes, along with the lase scan matcher in order to use the robot's Hokuyo for odometry. When I run the LSM alone or with Hector mapping the results are satisfying, which means that I get real and precise odometry and localisation. What I want is to load a map made with the above method and use AMCL to localise. So I need to have the local scan matcher working along with AMCL and the map server. The problem is that when AMCL begins its /amcl_pose topic will explode with impossible values such as : header:
seq: 59
stamp:
secs: 1383831717
nsecs: 913606750
frame_id: map
pose:
pose:
position:
x: -6544630.80033
y: 3216474.76088
z: 0.0
orientation:
x: 0.0
y: 0.0
z: 0.702181212802
w: 0.711998275552
covariance: [35307899258837.086, 3493650456763.3486, 0.0, 0.0, 0.0, 0.0, 3493650456763.3496, 26413591121546.38, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 9.113657631539715]
, and promptly crash. The transforms provided can be seen in the following launch files:
Firstly, the lase scan matcher launch file : <launch>
<!-- <node pkg="tf" type="static_transform_publisher" name="world_odom" args="0.10 0 0 0.0 0.0 0.0 /world /map 40"/> -->
<node pkg="tf" type="static_transform_publisher" name="map_odom" args="0.10 0 0 0.0 0.0 0.0 /map /odom 100" />
<node pkg="tf" type="static_transform_publisher" name="odom_bl" args="0.10 0 0 0.0 0.0 0.0 /odom /base_link 100" />
<node pkg="tf" type="static_transform_publisher" name="bl_laser" args="0.0 0 0 0.0 0.0 0.0 /base_link /laser 100" />
<node name="map_server" pkg="map_server" type="map_server" args="/home/****/test.yaml"/>
<node pkg="laser_scan_matcher" type="laser_scan_matcher_node" name="laser_scan_matcher_node" output="screen">
<!-- <param name="fixed_frame" value = "odom"/> -->
<param name="base_frame" value = "/base_link"/>
<param name="fixed_frame" value = "map"/>
<param name="use_cloud_input" value="false"/>
<param name="publish_tf" value="true"/>
<param name="publish_odom" value="true"/>
<param name="use_odom" value="false"/>
<param name="use_imu" value="false"/>
<param name="use_alpha_beta" value="true"/>
<param name="max_iterations" value="10"/>
</node>
<node pkg="hokuyo_node" type="hokuyo_node" name="hokuyo_node">
<param name="intensity" type="bool" value="true"/>
</node>
</launch>
And secondly the AMCL launch file : <launch>
<!--- Run AMCL -->
<include file="/home/******/navigation-hydro-devel/amcl/examples/amcl_diff.launch" />
<node pkg="sek_drive" type="drive_base" respawn="true" name="sek_drive" output="screen">
<rosparam file="$(find sek_drive)/launch/costmap_common_params.yaml" command="load" ns="global_costmap" />
<rosparam file="$(find sek_drive)/launch/costmap_common_params.yaml" command="load" ns="local_costmap" />
<rosparam file="$(find sek_drive)/launch/local_costmap_params.yaml" command="load" />
<rosparam file="$(find sek_drive)/launch/global_costmap_params.yaml" command="load" />
<rosparam file="$(find sek_drive)/launch/base_local_planner_params.yaml" command="load" />
</node>
</launch>
What I notice is that the odometry provided by LSM has always all-zero covariance. Could that be a problem ... (more) |
2014-04-20 06:56:01 -0500 | marked best answer | Laser_scan_matcher can't find base_link Greetings. I am using the following launch file to get odometry from laser_scan_matcher so I can use it with amcl: <launch>
<node name="map_server" pkg="map_server" type="map_server" args="/home/skel/test.yaml" output="screen"/>
<node pkg="hokuyo_transformer" type="laser_to_pcl" name="laser_to_pcl"/>
<node name="hokuyo" pkg="hokuyo_node" type="hokuyo_node" required="true" output="screen" >
<param name="frame_id" type="str" value="laser"/>
<param name="port" type="string" value="/dev/ttyACM0"/>
<param name="intensity" type="bool" value="false"/>
</node>
<node pkg="laser_scan_matcher" type="laser_scan_matcher_node" name="laser_scan_matcher_node" output="screen">
<param name="fixed_frame" value = "odom"/>
<param name="base_frame" value="base_link"/>
<param name="use_alpha_beta" value="true"/>
<param name="use_odom" value="false"/>
<param name="use_imu" value="false"/>
<param name="max_iterations" value="10"/>
</node>
<node pkg="tf" type="static_transform_publisher" name="base_link_to_laser" args="0.0 0.0 0.0 0.0 0.0 0.0 /base_link /laser 40" />
</launch>
But when I run the file I get the following message : [ WARN] [1381839319.059787240]:
Skipping scan [ WARN]
[1381839320.066850260]: Could not get
initial transform from base to laser
frame, "base_link" passed to
lookupTransform argument target_frame
does not exist. However the transform is happenning and is being published since
rosrun tf tf_echo /base_link /laser
outputs At time 1381839581.581
- Translation: [0.000, 0.000, 0.000]
- Rotation: in Quaternion [0.000, 0.000, 0.000, 1.000]
in RPY [0.000, -0.000, 0.000]
Any idea on what is the matter ? I am currently using ROS Hydro on Ubuntu 12.04 |
2014-04-20 06:54:51 -0500 | marked best answer | Rviz segfaulting on startup When starting Rviz (rosrun rviz rviz) it produces a splash screen and immediately segfaults with : $ rosrun rviz rviz
[ INFO] [1371112927.848817565]: rviz revision number 1.8.17
[ INFO] [1371112927.848909490]: compiled against OGRE version 1.7.3 (Cthugha)
[ INFO] [1371112927.885475931]: Loading general config from [/home/****/.rviz/config]
Segmentation fault (core dumped)
I am using ROS Fuerte, with Ubuntu 12.04 LTS and an Intel graphics card (which as far as I understand may be the issue) I tried deleting the config files, differtent OGRE_RTT_MODEs, reinstalling, enabling/disabling OpenGL and updating drivers but so far no luck. UPDATE : Downloaded the latest update today (19/6/2013) and everything seems to work OK When running on GDB (I am sorry about the wall): (gdb) run
Starting program: /opt/ros/fuerte/stacks/visualization/rviz/bin/rviz
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[ INFO] [1371112634.850998769]: rviz revision number 1.8.17
[ INFO] [1371112634.851094314]: compiled against OGRE version 1.7.3 (Cthugha)
[New Thread 0x7fffe36ba700 (LWP 8202)]
[New Thread 0x7fffe2eb9700 (LWP 8204)]
[New Thread 0x7fffe26b8700 (LWP 8205)]
[New Thread 0x7fffe1eb7700 (LWP 8206)]
[New Thread 0x7fffe16b6700 (LWP 8211)]
[ INFO] [1371112634.928360124]: Loading general config from [/home/****/.rviz/config]
[New Thread 0x7fffc85fb700 (LWP 8214)]
[New Thread 0x7fffc7dfa700 (LWP 8215)]
[New Thread 0x7fffc75f9700 (LWP 8216)]
[New Thread 0x7fffc6df8700 (LWP 8217)]
[New Thread 0x7fffc65f7700 (LWP 8218)]
[New Thread 0x7fffc5df6700 (LWP 8219)]
[New Thread 0x7fffc55f5700 (LWP 8220)]
[New Thread 0x7fffc4df4700 (LWP 8221)]
[Thread 0x7fffc85fb700 (LWP 8214) exited]
[Thread 0x7fffc5df6700 (LWP 8219) exited]
[Thread 0x7fffc4df4700 (LWP 8221) exited]
[Thread 0x7fffc55f5700 (LWP 8220) exited]
[Thread 0x7fffc6df8700 (LWP 8217) exited]
[Thread 0x7fffc65f7700 (LWP 8218) exited]
[Thread 0x7fffc75f9700 (LWP 8216) exited]
[Thread 0x7fffc7dfa700 (LWP 8215) exited]
Program received signal SIGSEGV, Segmentation fault.
0x00007fffee014cc0 in xcb_glx_get_string_string_length ()
from /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0
And the backtrace : #0 0x00007fffee014cc0 in xcb_glx_get_string_string_length ()
from /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0
#1 0x00007ffff2b814e4 in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
#2 0x00007ffff2b7ef4c in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
#3 0x00007fffca46d96f in Ogre::GLSupport::initialiseExtensions (this=0x6c30a0)
at /tmp/buildd/ros-fuerte-visualization-common-1.8.4/debian/ros-fuerte-visualization-common/opt/ros/fuerte/stacks/visualization_common/ogre/build/ogre_src_v1-7-3/RenderSystems/GL/src/OgreGLSupport.cpp:53
#4 0x00007fffca4a5b9a in Ogre::GLXGLSupport::initialiseExtensions (
this=0x6c30a0)
at /tmp/buildd/ros-fuerte-visualization-common-1.8.4/debian/ros-fuerte-visualization-common/opt/ros/fuerte/stacks/visualization_common/ogre/build/ogre_src_v1-7-3/RenderSystems/GL/src/GLX/OgreGLXGLSupport.cpp:418
#5 0x00007fffca463365 in Ogre::GLRenderSystem::initialiseContext (
this=0x7fffe0dc7a58, primary=0x7fffe0dcc2e8)
at /tmp/buildd/ros-fuerte-visualization-common-1.8.4/debian/ros-fuerte-visualization-common/opt/ros/fuerte/stacks/visualization_common/ogre/build/ogre_src_v1-7-3/RenderSystems/GL/src/OgreGLRenderSystem.cpp:1061
#6 0x00007fffca46857b in Ogre::GLRenderSystem::_createRenderWindow (
this=0x7fffe0dc7a58, name=..., width=1, height=1, fullScreen=false,
miscParams=0x7fffffffd550)
at /tmp/buildd/ros-fuerte-visualization-common-1.8.4/debian/ros-fuerte-visualization-common/opt/ros/fuerte/stacks/visualization_common/ogre/build/ogre_src_v1-7-3/RenderSystems/GL/src/OgreGLRenderSystem.cpp:1017
#7 0x00007ffff601a96e in Ogre::Root::createRenderWindow (this=0x7fffe0db88d8,
name=..., width=<optimized out>, height=<optimized out>,
fullScreen=<optimized out>, miscParams=<optimized out>)
at /tmp/buildd/ros-fuerte-visualization-common-1.8.4/debian/ros-fuerte-visualization-common/opt/ros/fuerte/stacks ... (more) |