Skip to content

GTC DLI workflow docs#390

Merged
peterd-NV merged 18 commits intomainfrom
peterd/gtc_dli_docs
Feb 6, 2026
Merged

GTC DLI workflow docs#390
peterd-NV merged 18 commits intomainfrom
peterd/gtc_dli_docs

Conversation

@peterd-NV
Copy link
Collaborator

Summary

Add docs for GTC DLI course GR1 sequential static manipulation workflow

@xyao-nv xyao-nv force-pushed the peterd/gtc_dli_docs branch from 71f1e9a to dbe0bac Compare February 6, 2026 06:45
@xyao-nv xyao-nv marked this pull request as ready for review February 6, 2026 06:45
@xyao-nv
Copy link
Collaborator

xyao-nv commented Feb 6, 2026

I included all OSMO related cmds here. We can remove them later if you think it's too much. But at least for TME, they can follow the exact steps 1-5 to make sure at least closedloop works for each individual task. Then We can do the cross task training. Otherwise we will be suffering from not working trajectories. @alexmillane WDYT

@xyao-nv
Copy link
Collaborator

xyao-nv commented Feb 6, 2026

@peterd-NV in closedloop, the close door move rate metric is 0, which does not quite make sense to me. Can you take a look?

Copy link
Collaborator

@alexmillane alexmillane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! Thanks for doing this!

Comment on lines -19 to -22
.. todo::

Verifying Arena-GR00T on Blackwell architecture.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥳

* - **Interop**
- Isaac Lab Teleop, Isaac Lab Mimic
* - **Scene**
- Kitchen environment
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we better put Light Wheel Robocasa Kitchen to attribute LightWheel.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

* - **Scene**
- Kitchen environment
* - **Objects**
- Refrigerator (articulated object)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • object to place in refrigerator (rigid object)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Follow the instructions described on the CLI to mark subtask boundaries:

Left Arm:
1. **Pick & place completed:** Robot has completed the pick and place task
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps it's made clear in the CLI, but I'm wondering whether we should specify where the user should press the key here. Does this mean that you press the button once the door is closed? How does that interact with the reset.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding this to docs

Step 3: Validate Generated Data (Optional)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In order to validation the generated dataset, you can replay the generated data
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: in order to validate

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Comment on lines +100 to +105
To verify the generated LeRobot dataset, you first need to compute statistics information about the dataset.
This can be done by running the following command:

.. code-block:: bash

python submodules/Isaac-GR00T/gr00t/data/stats.py $DATASET_DIR/ranch_bottle_into_fridge/ranch_bottle_into_fridge_generated_100/lerobot gr1_joint
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I notice that the stats command alters some files. Does this have an affect on training? I wasn't running this when training things in Zurich. I'm wondering if that could have affected the performance?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stats.py added stats.json & rel_stats.json which I think it's used in dataloader for normalization. It's included in training but not replaying. I don't think it's a bug from stats ops itself, as it mostly copies from n1.5.


.. todo::
There is a bug in ISAAC-GR00T submodule gr00t/data/stats.py. PR is submmited and in review from Gear.
Usele gpu finetune command in the last step for now.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use finetune command?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

--dataset_path=$DATASET_DIR/arena_gr1_manipulation_dataset_generated/lerobot \
--output_dir=$MODELS_DIR \
--modality_config_path=isaaclab_arena_gr00t/embodiments/gr1/gr1_arms_only_data_config.py \
--global_batch_size=24 \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shall we go with 96? In my testing this results in a lower training error, and doesn't affect the training time.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch. It was trained with 96 but I forgot to update the doc here

python isaaclab_arena/evaluation/policy_runner.py \
--policy_type isaaclab_arena_gr00t.policy.gr00t_closedloop_policy.Gr00tClosedloopPolicy \
--policy_config_yaml_path isaaclab_arena_gr00t/policy/config/gr1_manip_ranch_bottle_gr00t_closedloop_config.yaml \
--num_steps 2000 \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To me it makes more sense that we run for a number of episodes. I'm adding that here: #383

What do you think?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's gonna be a great idea once you merge it. It looks like it has issue for recording metrics yesterday I ran it.

@xyao-nv xyao-nv force-pushed the peterd/gtc_dli_docs branch from 8d0cae1 to 103fb87 Compare February 6, 2026 18:49
@peterd-NV peterd-NV changed the title Draft: GTC DLI workflow docs GTC DLI workflow docs Feb 6, 2026
@peterd-NV peterd-NV merged commit e81d5e4 into main Feb 6, 2026
5 checks passed
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

Successfully merging this pull request may close these issues.

3 participants