You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[major fix]update the code base to avoid isaacsim shutdown issue, add auto-skill scripts, update task import order issue, skip task scanning if not using (#761)
`make_vec` provides a standardized helper that wraps task instantiation in a **Gym‑compatible API**. It is the recommended entry point for creating environments.
88
88
89
89
```python
90
-
import metasim# triggering the registration of tasks with Gymnasium
90
+
import metasim
91
91
from gymnasium import make_vec
92
92
93
+
metasim.register_gym_envs() # register RoboVerse/* with Gymnasium before make_vec
94
+
93
95
env = make_vec(
94
96
env_id, # e.g., "example.my_task"
95
97
num_envs=args.num_envs,
@@ -109,15 +111,17 @@ env = make_vec(
109
111
110
112
---
111
113
112
-
## 4. Task Registration & Auto‑Import
114
+
## 4. Task Registration & Discovery
113
115
114
-
### 4.1 Auto‑import paths
116
+
### 4.1 Discovery paths
115
117
116
-
Task modules under the following directories are **auto‑imported and registered** at runtime:
118
+
Task modules under these packages are found when discovery runs (not on every `import metasim`):
117
119
118
120
*`metasim/example/example_pack/tasks`
119
121
*`roboverse_pack/tasks`
120
122
123
+
Discovery is triggered by `get_task_class`, `list_tasks`, or `metasim.register_gym_envs()`.
124
+
121
125
> For new project tasks, place modules under **`roboverse_pack/tasks`**.
0 commit comments