{ "id": 1343, "title": "Can we get the skeleton's from the Kinect SDK as well?", "url": "/competitions/GestureChallenge/discussion/1343", "author_name": "", "post_date": "2012-02-08T12:44:23.387Z", "votes": null, "comment_count": 7, "views": 4258, "content": "

Sorry if this has already been asked.  Since the data is coming from a Kinect sensor, it would be really helpful to get the skeleton data in the video, which the SDK can't get based solely on the video.

\r\n

 

\r\n

Could this be included in the data, or no?

", "messages": [ { "id": "8483", "postDate": "02/08/2012 12:44:23", "content": "

Sorry if this has already been asked.  Since the data is coming from a Kinect sensor, it would be really helpful to get the skeleton data in the video, which the SDK can't get based solely on the video.

\r\n

 

\r\n

Could this be included in the data, or no?

", "rawMarkdown": "", "votes": null }, { "id": "8497", "postDate": "02/09/2012 06:38:29", "content": "

Yes, it was definitely asked before, and received an indefinite answer. Anyways at this point in the contest I don't think releasing this data would be fair to those contestants who have already invested a lot in developing their own body part recognition.

", "rawMarkdown": "", "votes": null }, { "id": "8559", "postDate": "02/14/2012 06:41:25", "content": "

I am sorry but we are struggling with this and do not have yet skeletons for you. The basic MS SDK tracker works only for full body skeletons and the seated tracker is not yet available through the SDK. We are looking into alternative solutions.

\r\n

In the mean time, we are annotating data by hand and will soon provide you with images with the position of head, shouders, elbows and hands that you can train with.

\r\n

Isabelle

", "rawMarkdown": "", "votes": null }, { "id": "8740", "postDate": "02/28/2012 18:54:50", "content": "

We just released body part annotations for the development set 01-20:

\r\n

https://sites.google.com/a/chalearn.org/gesturechallenge/data/data-annotations

\r\n

This should help people who want to train systems to automatically locate body parts.

\r\n

Note: we expect the participants to create an automatic system to locate body parts, not to manually labels them. This is why we do not provide human annotations for the validation data and will not provide any for the final evaluation data.

\r\n

[quote=Isabelle;8559]

\r\n

I am sorry but we are struggling with this and do not have yet skeletons for you. The basic MS SDK tracker works only for full body skeletons and the seated tracker is not yet available through the SDK. We are looking into alternative solutions.

\r\n

In the mean time, we are annotating data by hand and will soon provide you with images with the position of head, shouders, elbows and hands that you can train with.

\r\n

Isabelle

\r\n

[/quote]

", "rawMarkdown": "", "votes": null }, { "id": "8755", "postDate": "02/29/2012 16:12:12", "content": "

Dear Isabelle,

\r\n

In your last post you answered :"we expect the participants to create an automatic system to\r\nlocate body parts,"

\r\n

I had the impression that we are supposed to recognize gestures only. I'm sure finding the body parts would help the gesture recognition process but by putting this constraint on the expected solution would limit the freedom for developers to create body\r\n part free gesture recognition.

\r\n

I'd appreciate it if you could direct me to the place where locating body parts is defined as part of the goal of this competition.

", "rawMarkdown": "", "votes": null }, { "id": "8757", "postDate": "02/29/2012 16:22:41", "content": "

Hi shuky,

\r\n

    I guess what Isabelle meant is that "we don't provide human annotation for the validation/final data because we expect the participants to create an automatic system to locate body parts if participants' recognition algorithm requires the position\r\n of body part."

\r\n

   Therefore, locating body parts is not compulsory. (I believe for the moment, few (probably even no body) on the leaderboard took the approach of locating body part first.)

\r\n

   So the provided body part information is just an extra approach/info. participants can adopt/utilize.

\r\n

   Hope I am right ;)

\r\n

Cheers

", "rawMarkdown": "", "votes": null }, { "id": "8791", "postDate": "03/01/2012 21:24:53", "content": "

[quote=stevenwudi;8757]

\r\n

Hi shuky,

\r\n

    I guess what Isabelle meant is that "we don't provide human annotation for the validation/final data because we expect the participants to create an automatic system to locate body parts if participants' recognition algorithm requires the position\r\n of body part."

\r\n

   Therefore, locating body parts is not compulsory. (I believe for the moment, few (probably even no body) on the leaderboard took the approach of locating body part first.)

\r\n

   So the provided body part information is just an extra approach/info. participants can adopt/utilize.

\r\n

   Hope I am right ;)

\r\n

Cheers

\r\n

[/quote]

\r\n

Yes, this is correct, sorry for the confusion, I did not mean that you need to indentify the body parts. However, if you do, this must be done automatically in your final system, not with human interventions.

