-
Notifications
You must be signed in to change notification settings - Fork 3k
Managed environments actions / observations descriptions #2730
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
Managed environments actions / observations descriptions #2730
Conversation
d07d009 to
0cbff3d
Compare
278696c to
60d9480
Compare
7e3b4c3 to
f859272
Compare
docs/source/policy_deployment/01_io_descriptors/io_descriptors_101.rst
Outdated
Show resolved
Hide resolved
|
|
||
| for group_name in self._group_obs_term_names: | ||
| group_data[group_name] = [] | ||
| # check ig group name is valid |
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.
| # check ig group name is valid | |
| # check if group name is valid |
| They always take the output tensor of the observation term as the first argument, and the descriptor as the second argument. | ||
| In the ``kwargs`` all the inputs of the observation term are provided. In addition to the ``on_inspect`` functions, the decorator | ||
| will also call run some functions in the background to collect the ``name``, the ``description``, and the ``full_path`` of the |
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.
| will also call run some functions in the background to collect the ``name``, the ``description``, and the ``full_path`` of the | |
| will also run some functions in the background to collect the ``name``, the ``description``, and the ``full_path`` of the |
| self._IO_descriptor.clip = None | ||
| return self._IO_descriptor | ||
| This is it! You should now be able to attach an IO descriptor to your own custom action terms which concludes this tutorial. |
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 as a user
… resolve function to get more data out of the term.
…ess. There are some caveats so we'll need good doc for it
…s. The new decorator can mock its signature, so we don't need that anymore
da653d5 to
3f6cdee
Compare
Test Results Summary1 690 tests 1 688 ✅ 57m 7s ⏱️ Results for commit 3f6cdee. |
Signed-off-by: ooctipus <zhengyuz@nvidia.com>
) # Description Experimental branch to generate observations and actions descriptions from managed environments. ## Type of change - New feature (non-breaking change which adds functionality) - This change requires a documentation update ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./isaaclab.sh --format` - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file - [x] I have added my name to the `CONTRIBUTORS.md` or my name already exists there --------- Signed-off-by: ooctipus <zhengyuz@nvidia.com> Co-authored-by: ooctipus <zhengyuz@nvidia.com>
Description
Experimental branch to generate observations and actions descriptions from managed environments.
Type of change
Checklist
pre-commitchecks with./isaaclab.sh --formatconfig/extension.tomlfileCONTRIBUTORS.mdor my name already exists there