moving ART messages to new art_msgs package

[Jack O'Quin]

We just created a new art_msgs package in the art_vehicle stack.

It's purpose is to hold all the ART-specific ROS message definitions.
We expect this to simplify package dependencies within the art_vehicle
stack, and reduce build overhead. It will also simplify building
experimental packages with alternate implementations of the same
interfaces.

As messages are migrated from their present packages to art_msgs,
users may experience problems when updating their build trees from the
Subversion repository. We will minimize this as much as possible, by
converting all known uses of each message when it migrates to the new
package. Sanbox uses are more likely to be overlooked in this process
than the art_vehicle stack in trunk.

Another source of possible confusion may occur when playing back data
from bag files captured before the transition. We are defining ROS bag
migration rules to handle this, but you may need to run rosbag fix if
your bag is out of date.

http://www.ros.org/wiki/rosbag/Commandline#fix

The first message has already been moved: applanix/GpsInfo is now
art_msgs/GpsInfo. The two known users of that message have already
been updated (revision 606).

We will try to get most of the messages moved quickly, one package at
a time. We want to minimize the transition time and avoid messages
getting updated in only one of two locations and bag files being
recorded with only some of the messages moved.

[Jack O'Quin]

I just committed revision 614 moving all the art_nav messages to
art_msgs. I also fixed all known uses of these messages. There were
none in sandbox that I could find.

Also, revision 613 fixed the references to GpsInfo in art_speech,
which I had missed when I first moved that message.

I'll probably do the art_nav messages next. The immediate intent is to
make it easier to experiment with different implementations of art_map
and art_nav.
--
 joq

[Jack O'Quin]

On Fri, Sep 24, 2010 at 10:13 AM, Jack O'Quin <jack....@gmail.com> wrote:

> I'll probably do the art_nav messages next. The immediate intent is to
> make it easier to experiment with different implementations of art_map
> and art_nav.

Those messages just moved.

There were a lot references in sandbox. I hope I found them all, but
it's hard to be sure with python code. Please update and check your
packages if there is any doubt.
--
 joq

[Michael Quinlan]

WIll do.

[Jack O'Quin]

I've finished moving all the art_vehicle messages to art_msgs.

All known users of the messages have been updated in svn (including
sandbox). If you have copies checked out from the repository, "svn up"
should fix most of the references, with local changes possibly needing
to be modified by hand.

I have updated the documentation, including a new ROS wiki page for
the art_msgs package:

http://www.ros.org/wiki/art_msgs

In addition, I moved the pilot node and its scripts out of the art_nav
package into a new art_pilot package of its own:

http://www.ros.org/wiki/art_pilot

That was easy to do after the global message move, a definite plus to
defining all our messages in a separate package.

With all these far-reaching changes, something is sure to have broken.
Let me know right away if you discover any new strange behavior.
--
 joq