weisshardt's profile - activity

Is it possible to ignore RPM releases and only trigger Ubuntu targets?

The cob_driver stack is specific for Care-O-bot hardware and will probably not work without modifications on different hardware. Which hardware are you working on?

There is no executable file output by purpose for cob_canopen_motor. There is just a lib generated which is e.g. linked from cob_base_drive_chain. cob_base_drive_chain generates the executable file.

The problem you describe is not related to the cob_script_server but to the trajectory controller which is moving the components in gazebo. The script_server just forwards the action result which is returned by the actionlib interface to the gazebo controllers. So far I am not aware of a sulution solving this. If you want to investigate furhter you'd probably dive into cob_controller_configuration_gazebo.

The argument pkg_arg get substituted by the absolute path to the package my_pkg which could for example be the string /home/user/ros/my_pkg. Hence rosbuild_add_roslaunch_check could check the current ROS_PACKAGE_PATH for the existence of this package and the file included.launch as roslaunch does when executing. The value for the argument is determined by the current ROS_PACKAGE_PATH which can be checked offline in my opinion.

By the way, the behaviour is the same as hardcoding the argument to point to my_pkg:

<arg name="pkg_arg" default="/home/user/ros/my_pkg"/>

So why shouldn't it be possible to check this?

Hi,

maybe this is a very special usecase but I encountered some missmatching between the behaviour of roslaunch and the result of rosbuild_add_roslaunch_check.

In detail: I tried to setup a launch file with

<?xml version="1.0"?>
<launch>

<!-- define arg -->
<arg name="pkg_arg" default="$(find my_pkg)"/>

<!-- use arg -->
<param name="param1" value="$(arg pkg_arg)"/> <!-- this is working, test is ok -->
<include file="$(arg pkg_arg)/included.launch"/> <!-- this is working too, but test fails-->

</launch>

trying to use a launch file argument to find an include file. The behaviour when roslaunching the file is fine, the parameter gets uploaded and the included.launch file gets included. Perfect. But when I add a rosbuild_add_roslaunch_check for that file I get

Traceback (most recent call last):
  File "/opt/ros/electric/stacks/ros_comm/tools/rostest/bin/roslaunch-check.py", line 86, in <module>
error_msg = check_roslaunch_file(roslaunch_path)
  File "/opt/ros/electric/stacks/ros_comm/tools/rostest/bin/roslaunch-check.py", line 48, in check_roslaunch_file
error_msg = roslaunch.rlutil.check_roslaunch(roslaunch_file)
  File "/opt/ros/electric/stacks/ros_comm/tools/roslaunch/src/roslaunch/rlutil.py", line 206, in check_roslaunch
base_pkg, file_deps, missing = roslaunch.depends.roslaunch_deps([f])
  File "/opt/ros/electric/stacks/ros_comm/tools/roslaunch/src/roslaunch/depends.py", line 239, in roslaunch_deps
rl_file_deps(file_deps, launch_file, verbose)
  File "/opt/ros/electric/stacks/ros_comm/tools/roslaunch/src/roslaunch/depends.py", line 146, in rl_file_deps
parse_launch(launch_file, file_deps, verbose)
  File "/opt/ros/electric/stacks/ros_comm/tools/roslaunch/src/roslaunch/depends.py", line 131, in parse_launch
_parse_launch(launch_tag.childNodes, launch_file, file_deps, verbose)
  File "/opt/ros/electric/stacks/ros_comm/tools/roslaunch/src/roslaunch/depends.py", line 82, in _parse_launch
sub_launch_file = resolve_args(tag.attributes['file'].value)
  File "/opt/ros/electric/ros/core/roslib/src/roslib/substitution_args.py", line 216, in resolve_args
resolved = _arg(resolved, a, args, context)
  File "/opt/ros/electric/ros/core/roslib/src/roslib/substitution_args.py", line 167, in _arg
raise ArgException(arg_name)
roslib.substitution_args.ArgException: pkg_arg

My guess is that something in the cmake macro for checking roslaunch files is wrong. Can somebody point me to the right location?

Best, Florian

libpcan is downloading a tarball from code.ros.org. Are you sure you have internet access and code.ros.org is available from your location?

I just did a fresh checkout and successfull build on ubuntu 10.04, 11.10 and 12.04 for electric and fuerte.

The cob_apps stack is deprecated. This means that there is no release for oneiric. The content of cob_apps was spread into cob_command_tools, cob_navigation and cob_manipulation.

The cob_apps stack is deprecated. This means that there is no release for oneiric. The content of cob_apps was spread into cob_command_tools, cob_navigation and cob_manipulation.

Hi, the fix is in the new release which ich now available in the debian sources of electric, too.

Hi, the fix is in the new release which ich now available in the debian sources of electric, too.