enchance obs manager#18
Open
vybhav-ibr wants to merge 1 commit intojgillick:mainfrom
Open
Conversation
…ns as a seperate box, make obs_size calculation compatable with multi-dimensional arrays to support sensors
Owner
|
This PR is not ready for review:
Please avoid submitting incomplete PRs |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
modify observation manager to return each component of the observations as a separate box, make obs_size calculation compatible with multi-dimensional arrays to support sensors
makes the observation_space of the type collection.OrderedDict, This makes it possible for the policy to segregate the observations into its individual components(this is only possible with skrl, and skrl has a built in function for this called space_to_space), after the observation is divided into its constituents, different NNs can be used for the different observations, for instance the sensor observations like lidar, camera can be encoded into lower dimensional vectors using a CNN, which also helps preserve the spatial relation between the pixels/points. This is pretty much the only way sensor data can be used for RL, because using a fully connected network for the sensor observations will make the network way too large(a few million parameters).
here is an example of how this is used in SKRL code