Databases
StackOverflow2013
Postsdbo
POHuman pose estimation - efficient linking of body parts
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHuman pose estimation - efficient linking of body parts
    primarykey
    data
    text
    <p><strong>Problem's description:</strong> I am working at a project whose goal is to identify people's body parts in images (torso, head, left and right arms etc). The approach is based on finding parts of the human body (hypothesis) and then searching for the best pose configuration (= all the parts that really form a human body). The ideea is described better at this link <a href="http://www.di.ens.fr/willow/events/cvml2010/materials/INRIA_summer_school_2010_Andrew_human_pose.pdf">http://www.di.ens.fr/willow/events/cvml2010/materials/INRIA_summer_school_2010_Andrew_human_pose.pdf</a>. </p> <p>The hypothesis are obtained after running a detection algorithm (here I am using a classifier from machine learning field) for each body part separately. So, the type of each hypothesis is known. Also, each hypothesis has a location (x and y coordinates in the image) and an orientation.</p> <p>To determine the cost of linking two parts together, one can consider that each hypothesis of type head can be linked with each hypothesis of type torso (for example). But, a head hypothesis which is in the top right location of the image can not be linked (from a human point of view) with a torso hypothesis which is in the bottom left location of the image. I am trying to avoid these kinds of links based on the last statement and also due to the execution time. </p> <p><strong>Question:</strong> I am planing to reduce the searching space by considering a distance to the farthest hypothesis which can be a linking candidate. Which is the fastest way of solving this searching problem?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRobert Harvey
    1. USRaluca Pandaru
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHuman pose estimation - efficient linking of body parts
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHuman pose estimation - efficient linking of body parts
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHuman pose estimation - efficient linking of body parts
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you looking for the name of an algorithm which you can research further?
      singulars
      1. POHuman pose estimation - efficient linking of body parts
      1. USRobert Harvey
    2. CONot to answer your specific question, but just giving you a link to a related project that it may be useful (or not) to you :-) https://github.com/joaquimrocha/Skeltrack
      singulars
      1. POHuman pose estimation - efficient linking of body parts
      1. USNelson
    3. COYes, I need an algorithm or any other approach which performs better than the one of considering all the possible links between 2 hypothesis of different type.
      singulars
      1. POHuman pose estimation - efficient linking of body parts
      1. USRaluca Pandaru
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload