hongsukchoi / TCMR_RELEASE

Official Pytorch implementation of "Beyond Static Features for Temporally Consistent 3D Human Pose and Shape from a Video", CVPR 2021
MIT License
274 stars 39 forks source link

The 'scale' value for pre-processed data (*.pt files) #8

Open ZhimaoPeng opened 2 years ago

ZhimaoPeng commented 2 years ago

This project provides pre-processed data in a variety of configurations (e.g. 3dpw_train_occ_db.pt, 3dpw_train_db.pt). Do the 'scale' parameters in the 'extract_features' function have the same value when these files are generated? If not, what are their values?

    for i in tqdm(range(len(set(vid_segments)))):
        features = extract_features(model, None, np.array(vid_used_frames)[int(ids[i]):int(ids[i + 1])],
                                    vid_used_bbox[int(ids[i]):int(ids[i + 1])],
                                    kp_2d=np.array(vid_used_joints)[int(ids[i]):int(ids[i + 1])],
                                    dataset='spin', debug=False, **scale=1.2**)  # 1.0 for mpii3d_train_scale1_db.pt
        dataset['features'].append(features)
hongsukchoi commented 2 years ago

Hi, the scale values vary across the datasets, but do not change on the same dataset. That is, 3dpw_train_occ_db.pt and 3dpw_train_db.pt are generated using the same scale (1.2) as written in the released code files.

We applied different scales across the datasets, because the size of bounding box annotations were too different. For example, bounding boxes of one dataset appeared to be too tight, but these of another dataset appeared to be too loose. But the overall performance does not change much though,