Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is action_name required for the dataset? #21

Open
cacticaxas opened this issue May 8, 2023 · 3 comments
Open

Is action_name required for the dataset? #21

cacticaxas opened this issue May 8, 2023 · 3 comments

Comments

@cacticaxas
Copy link

Hello,

I'm trying to implement a dataset that does not have any action_name. In the documentation provided (https://github.com/cure-lab/DeciWatch/blob/main/doc/data.md) it states that the data should be given in the following format of [action_name]/[sequence_name]/[image_id]. Can the action_name be omitted or must it be provided for my custom dataset?

@juxuan27
Copy link
Contributor

juxuan27 commented May 8, 2023

You can simply omit it but this may cause some change of the code in visualization part (if you use the visualization of Human3.6M). But if you simply want to train and evaluate, this will not cause any problem.

@cacticaxas
Copy link
Author

I see. Thank you for the explanation. I have, however, a follow-up question.

In my custom dataset, I have more than one pose annotations for each person in the frame. However, I noticed in the .npz files format that was provided, only one annotation is assigned to each frame eventhough there is more than one person in the frame. In this case I am referring to the "joints_2d" field in Sub-JHMDB dataset, where the shape of each sequence is the corresponding_sequence_length*(15*2).

Is it possible to include more than one annotations per frame for multi-person human pose estimation?

@juxuan27
Copy link
Contributor

Sorry for the late reply. You may change the shape to corresponding_sequence_length*(30*2), where the 30 is the concat of 2 15 (in case you have 2 person). However, you may need some effort to change the visualization code if you do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants