-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RLlib] Examples folder cleanup: ModelV2 -> RLModule wrapper for migrating to new API stack (by config). #47427
[RLlib] Examples folder cleanup: ModelV2 -> RLModule wrapper for migrating to new API stack (by config). #47427
Conversation
…api_stack_migration_modelv2
…api_stack_migration_modelv2
…api_stack_migration_modelv2
…api_stack_migration_modelv2_from_config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
# API stack, the connector pipelines are responsible for doing this) -> We have | ||
# to remove, then re-add the time rank here to make ModelV2 work with the new | ||
# model-to-env pipelines. | ||
if state_in: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, now LSTM is possible :)
module_class=ModelV2ToRLModule, | ||
model_config_dict={ | ||
"policy_id": DEFAULT_POLICY_ID, | ||
"algo_config": config_old_stack, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we call this specifically "old_api_stack_algo_config"
to make clear that this is something only for this kind of purpose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good point! Will change ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
…api_stack_migration_modelv2_from_config
…ating to new API stack (by config). (ray-project#47427) Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
…ating to new API stack (by config). (ray-project#47427) Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
…ating to new API stack (by config). (ray-project#47427) Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
…ating to new API stack (by config). (ray-project#47427) Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
…ating to new API stack (by config). (ray-project#47427) Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
…ating to new API stack (by config). (ray-project#47427) Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
…ating to new API stack (by config). (ray-project#47427) Signed-off-by: ujjawal-khare <ujjawal.khare@dream11.com>
Adds example script and RLModule example class for easy ModelV2 -> RLModule migration to new API stack using an old API stack config.
Why are these changes needed?
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.