ipa320 / care-o-bot Goto Github PK
View Code? Open in Web Editor NEWHome Page: http://www.care-o-bot.de
License: Apache License 2.0
Home Page: http://www.care-o-bot.de
License: Apache License 2.0
previous release: #51
cob_android
: up-to-date ๐ 0.1.4
cob_calibration_data
: ros/rosdistro#20565 ๐ 0.6.10
cob_command_tools
: ros/rosdistro#20572 ๐ 0.6.10
cob_common
: kinetic: ros/rosdistro#20566, melodic: ros/rosdistro#20568 ๐ 0.6.10
cob_control
: ros/rosdistro#20567 ๐ 0.7.3
cob_driver
: ros/rosdistro#20570 ๐ 0.6.13
cob_environments
: ros/rosdistro#20569 ๐ 0.6.7
cob_extern
: up-to-date ๐ 0.6.12
cob_gazebo_plugins
: up-to-date ๐ 0.7.2
cob_hand
: up-to-date ๐ 0.6.5
cob_manipulation
: up-to-date ๐ 0.7.1
cob_navigation
: up-to-date ๐ 0.6.7
cob_perception_common
: ros/rosdistro#20571 ๐ 0.6.13
cob_robots
: ros/rosdistro#20574 ๐ 0.6.7
cob_simulation
: up-to-date ๐ 0.6.10
cob_substitute
: up-to-date ๐ 0.6.7
cob_supported_robots
: ros/rosdistro#20573 ๐ 0.6.10
schunk_modular_robotics
: up-to-date ๐ 0.6.12
sick_visionary_t
:
care-o-bot
: ros/rosdistro#20575 ๐ 0.6.7
I start to work with care-o-bot4. But I cannot install simulation by "http://wiki.ros.org/Robots/Care-O-bot/indigo" (I have confirmed that it was installed in the last year, but not now.)
So I want to install by cob_simulator but I don't know how to install by cob_simulator in github.
Before I activate the hardware, I want to simulation hard.
I want you to help me simulate.
Thank you.
cob_android
: ros/rosdistro#16717, ros/rosdistro#16718
cob_calibration_data
: ros/rosdistro#16719, ros/rosdistro#16720
cob_command_tools
: ros/rosdistro#16721, ros/rosdistro#16722
cob_common
: ros/rosdistro#16723, ros/rosdistro#16724
cob_control
: ros/rosdistro#16745, ros/rosdistro#16748
cob_driver
: ros/rosdistro#16725, ros/rosdistro#16726
cob_environments
: ros/rosdistro#16727, ros/rosdistro#16728
cob_extern
: ros/rosdistro#16713, ros/rosdistro#16714
cob_gazebo_plugins
: ros/rosdistro#16746, ros/rosdistro#16747
cob_hand
: ros/rosdistro#16729, ros/rosdistro#16730
cob_manipulation
: ros/rosdistro#16749, ros/rosdistro#16750
cob_navigation
: ros/rosdistro#16731, ros/rosdistro#16732
cob_perception_common
: ros/rosdistro#16733, ros/rosdistro#16734
cob_robots
: ros/rosdistro#16735, ros/rosdistro#16736
cob_simulation
: ros/rosdistro#16737, ros/rosdistro#16739
cob_substitute
: ros/rosdistro#16738, ros/rosdistro#16740
cob_supported_robots
: ros/rosdistro#16715, ros/rosdistro#16716
schunk_modular_robotics
: ros/rosdistro#16741, ros/rosdistro#16742
:sick_visionary_t
care-o-bot
: ros/rosdistro#16751, ros/rosdistro#16753
As discussed here there seems to be a problem with travis tests failing "randomly".
This should be investigated in more detail!
@ipa-fmw @ipa-mdl @ipa-bnm @ipa-mig FYI
Tracking the related PRs to rosdistro:
0.1.2-0
ros/rosdistro#109560.6.5-0
ros/rosdistro#109530.6.4-0
ros/rosdistro#109570.6.5-0
ros/rosdistro#109540.6.11-0
ros/rosdistro#109580.6.7-0
ros/rosdistro#109760.6.3-0
ros/rosdistro#109550.6.4-0
ros/rosdistro#109510.6.4-0
ros/rosdistro#109600.6.4-0
ros/rosdistro#109640.6.4-0
ros/rosdistro#109650.6.7-0
ros/rosdistro#109610.6.5-0
ros/rosdistro#109680.6.5-0
ros/rosdistro#109630.6.3-0
ros/rosdistro#109520.6.7-0
ros/rosdistro#109621.1.6-0
ros/rosdistro#109500.6.5-0
ros/rosdistro#10969Tracking the related PRs to rosdistro:
indigo_dev
for Indigo and kinetic_dev
for Kinetic
0.1.3-0
indigo: ros/rosdistro#15548 โ
kinetic: ros/rosdistro#15655 โ
0.6.7-0
indigo: ros/rosdistro#15540 โ
kinetic: ros/rosdistro#15542 โ
0.6.6-0
indigo: ros/rosdistro#15538 โ
kinetic: ros/rosdistro#15594 โ
0.6.7-0
indigo: ros/rosdistro#15531 โ
kinetic: ros/rosdistro#15532 โ
0.6.15-0, 0.7.0-0
indigo: ros/rosdistro#15546 โ
kinetic: ros/rosdistro#15560 โ
0.6.10-0
indigo: ros/rosdistro#15579 โ
kinetic: ros/rosdistro#15580 โ
0.6.5-0
indigo: ros/rosdistro#15545 โ
kinetic: ros/rosdistro#15547 โ
0.6.11-0
Indigo: ros/rosdistro#15529 โ
Kinetic: ros/rosdistro#15530 โ
0.6.6-0, 0.7.1-0
indigo: ros/rosdistro#15537 โ
kinetic: ros/rosdistro#15539 โ
0.6.2-0
indigo: ros/rosdistro#15549 โ
kinetic: ros/rosdistro#15551 โ
0.6.5-1
@ipa-rmb indigo: ros/rosdistro#15641 โ
kinetic ros/rosdistro#15698 โ
0.6.5-0
indigo: ros/rosdistro#15558 โ
kinetic: ros/rosdistro#15593 โ
0.6.10-0
indigo: ros/rosdistro#15550 โ
kinetic: ros/rosdistro#15552 โ
0.6.7-1
@ipa-rmb indigo: ros/rosdistro#15646 โ
kinetic: ros/rosdistro#15699 โ
0.6.8-0
@ipa-rmb indigo: ros/rosdistro#15648 โ
kinetic: ros/rosdistro#15700 โ
0.6.6-0
indigo: ros/rosdistro#15556 โ
kinetic: ros/rosdistro#15557 โ
0.6.7-0
indigo: ros/rosdistro#15534 โ
kinetic: ros/rosdistro#15536 โ
0.6.9-0
indigo: ros/rosdistro#15533 โ
kinetic: ros/rosdistro#15568 โ
0.0.5-0, 0.0.5-1
indigo: ros/rosdistro#15665 โ
kinetic: ros/rosdistro#15666 โ
@ipa-fmw @ipa-nhg @ipa-mdl @ipa-mig @ipa-rmb @ipa-bnm
https://github.com/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+user%3Aipa320+Migration+package+format+2
Let's use this Issue for general discussion about what's still missing for a successfull migration to package format 2:
Remaining repos to be migrated:
Remaining decisions to be applied wherever it occurs:
Please contribute to the discussion in case something is not yet mentioned here...
@ipa-fez @ipa-jba @ipa-rmb @ipa-fmw @ipa-mig @ipa-nhg @ipa-mdl @fmessmer FYI
I'll start this issue for discussion that should lead to an improved/extended default .travis.yml
that we use in all our repos (see list below).
I suggest to first discuss which new features are to be added to the new default .travis.yml
and then provide PRs for all affected repos in a torrent for consistency!
New features to be added:
jade
testing - once and for all - we do not support it...safes some jobs on the travis serversUPSTREAM_WORKSPACE=file
to test with .rosinstall
file + UPSTREAM_WORKSPACE=debian
(default) to test against releases (I don't think we need to make another distinction against ROS_REPO=ros
and ROS_REPO=ros-shadow-fixed
industrial_ci/master
)CATKIN_LINT
!Who steps forward and is willing to provide a suggestive PR against care-o-bot
, i.e. this, repo?
NAV-REPOS:
PERCEPTION-REPOS:
MSH-REPOS:
Please add repos in case I missed one...
cob_android
: up-to-date
cob_calibration_data
: ros/rosdistro#18589 ros/rosdistro#18590
cob_command_tools
: ros/rosdistro#18645 ros/rosdistro#18646
cob_common
: ros/rosdistro#18592 ros/rosdistro#18593
cob_control
: ros/rosdistro#18610 ros/rosdistro#18611
cob_driver
: ros/rosdistro#18596 ros/rosdistro#18597
cob_environments
: up-to-date
cob_extern
: up-to-date
cob_gazebo_plugins
: up-to-date
cob_hand
: ros/rosdistro#18598 ros/rosdistro#18599
cob_manipulation
: up-to-date
cob_navigation
: ros/rosdistro#18600 ros/rosdistro#18602
cob_perception_common
: ros/rosdistro#18601 ros/rosdistro#18603
cob_robots
: ros/rosdistro#18604 ros/rosdistro#18605
cob_simulation
: ros/rosdistro#18606 https://github.com/ros/rosdistro/pulls
cob_substitute
: up-to-date
cob_supported_robots
: ros/rosdistro#18594 ros/rosdistro#18595
schunk_modular_robotics
: ros/rosdistro#18607 ros/rosdistro#18608
:sick_visionary_t
care-o-bot
: up-to-date
@ipa-fmw @ipa-mdl
Is there a way to configure travis in a way so that it tells us about missing dependencies as in
diagnostic_updater
diagnostic_msgs
We would need something like "rosdep install isolated/packagewise-with-uninstall"?
@fmessmer FYI
i.e. test whether a change in:
this can be done by adding the downstream dependencies to the .rosinstall file of the upstream repo
@ipa-fmw @ipa-nhg @ipa-mig @ipa-bnm @ipa-rmb
As we now have consequently reviewed and beautified our repositories and code, the next step commendable contribution to the ROS community could/should be to tend our attention to documentation!
I.e. we should:
I guess a minimum wiki documentation should include a meaningful description (from package.xml) and a descriptions of the ROS interfaces, i.e. subscribed/published topics/services/action as well as configurable parameters....)
ipa_canopen
was EOL in ros/rosdistro@c7a3fe4 and was removed from the package index, but care_o_bot_robot
still depends on it.
Either ipa_canopen
should be re-added, or care_o_bot_robot
should remove the dependency and be released.
Tested repositories
Not Tested
(Note that those packages have not been tested for functionality!)
as of the latest rosdistro
review guidelines, every released repo needs a LICENSE
file
https://github.com/ros/rosdistro/blob/master/REVIEW_GUIDELINES.md#types-of-pull-requests
for the next release cycle we should add a LICENSE
file for the Apache 2.0
license:
https://opensource.org/licenses/Apache-2.0
should be done for
I am the maintainer of the following packages, which I cannot support anymore due to me changing jobs.
Who is willing to take over? (* might also be deleted)
because it was requested in ipa320/schunk_modular_robotics#206, why not at least add melodic
checks to travis...
cob_android
: ipa320/cob_android#35
cob_calibration_data
: ipa320/cob_calibration_data#154
cob_command_tools
: https://github.com/ipa320/cob_command_tools/pull/245
cob_common
: https://github.com/ipa320/cob_common/pull/271
cob_control
: https://github.com/ipa320/cob_control/pull/208
cob_driver
: ipa320/cob_driver#380
cob_environments
: ipa320/cob_environments#135
cob_extern
: ipa320/cob_extern#99
cob_gazebo_plugins
: ipa320/cob_gazebo_plugins#38
cob_hand
: ipa320/cob_hand#23
cob_manipulation
: ipa320/cob_manipulation#138
cob_navigation
: ipa320/cob_navigation#106
cob_perception_common
: ipa320/cob_perception_common#95
cob_robots
: ipa320/cob_robots#780
cob_simulation
: ipa320/cob_simulation#168
cob_substitute
: ipa320/cob_substitute#52
cob_supported_robots
: ipa320/cob_supported_robots#21
schunk_modular_robotics
sick_visionary_t
care-o-bot
: #53
not to be released:
cob_docking
: https://github.com/ipa320/cob_docking/pull/470.0.2
ipa_differential_docking
: https://github.com/ipa320/ipa_differential_docking/pull/30.0.2
pointcloud_to_laserscan
: https://github.com/ipa320/pointcloud_to_laserscan/pull/131.3.2
sick_flexisoft
: https://github.com/ipa320/sick_flexisoft/pull/530.1.2
canopen_test_utils
: ipa320/canopen_test_utils#70.7.0
@ipa-srd @ipa-srd-fg
The goal is to prepare the cob_bringup
/cob_bringup_sim
structure (as well as everything that comes with it, e.g. robot_description, controller,...) to be able to use multiple robots at the same time.
This might later be extended to a multi-master setup....
Feel free to add more issues and problems faced in order to be able to solve them in accordance with single-robot usecase
@ipa-fmw @ipa-nhg @ipa-mig FYI
@ipa-fmw @ipa-nhg @ipa-mdl @ipa-mig @ipa-rmb @ipa-bnm @fmessmer FYI
This should be done after migration to package xml format 2 has been completed
See related comment
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 is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
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.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.