Adds Ray Workflow: Multiple Run Support, Distributed Hyperparameter Tuning, and Consistent Setup Across Local/Cloud #1301
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: glvov-bdai <[email protected]>
Signed-off-by: glvov-bdai <[email protected]>
Signed-off-by: glvov-bdai <[email protected]>
Signed-off-by: glvov-bdai <[email protected]>
kellyguo11
approved these changes
Dec 13, 2024
jsmith-bdai
approved these changes
Dec 13, 2024
Collaborator
jsmith-bdai
left a comment
jsmith-bdai
left a comment
There was a problem hiding this comment.
LGTM, thanks for adding!
|
Hi, have you tried using runtime environments to specify different pip packages, it always throw me an error saying failed to setup runtime environment because some packages could not be found.
but if I login to the node and executes python, then import the package, no error occurred Does this have something to do with the PYTHONPATH variable as in |
SevenFo
pushed a commit
to SevenFo/IsaacLab
that referenced
this pull request
May 19, 2025
…uning, and Consistent Setup Across Local/Cloud (isaac-sim#1301) This PR adds Ray support, which enables a lot of really cool stuff by leveraging the existing Hydra support, including but not limited to: - Several training runs at once in parallel or consecutively with minimal interaction - Using the same training setup everywhere (on cloud and local) with minimal overhead - Tuning hyperparameters - Tuning hyperparameters in parallel on multiple GPUs and/or multiple GPU Nodes - Simultaneously tuning model hyperparameters for different environments/agents - Resource Isolation
Collaborator
|
@sky-bro sorry for the late response please see #2632 (comment) in #2632 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds Ray support, which enables a lot of really cool stuff by leveraging the existing Hydra support, including but not limited to:
I know this PR seems huge, but most of the code diff is config files / argparser stuff / documentation / comments
My main project at BDAI is changing from RL to LfD effective November 1st, so I'm posting this PR as early as possible so I have as much time as possible to address comments.
It would be much appreciated if the NVIDIA folks can work with me to get this reviewed ASAP. I realize that this is a pretty big PR; but I also think that it adds a lot of cool functionality, and the merging process will go much smoother if I am able to devote time to this while at work. Thanks! ;)
Fixes # (issue#1190), (issue#1213)
Type of change
Screenshots
Checklist
pre-commitchecks with./isaaclab.sh --formatconfig/extension.tomlfileCONTRIBUTORS.mdor my name already exists there