协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
environment-usage【开发与工程】Run, inspect, wrap, record, and smoke-test ManiSkill environments from the public package with CPU/GPU, observation/control/render, and demo guidance.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill when the task is about existing ManiSkill environments only: quickstart creation, observation/control/render selection, CPU vs GPU backend choice, wrapper composition, demo modules, and safe smoke tests from the public package.
Start here:
gym.make, BaseEnv, backend, and wrapper contracts.What this sub-skill covers:
gym.make / mani_skill.envs usage for public tasksBaseEnv runtime options and backend selectionCPUGymWrapper, ManiSkillVectorEnv, RecordEpisodeFlattenObservationWrapper, FlattenRGBDObservationWrapper, FlattenActionSpaceWrapperdemo_random_action, demo_robot, visual demo modules, demo_reset_distributionWhat it does not cover:
Routing:
Operating rules:
import mani_skill.envs followed by gym.make(...) for ordinary use. Reach for mani_skill.envs.sapien_env.BaseEnv only when you need constructor details, print_sim_details(), or low-level runtime inspection.obs_mode as the observation contract and control_mode as the action contract. If the user is unsure which mode to choose, inspect env.observation_space, env.action_space, and the bundled API notes before changing code.num_envs=1 for CPU smoke and num_envs>1 for GPU parallelization. Default sim_backend="auto" selects PhysX CPU for one env and PhysX CUDA for multiple envs; use explicit physx_cpu, physx_cuda, or physx_cuda:n when you need to pin the backend.render_backend="none" or None for headless smoke checks, and only ask for human, rgb_array, sensors, or all after display/Vulkan support is known.RecordEpisode should be last among ManiSkill wrappers, CPUGymWrapper is for single-env CPU runs only, and ManiSkillVectorEnv is the outer adapter for batched GPU envs that need Gymnasium vector semantics.