Open SkalskiP opened 1 month ago
@SkalskiP do we want to filter "keypoint" group (ex: I have 7 detected humans I want to filter last 4 human keypoints and left other 3 humans based on filter) or just points itself because filtering points itself visually can break. Also in case of "shortages" should we fill values in something like negative values for prevents np.newaxis change requirement
@onuralpszr At which point would the newaxis cause issues? Would one of the dimensions collapse?
@onuralpszr At which point would the newaxis cause issues? Would one of the dimensions collapse?
My thinking was, Not using "newaxis" at all case and also curious about solution because we also talked about this in earlier how to manage because "filtering points" cause issue also key points can be incomplete (half body detection or semi visible cases)
I see your points. Filtering is ultimately a skeleton-level operation and is almost guaranteed to invalidate a [N x Skeleton]
array, if we want to continue keeping everything in a single block.
I see your points. Filtering is ultimately a skeleton-level operation and is almost guaranteed to invalidate a
[N x Skeleton]
array, if we want to continue keeping its keypoints in a single block.
To prevent that "we need" some sort of fillers because I need them all same but don't do anything, Because in picture It could be okay but in videos I can see problems like "occlusions" would be first.
@SkalskiP Shouldn't the class_id, confidence and class_name have the same shape as xy.shape[:2] and shouldn't they be arrays for keypoints detected for each object.
Bug
When trying to filter
KeyPoints
byconfidence
like this:I get this:
This is a symptom of a much broader problem - the
KeyPoints
object does not allow the skeleton of different objects to have different lengths.I managed to work around this problem like this, but it's a very hacky solution.
Additional