Views
No views yet
⚠️ IMPORTANT: For Ubuntu version and GPU-related settings, please refer to the IsaacSim 5.1.0 Documentation. And the simulation currently only supports CPU devices.
1# This creates the Assets/ directory with all required simulation resources
2hf download lehome/asset_challenge --repo-type dataset --local-dir Assetshf download lehome/dataset_challenge_merged --repo-type dataset --local-dir Datasets/examplehf download lehome/dataset_challenge --repo-type dataset --local-dir Datasets/examplelerobot-train --config_path=configs/train_<policy>.yamlconfigs/train_act.yaml - ACTconfigs/train_dp.yaml - DPconfigs/train_smolvla.yaml - SmolVLAdataset.root to point to your datasetbatch_size, steps, save_freq, etc.output_dir to save models elsewhere📖 For detailed training instructions, feature selection guide, and configuration options, see our Training Guide.
1# Evaluate using LeRobot policy
2# Note: --policy_path and --dataset_root are required parameters for LeRobot policies, ready to run once the dataset and model checkpoints are prepared.
3python -m scripts.eval \
4 --policy_type lerobot \
5 --policy_path outputs/train/act_top_long/checkpoints/last/pretrained_model \
6 --garment_type "top_long" \
7 --dataset_root Datasets/example/top_long_merged \
8 --num_episodes 2 \
9 --enable_cameras \
10 --device cpu
11
12# Evaluate custom policy
13# Note: Participants can define their own model loading logic within the policy class. Provides flexibility for participants to implement specialized loading and inference logic.
14python -m scripts.eval \
15 --policy_type custom \
16 --garment_type "top_long" \
17 --num_episodes 5 \
18 --enable_cameras \
19 --device cpu| Parameter | Description | Default | Required For |
|---|---|---|---|
--policy_type | Policy type: lerobot, custom | lerobot | All |
--policy_path | Path to model checkpoint | - | All (passed as model_path for custom) |
--dataset_root | Dataset path (for metadata) | - | LeRobot only |
--garment_type | Type of garments: top_long, top_short, pant_long, pant_short, custom | top_long | All |
--num_episodes | Episodes per garment | 5 | All |
--max_steps | Max steps per episode | 600 | All |
--save_video | Save evaluation videos | All | |
--video_dir | Directory to save evaluation videos | outputs/eval_videos | --save_video |
--enable_cameras | Enable camera rendering | All | |
--device | Device for inference: only cpu | 'cpu' | All |
--headless | Used for evaluation without GUI | disabled | All |
--policy_path (model path) and --dataset_root (dataset path, used for loading metadata).--policy_path is passed to the policy constructor as model_path. Participants can define their own model loading logic (refer to scripts/eval_policy/example_participant_policy.py).Release set of garments. Under the directory Assets/objects/Challenge_Garment/Release, each garment category folder contains a corresponding text file listing the garment names (e.g., Top_Long/Top_Long.txt).--garment_type to top_long, top_short, pant_long, or pant_short to evaluate all garments within that category.Assets/objects/Challenge_Garment/Release/Release_test_list.txt to include only the garments you want to test, then run with --garment_type custom.📖 For detailed policy evaluation guide, see eval_guide.
Submission instructions will be available on the competition website.