", "rawMarkdown": "", "votes": null }, { "id": "9200", "postDate": "03/10/2012 05:22:09", "content": "

I think, its hard to do that.

", "rawMarkdown": "", "votes": null } ], "comments": [ { "id": 8497, "author_name": "balazsgodeny", "author_url": "", "post_date": "02/09/2012 06:38:29", "content": "

Yes, it was definitely asked before, and received an indefinite answer. Anyways at this point in the contest I don't think releasing this data would be fair to those contestants who have already invested a lot in developing their own body part recognition.

", "votes": null, "replies": [] }, { "id": 8559, "author_name": "iguyon", "author_url": "", "post_date": "02/14/2012 06:41:25", "content": "

I am sorry but we are struggling with this and do not have yet skeletons for you. The basic MS SDK tracker works only for full body skeletons and the seated tracker is not yet available through the SDK. We are looking into alternative solutions.

\r\n

In the mean time, we are annotating data by hand and will soon provide you with images with the position of head, shouders, elbows and hands that you can train with.

\r\n

Isabelle

", "votes": null, "replies": [] }, { "id": 8740, "author_name": "iguyon", "author_url": "", "post_date": "02/28/2012 18:54:50", "content": "

We just released body part annotations for the development set 01-20:

\r\n

https://sites.google.com/a/chalearn.org/gesturechallenge/data/data-annotations

\r\n

This should help people who want to train systems to automatically locate body parts.

\r\n

Note: we expect the participants to create an automatic system to locate body parts, not to manually labels them. This is why we do not provide human annotations for the validation data and will not provide any for the final evaluation data.

\r\n

[quote=Isabelle;8559]

\r\n

I am sorry but we are struggling with this and do not have yet skeletons for you. The basic MS SDK tracker works only for full body skeletons and the seated tracker is not yet available through the SDK. We are looking into alternative solutions.

\r\n

In the mean time, we are annotating data by hand and will soon provide you with images with the position of head, shouders, elbows and hands that you can train with.

\r\n

Isabelle

\r\n

[/quote]

", "votes": null, "replies": [] }, { "id": 8755, "author_name": "shuky27958", "author_url": "", "post_date": "02/29/2012 16:12:12", "content": "

Dear Isabelle,

\r\n

In your last post you answered :"we expect the participants to create an automatic system to\r\nlocate body parts,"

\r\n

I had the impression that we are supposed to recognize gestures only. I'm sure finding the body parts would help the gesture recognition process but by putting this constraint on the expected solution would limit the freedom for developers to create body\r\n part free gesture recognition.

\r\n

I'd appreciate it if you could direct me to the place where locating body parts is defined as part of the goal of this competition.

", "votes": null, "replies": [] }, { "id": 8757, "author_name": "stevenwudi", "author_url": "", "post_date": "02/29/2012 16:22:41", "content": "

Hi shuky,

\r\n

    I guess what Isabelle meant is that "we don't provide human annotation for the validation/final data because we expect the participants to create an automatic system to locate body parts if participants' recognition algorithm requires the position\r\n of body part."

\r\n

   Therefore, locating body parts is not compulsory. (I believe for the moment, few (probably even no body) on the leaderboard took the approach of locating body part first.)

\r\n

   So the provided body part information is just an extra approach/info. participants can adopt/utilize.

\r\n

   Hope I am right ;)

\r\n

Cheers

", "votes": null, "replies": [] }, { "id": 8791, "author_name": "iguyon", "author_url": "", "post_date": "03/01/2012 21:24:53", "content": "

[quote=stevenwudi;8757]

\r\n

Hi shuky,

\r\n

    I guess what Isabelle meant is that "we don't provide human annotation for the validation/final data because we expect the participants to create an automatic system to locate body parts if participants' recognition algorithm requires the position\r\n of body part."

\r\n

   Therefore, locating body parts is not compulsory. (I believe for the moment, few (probably even no body) on the leaderboard took the approach of locating body part first.)

\r\n

   So the provided body part information is just an extra approach/info. participants can adopt/utilize.

\r\n

   Hope I am right ;)

\r\n

Cheers

\r\n

[/quote]

\r\n

Yes, this is correct, sorry for the confusion, I did not mean that you need to indentify the body parts. However, if you do, this must be done automatically in your final system, not with human interventions.

", "votes": null, "replies": [] }, { "id": 9200, "author_name": "hazelynb", "author_url": "", "post_date": "03/10/2012 05:22:09", "content": "

I think, its hard to do that.

", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "8483": "", "8497": "", "8559": "", "8740": "", "8755": "", "8757": "", "8791": "", "9200": "" }, "source": "meta" }