-
Notifications
You must be signed in to change notification settings - Fork 122
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
2d and 3d joints positions #131
Comments
You can follow the code in the forward_step to see how we calculate the 3D joints and project them to the image. |
Thank for your reply. This is the code i use to visualize the first 25 predicted 2d joints on the original frame. data = joblib.load('/home/markusc/Videos/panda_test/video/output2/webvid/medium/3/4dhumans/3_4dhumans.pkl') first_key = next(iter(data.keys())) image_path = '/home/markusc/Videos/panda_test/video/3/json_files/multiple/3/0_pose.png' img_height, img_width, _ = image.shape joints_2d_1 = joints_2d_1.reshape(-1, 2) joints_2d_1[:, 0] *= img_width print("Joints 2D 1 positions:") print("Joints 2D 2 positions:") plt.figure(figsize=(10, 10)) for idx, joint in enumerate(joints_2d_1): for idx, joint in enumerate(joints_2d_2): plt.title('2D Joints on Image - First Frame') |
@Marlod390 Hello, I would like to ask, for example, the following is the 3d_joints part of the information I extracted in the .pkl file, there are 45 lines in total, the last line looks like the origin, do you know how each line of information corresponds to each of the 44 joints? Do you know how each line of information corresponds to each of the 44 joints? For example, which joint is the first line of data? |
I tried to use the smpl parameter to calculate the position of 3d joints in order to compare with the data under the 3d_joints key, but found that the two data are different. At the same time, when I visualized the 2d joints on the original image, I also found that their positions did not match the actual ones. So I want to know how the 3d joints and 2d joints are calculated. Thanks in advance
The text was updated successfully, but these errors were encountered: