Home Page: http://www.ros.org/wiki/uos_tools
License: BSD 3-Clause "New" or "Revised" License
Useful tools for ROS implemented in Knowledge-based Systems group of Osnabrück University.
The current main branch is working with ROS2 humble. Some features from the ROS1 version are still missing. Feel free to contribute. To access the complete toolset for ROS1, switch to the corresponding branches: noetic, kinetic, ...
Running catkin_lint results in:
Warnings:
battery_guard: warning: unconfigured build_depend on 'rospy'
simple_approximate_time_synchronizer: warning: executable file 'src/simple_approximate_time_synchronizer/__init__.py' is not installed
Full results:
acc_finder: notice: package description starts with boilerplate 'This package contains two'
acc_finder: CMakeLists.txt(6): notice: list COMPONENTS should be sorted
acc_finder: CMakeLists.txt(8): notice: list CATKIN_DEPENDS should be sorted
acc_finder: CMakeLists.txt(12): notice: use ${PROJECT_NAME} instead of 'acc_finder'
battery_guard: warning: unconfigured build_depend on 'rospy'
battery_guard: notice: meaningless package description 'battery_guard'
battery_guard: CMakeLists.txt(10): notice: use ${PROJECT_NAME} instead of 'battery_guard'
joint_state_muxer: notice: meaningless package description 'joint_state_muxer'
joint_state_muxer: CMakeLists.txt(12): notice: use ${PROJECT_NAME} instead of 'joint_state_muxer'
move_base_straight: notice: meaningless package description 'move_base_straight'
move_base_straight: CMakeLists.txt(13): notice: use ${PROJECT_NAME} instead of 'move_base_straight'
rgbd_rosbag_tools: notice: meaningless package description 'rgbd_rosbag_tools'
rgbd_rosbag_tools: CMakeLists.txt(6): notice: list COMPONENTS should be sorted
rgbd_rosbag_tools: CMakeLists.txt(8): notice: list CATKIN_DEPENDS should be sorted
rotunit_snapshotter: CMakeLists.txt(8): notice: list COMPONENTS should be sorted
rotunit_snapshotter: CMakeLists.txt(20): notice: list CATKIN_DEPENDS should be sorted
rotunit_snapshotter: CMakeLists.txt(24): notice: use ${PROJECT_NAME} instead of 'rotunit_snapshotter'
rotunit_snapshotter: CMakeLists.txt(25): notice: use ${PROJECT_NAME} instead of 'rotunit_snapshotter'
rotunit_snapshotter: CMakeLists.txt(26): notice: use ${PROJECT_NAME} instead of 'rotunit_snapshotter'
rotunit_snapshotter: CMakeLists.txt(28): notice: use ${PROJECT_NAME} instead of 'rotunit_snapshotter'
simple_approximate_time_synchronizer: warning: executable file 'src/simple_approximate_time_synchronizer/__init__.py' is not installed
simple_approximate_time_synchronizer: notice: meaningless package description 'simple_approximate_time_synchronizer'
simple_approximate_time_synchronizer: CMakeLists.txt(6): notice: list COMPONENTS should be sorted
simple_approximate_time_synchronizer: CMakeLists.txt(10): notice: list CATKIN_DEPENDS should be sorted
tf_publisher_gui: notice: package description starts with boilerplate 'This is a'
tf_publisher_gui: CMakeLists.txt(12): notice: use ${PROJECT_NAME} instead of 'tf_publisher_gui'
uos_common_urdf: notice: package description starts with boilerplate 'This package contains'
uos_common_urdf: CMakeLists.txt(6): notice: list COMPONENTS should be sorted
uos_common_urdf: CMakeLists.txt(8): notice: list CATKIN_DEPENDS should be sorted
uos_diffdrive_teleop: notice: meaningless package description 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(6): notice: list COMPONENTS should be sorted
uos_diffdrive_teleop: CMakeLists.txt(10): notice: list CATKIN_DEPENDS should be sorted
uos_diffdrive_teleop: CMakeLists.txt(14): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(15): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(16): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(18): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(19): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(20): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(22): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(23): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(24): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(26): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(27): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(28): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(30): notice: use ${PROJECT_NAME} instead of 'uos_diffdrive_teleop'
uos_diffdrive_teleop: CMakeLists.txt(30): notice: list TARGETS should be sorted
uos_freespace: notice: meaningless package description 'uos_freespace package'
uos_freespace: CMakeLists.txt(6): notice: list COMPONENTS should be sorted
uos_freespace: CMakeLists.txt(10): notice: list CATKIN_DEPENDS should be sorted
uos_freespace: CMakeLists.txt(14): notice: use ${PROJECT_NAME} instead of 'uos_freespace'
uos_freespace: CMakeLists.txt(15): notice: use ${PROJECT_NAME} instead of 'uos_freespace'
uos_freespace: CMakeLists.txt(16): notice: use ${PROJECT_NAME} instead of 'uos_freespace'
uos_freespace: CMakeLists.txt(18): notice: use ${PROJECT_NAME} instead of 'uos_freespace'
Hi there,
I am trying to write a ROS node for ROS hydro and Gazebo 1.9 to use the reading from a hokuyo laser scanner to avoid an obstacle and move to the goal. Is this the purpose of the uos-freespace.cc ?
In this file, where is the goal position of the robot ?
In my case, I am using move_base to obtain the goal position but I want to use your code to avoid obstacles using a laser scanner and also use the goal set by move_base to move towards it. Could you help me with this please?
Ich würde gerne das Repo aufräumen um es dann zu releasen, damit wir die ceres Roboter und den Pluto Roboter einfach installieren können und hier einen definierten Stand haben. Einige Pakete sind Outdated. Also mir fallen da spontan drei Möglichkeiten ein.
Ich habe mal eine Liste gemacht was ich denke, was wir noch brauchen und was wir releasen sollten
Martin @mintar sag mal deine Meinug dazu.
According to http://ros-users.122217.n3.nabble.com/urdfpy-URDF-parser-in-Python-td3828595.html, urdf_python is now integrated into urdf_parser_py.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.