-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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] No Preprocessors (part 2). #18468
[RLlib] No Preprocessors (part 2). #18468
Conversation
If
|
Another possible problem is the It seems that for dict observations and without any preprocessor, the input The ray/rllib/policy/torch_policy.py Line 938 in ae689ec
|
…deprecate_preprocessors_part_2
Thanks for your comments @yangysc ! These were invaluable. I added another test case covering single action calculations (and training) for all frameworks with the no-preprocessor setting and a complex observation space. Seems to be solid enough now to give this a go :) |
Very glad to help. Also, thanks for your excellent work. |
…deprecate_preprocessors_part_2 # Conflicts: # rllib/policy/policy.py
This PR was motivated in preparation for soon allowing individual observation components to be addressed by the trajectory view API, for example to enable frame-stacking for individual observation components within a complex observation space (Tuple|Dict). Also, soon soft-deprecating RLlib's Preprocessor API should increase transparency for the users and allow batched, model-based preprocessing of observations. Observations will arrive in the model exactly as they are returned by the env.
This is the second part of this (already merged) PR here:
#18367
dm_tree.flattened
and stored per-column in the collector: e.g.Why are these changes needed?
Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.