konanrobot / alufr-ros-pkg Goto Github PK

What steps will reproduce the problem?
1. Compile latest commit where USE_PCL_ICP was inserted

What is the expected output? What do you see instead?
/rgbdslam/src/node.cpp:45:17: fatal error: icp.h: No such file or directory


What version of the product are you using? On what operating system?
Ubuntu 12.04 with latest commit of rgbdslam

Please provide any additional information below.

Just a note, you are missing continual_planning_executive/TemporalAction.h in 
your svn. I finally found a possibly old version here 
(http://ros.org/rosdoclite/fuerte/api/continual_planning_executive/html/Temporal
Action_8h_source.html) to temporarily compile the code, but if you could upload 
the current version to the svn that would be great!

Thanks
Jennifer

I'm not sure this works completely correctly, specifically I just connected the 
dogleg optimizer algorithm. Also the launcher starts everything now, but with 
the existing settings the point cloud does not get displayed

[deleted issue]

What steps will reproduce the problem?

1. Setup ros node using depth_image_proc to publish point_cloud_xyzrgb on 
/camera/points topic.

2. Execute this command:

$ rosrun octomap_server octomap_server_node cloud_in:=/camera/points 
_frame_id:=/world

[ INFO] [1369221775.959744322]: Publishing latched (single publish will take 
longer, all topics are prepared)
Illegal instruction (core dumped)

What is the expected output?

octomap-sever should process point cloud and publish occupancy grid markers 
that can be visualised in rviz.

What do you see instead?

octomap_server node crashes with Illegal instruction (core dumped)

What version of the product are you using?

ROS feurte (ros-feurte-octomap-mapping)

On what operating system?

Linux XX 3.2.0-43-generic #68-Ubuntu SMP Wed May 15 03:33:33 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux

Please provide any additional information below.

My setup used to work correctly - I believe there was an update at the 
beginning of may due to file timestamps:

 ls -lh /opt/ros/fuerte/stacks/octomap_mapping/
total 20K
-rw-r--r--  1 root root  817 Feb 16 12:44 CMakeLists.txt
-rw-r--r--  1 root root   47 Feb 16 12:44 Makefile
drwxr-xr-x  2 root root 4.0K May  8 13:54 octomap
drwxr-xr-x 11 root root 4.0K May  8 13:54 octomap_server
-rw-r--r--  1 root root  985 Feb 16 12:44 stack.xml

I hadn't used the tools since then (and didn't notice I had updated it) but now 
it crashes (with the exact same setup that used to work).

I have attached a patch to expose Naoqi's ALBehaviorManager functions to ROS. 
Note it doesn't expose all of the Naoqi's functions but it allows to execute a 
behaviour, to stop a currently-running behaviour and to list all installed 
behaviours.

Implementation is coded as a python script and leverages ROS services (to query 
installed behaviors) and actionlib (to execute/stop a behaviour).

The code has been tested on Naoqi v.1.12 both in a virtual environment and in a 
real NAO.

I am happy to improve the code if needed.

Patch has been tested against nao_robot rev.3046 (latest revision)

Short description:
Expose NaoQi's ALBehaviorManager core functions to ROS through the use of 
services and actionlib. Functionality includes start/stop a behavior and 
listing of installed behaviors. One new service and one new action were added.

What steps will reproduce the problem?
1. Run RGBDSLAM
2. Repeatedly request the model to be sent, either using the GUI or with 
service calls. Also happens if you repeatedly try to save trajectory. I have 
tried different intervals of making requests but it even happens if requesting 
every 10 seconds.

I get the following error message:

[rgbdslam-7] process has died [pid 20770, exit code -11].
log files: 
/home/james/.ros/log/6dd532b8-573d-11e1-8050-002608dcf037/rgbdslam-7*.log

What version of the product are you using? On what operating system?
Ubuntu 11.10. ROS Electric. Happens with either SURF or SIFTGPU techniques.

When calling a service, e.g. "rosservice call rgbdslam/ros_ui save_features" 
the service call returns immediately after the correspondig Qt signal is sent. 
This makes a script-like interaction with rgbdslam difficult, e.g. when you 
want to process the files that are created by a service call.
I suggest to add a signal that is emitted when the work has finished and 
waiting for this signal to arrive in RosUi::services*.
As I am interested in this behaviour I am willing to work on it to provide a 
patch.
Do you see any downsides?

Hi there!

I attached a patch, which adds a nodelet version of the octomap server.
The changes are minimal.
Only important change to files outside octomap_server_nodelet.cpp is the 
addition of passing a node handle to the OctomapServer class and also using the 
same handle for retrieving parameters.
This is necessary, because otherwise topic and parameter remappings will not 
work.

Marcus

When doing my previous refactoring I hadn't needed to access to 
m_bodyPoseClient or m_bodyPoseTimeOut. Now I've added some custom poses to the 
pose_manager via the yaml file, I need a way of triggering them from my 
TeleopNaoJoy subclass. The quick way to do this is to make ththe m_bodyPose*  
variables protected in TeleopNaoJoy. The slightly nicer way would be to add a 
protected method that takes a single string arg and sends that as the 
pose_goal, waits, then returns the result. Please could you do one of these? I 
don't mind which.

thanks, Nick

What steps will reproduce the problem?
1. Install Hydro
2. Follow http://wiki.ros.org/rgbdslam


Rosmake complains about unmet dependency: PCL


This may be relivant:
http://wiki.ros.org/hydro/Migration#PCL

I am in the process of developing a Nao teleoperation node to generate a demo 
system. As I would like to reuse as much existing functionality as possible, 
I'd like to base this on the teleop_nao_joy node. However the source files for 
this class do not currently allow subclassing. I have restructured them (based 
on svn rev 2730) to do so. In summary I've created 
nao_teleop/include/nao_teleop/teleop_nao_joy.h and made a library that is built 
from teleop_nao_joy.cpp. There is now a new file teleop_nao_joy_node.cpp which 
creates a node which has the same functionality as the previous 
teleop_nao_joy.cpp node. New classes can be developed by subclassing 
TeleopNaoJoy and calling subscribeToJoystick with a callback from the subclass. 
I've attached an svn diff of the changes plus an example of subclassing that 
works. I would be extremely grateful if you could merge these into the trunk, 
or let me know what changes you'd like before merging can happen.

cheers, Nick