jrivero's profile - activity

please don't post your question in three different sites. Let's follow the problem here http://answers.gazebosim.org/que

Looks like the system that run bloom was configured to use our rosdep overlay typically used to release ROS wrappers for gazebo new versions not officially supported in ROS.

If you still have access to that system, you can easily verify it by running:

rosdep resolve gazebo_msgs

If this is the case, in order to use the standard ROS supported versions again, I would suggest to remove the 00-* files in /etc/rosdep/sources.list.d , run rosdep updateand launch bloom again to generate a new -release version of your debian control files.

We will be upgrading the version of askbot which answers.ros.org runs soon.

Would be nice to get an RSS feed for an specific tag.

Tag pages showing lists of corresponding answers display an RSS button which always points to the "all answers" feed.

After checking the askbot site, their links to RSS feed in a tag page can generate this kind of tag feed via HTML param "?tags=". Probably is a question to update the whole askbot since theirs is in 0.7.32 and answers.ros.org 0.6.74.

Thanks.

Here is a good overview of creating your own ROS repository.

1. At a minimum, send a message to the ros-users mailing list containing the repository address.

   Since git and hg repositories generally require separate source URLs for each stack, you may also wish to provide a .rosinstall file, allowing fine-grained control over your part of the index. (For svn repositories, that is often not needed.)

2. Wiki pages are not created automatically. You are free to create them before or after announcing the new repository.

   Please do create them, using the appropriate wiki templates. Some fields will not appear until the indexer finds your code. That's OK.

   Personally, I like to create package and stack pages before they appear in the repository. Then, I can easily tell when the indexer has visited them.

3. Binary ROS releases are not required, but I would recommend them. A good general open source practice is to "release early and often".

We are getting close to release our department ROS repository. We changed the SVN layout so now a trunk/ tags/ and branches/ is available on each stack. The install/update process is handle via rosinstall tool.

Questions are:

1. We need to provide to the ROS indexer a "whole repository" .rosinstall file, don't we?
2. Main repository wiki page should be documented before or after asking for inclusion? In the same line, is preferred to create wiki pages for each stack/pkg before or the indexer will create the page for us?
3. At this moment we haven't got any of our stacks released (using the ROS release tools). is it mandatory, recommended or not related at all before asking for inclusion in the list of repositories?

Thanks.

To answer your direct question. Velocities are instantaneous and therefore there is no such thing as Euler notation vs fixed frame notation. Also note that quaternions represent orientations and are not appropriate for velocities.

You can convert between all the different conventions, Euler*, Fixed axis etc. You will also find that EulerZYX(YPR) and FixedXYZ(RPY) is conveniently the same three components.

Trying to know what kind of coordinate system is using in twist message[1] (angular velocities) is not clear to us what does "free space" refers to.

¿Is it refering to EULER ZYX convention? ¿Or Fixed Frame?

In the second case, we can create a Quaterion[2] from EULER ZYX, and we would be interested to know if there is any method to extract the Fixed Frame coordinates from this quaternion.

Thanks a lot.

[1] http://www.ros.org/doc/api/geometry_m...
[2] http://www.continuousphysics.com/Bull...