Skip to content

[BUG] preprocess code produce the different shape retargetting results #10

@Kashu7100

Description

@Kashu7100

The resulting files from retargetting commands (below) have different dimensions from the provided files.
Specifically, those generated has temporal length of 200 but the one provided in assets has 600+.
When I run the RL with those generated, the First dim size mismatch occurs in load_demo in RewardModule (because it loads the 200 length demo and slice it from 30).
With modification on the frame_start and frame_end in the load_contact_retarget_data (frame_start=frame_start, frame_end=frame_end -> frame_start=0, frame_end=len(demo_data["obj_pos"])), I could load the generated files but the RL results are much worse (and eval trials were unsuccessful unlike the policy trained with provided one).

Image
  • retargeter_results/${HAND}/${OBJ}_use_01_vector.npy
  • retargeted/${HAND}/s01/${OBJ}_use_01_vector_para.pt
  • contact_retarget/${HAND}/s01/${OBJ}_use_01.npy
OBJ=box
HAND=inspire
CLIP=box-30-230

python dexmachina/retargeting/parallel_retarget.py --clip $CLIP --hand ${HAND} --control_steps 2000 --save_name para --save -ow

FNAME=dexmachina/assets/arctic/processed/s01/${OBJ}_use_01.npy
python dexmachina/retargeting/map_contacts.py --hand $HAND --load_fname $FNAME 

Could you double check on those preprocess codes as well as arguments to the script so that I can reproduce the retargeting results (.npy and _para.pt) provided?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions