Extended Taskset for the Fetch Robot
Installation
you can do:
pip install gym-fetch
Alternatively, you can clone this repo and install under development mode:
git clone <this repo> cd <this repo> pip install -e .
Environments
We extend existing Fetch environments from gym, with 7 new manipulation tasks. The gym.Fetch environment are much better engineered than the sawyer environments that metaworld uses. They are faster to initialize, and have a small (50 step) maximum episode length, making these environments faster to train on.
We might or might not need to extend the max_episode_steps on more complex tasks.
Reach-v2 |
Push-v2 |
PickPlace-v2 |
Slide-v2 |
|---|---|---|---|
For Up-To-Date Environments
All documentations are maintained in the https://github.com/geyang/gym_fetch/blob/master/specs folder, where each task set is one markdown file.
original gym fetch tasks: https://github.com/geyang/gym_fetch/blob/master/specs/gym_fetch.md
``bin`` tasks: https://github.com/geyang/gym_fetch/blob/master/specs/bin.md
``bin_debug`` tasks: https://github.com/geyang/gym_fetch/blob/master/specs/bin_debug.md
``box`` tasks: https://github.com/geyang/gym_fetch/blob/master/specs/box.md
``drawer`` tasks: https://github.com/geyang/gym_fetch/blob/master/specs/drawer.md
The multi-task environments are still under development. They are located under
fetch
├── tasksets
├── box_block.md
├── box_block.py
Primitive Single Task Environments
The tasks involve a single primitive action such as open/closing a box, or a drawer. They do not additionally involve placing an object into the opened drawer or box. We include bin picking and placing because the bin does not require additional actions to open.
Box-open-v0 |
Box-close-v0 |
Bin-pick-v0 |
Bin-place-v0 |
|---|---|---|---|
Drawer-open-v0 |
Drawer-close-v0 |
||
Intermediate Task
These tasks additionally require placing the object inside an open drawer or box. We include the Bin-picking environment for completeness.
Name |
Status |
|---|---|
Bin-pick-v2 |
✅ done |
Bin-place-v2 |
✅ done |
Box-place-v2 |
✅ done |
Box-pick-v2 |
✅ done |
Drawer-place-v2 |
✅ done |
Drawer-pick-v2 |
✅ done |
Bin-pick-v0 |
Bin-place-v0 |
Box-pick-v0 |
Box-place-v0 |
|---|---|---|---|
Drawer-pick-v0 |
Drawer-place-v0 |
||
Multi-task Environments
These environments require significantly more memory due to the increasing complexity of contact detection and collision dynamics. These are also slower to run.
Name |
Render |
|---|---|
BoxBin-v2 |
✅ done |
DrawerBin-v2 |
✅ done |
BoxBinDrawer-v2 |
✅ done |
BoxBin-v0 |
DrawerBin-v0 |
BoxBinDrawer-v0 |
|---|---|---|
Metadata
Release files for gym-fetch 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gym_fetch-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for gym_fetch-0.2.2-py3-none-any.whl |
Release files / gym_fetch-0.2.2-py3-none-any.whl
| Download URL | gym_fetch-0.2.2-py3-none-any.whl |
|---|---|
| Size | 744.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b743681bbc883f7e94fa45fad1eed5cc75f4b91092fe93043c20c458dc710f05
|
|
BLAKE2b-256 checksum How to use checksums |
86618182399b69ee04877bfe21311b3307eb186aee84641cb909119cb6b4d024
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.8
|
Security for gym-fetch 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.