- Initialize the org.happy.artist.rmdmia.
- Call bag.start(OutputStream os, Bag.CHUNK_COMPRESSION_NONE)); // Where os is the OutputStream you intend to write the file. Examples could be a FileOutputStream, or a network output stream that writes the file to Google Drive, or Dropbox (just examples).
- Call bag.addConnectionHeader(char topic, int conn, char connection_header_hex); for each new connection header on connection handshake. int conn is a unique int connection id chosen for the connection (might be a good idea to iterate through topic ids to create an int array, or other mechanism to chose a unique int. connection_header_hex will be the ROS Serialized Message in the connection header.
- Call bag.addMessage(long time, int conn, char message_data_hex); Pass in the long time, associated connection header int conn id, and the ROS serialized message to add to the rosbag file.
(Human Support Robot) on October 23th and 24th in Tokyo. TORK assisted
the event and the software.
HSR has been developed as an elderly care for domestic situations as
well as in medical facilities. This time TMC invited researchers and
students from institutes in Japan. 15 participants got a hands-on
experience, tried out making small tasks to let the mobile-manipulator
robot interact with human, and had fun.
All of the higher-end functionalities such as self-localization,
vision-based collision avoidance, motion planning and so on are
available via a de-facto standard opensource robotics framework ROS
(Robot Operating System) (that is, as previously announced). It also
comes with script language interface so that it doesn't require
developers to be well acquainted with ROS.
With the feedback from the attendees this time TMC expects to boost
the development in the future.
ROS Aerial Vehicle Users,
We'd like to invite you to participate in an effort to develop a standard set of messages for communicating within robotics components on Micro Air Vehicles (MAVs). At the IROS workshop on MAV's (proceedings) this fall it was identified that the MAV community has many different implementations of the same capabilities. They are often all closely related and are almost compatible but rarely is it easy to switch between different implementations, or use different implementations together. From that discussion it was proposed to work toward building up a common way to communicate and enable the MAV community to collaborate most effectively.
To make this happen we have setup a mailinglist and wiki pages to be a place to coordinate this effort (MAV SIG, mailing list). If you are interested in this topic we ask that you join, listen and participate so that we can get as broad a spectrum of voices as possible.
We have chosen the ROS SIG format as it has proven effective at developing standard messages which are used by many people every day. ROS SIG's are relatively unstructured and allow adaptation for differences in each community and process.
We plan to use the ROS .msg format as a way to formalize the messages, since it is a relatively compact way to express messages which has representations in many languages. The most important part of the process will not be the actual msg file that comes out, but the datatypes for which people can rely on being isomorphic when transitioning between systems.
Having common datatypes will allow us to have better modularity and interoperability. As an example from the ROS ecosystem, there are 10+ different laser scanner drivers in the ROS ecosystem and 18+ different camera drivers (ROS sensors). Because these drivers all use a standard set of messages a user of those sensors can switch which sensor they are using on their system, or deploy systems with different sensors and the rest system will continue to operate without modifications. There are more complicated examples such as the navigation stack which has a standard set of messages for sending commands and providing feedback. This same interface has been used for differential drive, holonomic, free flying, and even walking robots.
There are already dozens of MAV related ROS packages released and we hope that developing these standard messages can help coordinate the efforts of the many contributors already working on aerial vehicles in ROS.
Tully Foote (OSRF), Lorenz Meier (ETHZ / CVG, PX4), Markus Achtelik (ETHZ / ASL).
From Florian Weißhardt via ros-users@
Position: Software Engineer, possibility to obtain PhD degree
Location: Fraunhofer IPA, Stuttgart, Germany
Experience: Strong skills in software design and C/C++ development and rich experience in ROS development
Finding solutions to organizational and technological challenges, particularly within the production environment of industrial enterprises. That, in a nutshell, is the key focus of the research and development work carried out at the Fraunhofer Institute for Manufacturing Engineering and Automation IPA. With 14 individual departments engaged in the fields of Corporate Organization, Automation and Surface Engineering, our R&D projects aim to enhance production processes and make products more cost-effective and environmentally friendly by identifying and exploiting the potential for automation and streamlining at clients' companies.
The Fraunhofer IPA department for robot and assistive systems develops service robots for various application fields (e.g. domestic, inspection, logistics, production assistance, manufacturing, etc.) with the goal of reliable, robust and safe service of these robots in everyday environments. These applications require complex software systems including navigation, planning, perception and manipulation for dynamic and changing environments and intuitive human-robot interaction.
The position covers the development of concepts and tools to reduce integration effort and simplify application development for these complex robotic systems in the frame of public funded national and EU projects. The transfer of the results to industry by organizing workshops, publishing articles relevant magazines and exhibiting demonstrators at fairs and conferences is part of the job description as well.
You have completed your master or diploma degree with excellent results and are interested in interdisciplinary research with high-tech robots like Care-O-bot or KUKA iiwa. You could already gather experience in scientific working and optimally already presented your first results at an international conference. You are confident in software architectures and software engineering and have practical experiences with the development of robot applications in ROS.
We offer you a highly interesting and diverse work environment with both contact to top robotics researchers and industry. In addition to obtaining a phd degree, the position encompasses early transfer of project and staff responsibility. For the implementation and validation of your ideas, we offer exceptionally equipped laboritories and test environments.
- Rich experience in ROS development
- A Master/Diploma degree from a top university in computer science, robotics or software engineering
- Strong skills software design and C/C++ development
- Proficient oral and written English skills
- Experience with model-driven engineering approaches
- Oral and written German skills
Please include the following documents in your application:
- Cover letter that expresses your motivation and (research) goals
- Transcripts of all obtained degrees (including scholar education)
- References and certificates relevant to the position
Please send your application to firstname.lastname@example.org referring to position IPA-2014-109.
From Nick Hawes via ros-users@
I would like to announce the release of a new suite of tools to enable the persistent storage, analysis and retrieval of ROS messages in a MongoDB database.
The mongodb_store package:
... provides nodes to store arbitrary ROS messages in a MongoDB database, query the database and retrieve messages, with helper classes in C++ and Python. Nodes are also available to provide rosbag-like functionality using the [same db format] (http://wiki.ros.org/mongodbstore#LoggingofTopics:mongodblog) and also [parameter persistence across system runs] (http://wiki.ros.org/mongodbstore#Parameterpersistence:config_manager.py).
Packages are available on Ubuntu for Indigo and Hydro, e.g.
- ros-indigo-mongodb-log - The mongodb_log package
- ros-indigo-mongodb-store - A package to support MongoDB-based storage and analysis for data from a ROS system, eg. saved messages, configurations etc
- ros-indigo-mongodb-store-msgs - The mongodbstoremsgs package
These tools were developed by the STRANDS project to support the development, debugging and runtime introspection of long-term autonomous mobile robots, but we hope they will be useful to the ROS community more generally.
Note that there is an overlap in functionality between these tools and warehouse-ros. We developed our own solution as the existing packages appeared to be unsupported and special-purpose, but as this appears to be changing, we may want to look at combining these two packages.
For feedback, pull requests, feature requests and bug reports please go to: https://github.com/strands-project/mongodb_store/issues