From ros-users-bounces@code.ros.org  Tue Mar 22 16:17:50 2011
Return-Path: <ros-users-bounces@code.ros.org>
X-Original-To: www-data@code.ros.org
Delivered-To: www-data@code.ros.org
Received: from pub5.willowgarage.com (localhost [127.0.0.1])
	by pub5.willowgarage.com (Postfix) with ESMTP id C73032EC687;
	Tue, 22 Mar 2011 16:17:50 -0700 (PDT)
X-Original-To: ros-users@code.ros.org
Delivered-To: ros-users@code.ros.org
Received: from mail-fx0-f46.google.com (mail-fx0-f46.google.com
	[209.85.161.46])
	by pub5.willowgarage.com (Postfix) with ESMTPS id 3FDC525C7A7
	for <ros-users@code.ros.org>; Tue, 22 Mar 2011 16:17:49 -0700 (PDT)
Received: by fxm17 with SMTP id 17so8385187fxm.5
	for <ros-users@code.ros.org>; Tue, 22 Mar 2011 16:17:47 -0700 (PDT)
Received: by 10.223.98.8 with SMTP id o8mr2368354fan.22.1300835867134; Tue, 22
	Mar 2011 16:17:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.101.208 with HTTP; Tue, 22 Mar 2011 16:17:27 -0700 (PDT)
From: "David Lu!!" <davidlu@wustl.edu>
Date: Tue, 22 Mar 2011 18:17:27 -0500
X-Google-Sender-Auth: ZXBWMJlqckWJRUMNRKtxJ4mH5h0
Message-ID: <AANLkTikQZsiEVV0m0FR8gEhwdQMeRzshQqr0LaLx9BJq@mail.gmail.com>
To: ROS Users <ros-users@code.ros.org>
Subject: [ros-users] Skeletons
X-BeenThere: ros-users@code.ros.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: User discussions <ros-users@code.ros.org>
List-Id: User discussions <ros-users.code.ros.org>
List-Unsubscribe: <https://code.ros.org/mailman/listinfo/ros-users>,
	<mailto:ros-users-request@code.ros.org?subject=unsubscribe>
List-Archive: </lurker/list/ros-users.html>
List-Post: <mailto:ros-users@code.ros.org>
List-Help: <mailto:ros-users-request@code.ros.org?subject=help>
List-Subscribe: <https://code.ros.org/mailman/listinfo/ros-users>,
	<mailto:ros-users-request@code.ros.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1814222427052781499=="
Mime-version: 1.0
Sender: ros-users-bounces@code.ros.org
Errors-To: ros-users-bounces@code.ros.org

--===============1814222427052781499==
Content-Type: multipart/alternative; boundary=0015174beb62c58a83049f1a733a

--0015174beb62c58a83049f1a733a
Content-Type: text/plain; charset=ISO-8859-1

Hey Ros-users-

Has there been any talk of creating a standardized Skeleton message? Right
now, it seems like the openni_tracker package just publishes transforms. It
seems like if the Kinect does skeleton tracking, there should be a skeleton
message.

I know pi_tracker has its own Skeleton message, which looks like it might
fit the bill, although I don't think it defines which parts are connected
(hip bone is connected to the thigh bone).
http://www.ros.org/doc/api/pi_tracker/html/msg/Skeleton.html

It might be good to have for not only the Kinect, but for other motion
capture rigs (Vicon and the like).

Are there any other similar message out there?

-David!!

--0015174beb62c58a83049f1a733a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hey Ros-users-<div><br></div><div>Has there been any talk of creating a sta=
ndardized Skeleton message? Right now, it seems like the openni_tracker pac=
kage just publishes transforms. It seems like if the Kinect does skeleton t=
racking, there should be a skeleton message.=A0</div>

<div><br></div><div>I know pi_tracker has its own Skeleton message, which l=
ooks like it might fit the bill, although I don&#39;t think it defines whic=
h parts are connected (hip bone is connected to the thigh bone).=A0</div>

<div><meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf-=
8"><a href=3D"http://www.ros.org/doc/api/pi_tracker/html/msg/Skeleton.html"=
>http://www.ros.org/doc/api/pi_tracker/html/msg/Skeleton.html</a></div><div=
><br>

</div><div>It might be good to have for not only the Kinect, but for other =
motion capture rigs (Vicon and the like).=A0</div><div><br></div><div>Are t=
here any other similar message out there?</div><div><br></div><div>-David!!=
</div>


--0015174beb62c58a83049f1a733a--

--===============1814222427052781499==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users

--===============1814222427052781499==--

