[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F8Z6H6VFK2W3DTZSHSNFDF":3,"skill-same:01M7F8Z6H6VFK2W3DTZSHSNFDF":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7F8Z6H6VFK2W3DTZSHSNFDF","simulation-setup",null,"Prepare and diagnose the ROS Noetic, Gazebo, catkin, launch, and Velodyne runtime used by DRL-robot-navigation without claiming unavailable native simulator verification.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fdrl-robot-navigation\u002Fsub-skills\u002Fsimulation-setup\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: simulation-setup\ndescription: \"Prepare and diagnose the ROS Noetic, Gazebo, catkin, launch, and\n  Velodyne runtime used by DRL-robot-navigation without claiming unavailable\n  native simulator verification.\"\ndisable-model-invocation: true\nmetadata:\n  disco-role: operating\nlicense: MIT\n---\n\n# Simulation setup\n\nUse this skill when a Researcher must make the ROS\u002FGazebo simulator available, understand\nhow the repository starts it, or diagnose a startup, package, resource, sensor, display, or\nprocess-lifecycle failure. This is an operating guide, not a training or reward guide.\n\n## Contract and limits\n\n- Target baseline: ROS Noetic on Ubuntu 20.04, with the Python\u002FPyTorch versions stated by\n'the project README. The simulator also depends on Gazebo ROS packages and a catkin toolchain.\n- The normal build is `catkin_make_isolated` from the workspace root. Source the ROS and\nworkspace setup files in every shell that uses `roslaunch`, `rospack`, or Gazebo.\n- The composite launch is the repository's `TD3\u002Fassets\u002Fmulti_robot_scenario.launch`; its\nresolved package launch files and sensor xacro are summarized in\n`references\u002Flaunch-topology.md`.\n- Full ROS\u002FGazebo\u002Froscore\u002Froslaunch\u002Fcatkin native verification was unavailable in the\nextraction environment. The bundled checker is static and safe: it never starts ROS,\nGazebo, Docker, xacro, or a long-lived process. Do not report native runtime success from\nits output.\n- Do not silently change launch files, substitute a 2-D laser for the Velodyne topic, or\nclaim that a headless Docker build is a verified workaround. Route navigation state,\nreward, TD3, and policy behavior to the sibling skills.\n\n## First response to a setup request\n\n1. Identify the execution boundary: a supported Ubuntu\u002FROS host, a ROS Noetic container,\n   or a host without ROS. Ask for a supported provisioned environment when `\u002Fopt\u002Fros\u002Fnoetic`\n   and the ROS commands are absent; do not fake them with pip packages.\n2. Run the bundled, read-only check from this skill directory:\n\n   ```bash\n   python3 scripts\u002Fcheck_ros_prerequisites.py --workspace \u003Ccatkin-workspace>\n   ```\n\n   Add `--json` for machine-readable diagnostics. It checks command presence, the ROS\n   prefix, workspace paths, and environment values; it does not launch anything.\n3. In a shell intended for the run, source the installed ROS setup and then the workspace\n   setup (the latter is produced only after a successful build):\n\n   ```bash\n   source \u002Fopt\u002Fros\u002Fnoetic\u002Fsetup.bash\n   cd \u003Ccatkin-workspace>\n   source devel_isolated\u002Fsetup.bash\n   ```\n\n   Keep `ROS_MASTER_URI`, `ROS_HOSTNAME`, and the simulator port consistent across every\n   shell. If the ROS prefix is missing, follow the safe path in `references\u002Ftroubleshooting.md`.\n4. Configure the resource path before Gazebo resolves `TD3.world` and mesh assets. Preserve\n   any existing entries rather than replacing them:\n\n   ```bash\n   export ROS_HOSTNAME=localhost\n   export ROS_MASTER_URI=http:\u002F\u002Flocalhost:11311\n   export ROS_PORT_SIM=11311\n   export GAZEBO_RESOURCE_PATH=\u003Ccatkin-workspace>\u002Fsrc\u002Fmulti_robot_scenario\u002Flaunch${GAZEBO_RESOURCE_PATH:+:$GAZEBO_RESOURCE_PATH}\n   ```\n\n5. Build manually from the workspace root when the prerequisites are present:\n\n   ```bash\n   catkin_make_isolated\n   ```\n\n   Review the first package or dependency failure; do not paper over it by copying\n   generated `devel*` files from another machine.\n\n## Startup topology and expected contracts\n\n- `multi_robot_scenario.launch` includes `empty_world.launch`, which starts `gzserver`\n  with `TD3.world`, then includes `pioneer3dx.gazebo.launch` for model `r1` at the origin.\n- The robot launch expands `pioneer3dx.xacro`, spawns `r1`, and starts robot\u002Fjoint state\n  publishers. The xacro wires the diff-drive plugin (`\u002Fr1\u002Fcmd_vel`, `\u002Fr1\u002Fodom`) and the\n  CPU Velodyne VLP-16 (`\u002Fvelodyne_points`).\n- The composite also starts RViz unconditionally using `pioneer3dx.rviz`; its `gui` arg\n  does not disable that RViz node. A display-less Docker shell therefore needs an\n  explicitly headless-safe launch choice; the documented Docker path is not native\n  verification and is not automatically repaired by this skill.\n- Confirm package resolution before debugging Gazebo:\n\n  ```bash\n  rospack find multi_robot_scenario\n  rospack find velodyne_description\n  rospack find velodyne_gazebo_plugins\n  ```\n\n  The standalone `pioneer3dx.urdf.launch` contains a stale `multi_robot_tutorial` package\n  reference and is not the composite path. Prefer the composite topology unless a user\n  intentionally maintains a corrected standalone launch.\n\n## Velodyne readiness\n\nThe robot's VLP-16 macro uses CPU ray mode (`gpu:=false`), 16 vertical lasers, 360\nhorizontal samples, 10 Hz, horizontal angles `[-1.57, 1.57]`, and topic `\u002Fvelodyne_points`.\nThe plugin emits `sensor_msgs\u002FPointCloud2` with `x`, `y`, `z`, `intensity`, `ring`, and\n`time` fields. The environment subscribes to the absolute topic and therefore will not\nreceive data from an arbitrary remapped or 2-D laser topic. The plugin activates sensor\nproduction when it has a subscriber, so check the subscriber and topic before treating an\nempty cloud as a Gazebo failure. See `references\u002Fvelodyne-sensor.md` for a diagnostic order.\n\n## Headless\u002Fcontainer guidance\n\nThe README documents `docker build -t drl_noetic .`, an interactive `docker run`, and\nstarting training inside the container. The Dockerfile sets software rendering,\n`GAZEBO_HEADLESS_RENDERING=1`, an empty `DISPLAY`, ROS localhost values, and a launch\nresource path, then clones a named remote branch and builds with `catkin_make`. Treat this\nas a reproducible starting point only: it performs a network-dependent build, follows a\nbranch rather than this snapshot, has no persistence with `--rm`, and the composite still\ncontains an unconditional RViz node. Read `references\u002Fcontainer.md` before using it.\nDo not add an automatic Docker build\u002Frun helper or an infinite training\u002Flaunch script.\n\n## Handoff and evidence\n\nReport which checks passed, which are missing, and whether the result is host or container\nbased. Keep these separate:\n\n- static prerequisites and package\u002Fpath evidence;\n- successful catkin build and generated setup file;\n- actual roscore\u002Froslaunch\u002FGazebo startup;\n- live `\u002Fvelodyne_points`, `\u002Fr1\u002Fodom`, and Gazebo service evidence.\n\nThe current source snapshot supports the first category and documents the others, but the\navailable environment did not support the final three. Use the troubleshooting reference\nfor xacro\u002Fpackage errors, missing resources, Gazebo\u002FRViz display problems, plugin loading,\nand orderly shutdown. If the request is about observation binning, reward, action scaling,\nor TD3 parameters, hand it to the corresponding sibling sub-skill instead of expanding\nthis one.\n","# Simulation setup\n\nUse this skill when a Researcher must make the ROS\u002FGazebo simulator available, understand\nhow the repository starts it, or diagnose a startup, package, resource, sensor, display, or\nprocess-lifecycle failure. This is an operating guide, not a training or reward guide.\n\n## Contract and limits\n\n- Target baseline: ROS Noetic on Ubuntu 20.04, with the Python\u002FPyTorch versions stated by\n'the project README. The simulator also depends on Gazebo ROS packages and a catkin toolchain.\n- The normal build is `catkin_make_isolated` from the workspace root. Source the ROS and\nworkspace setup files in every shell that uses `roslaunch`, `rospack`, or Gazebo.\n- The composite launch is the repository's `TD3\u002Fassets\u002Fmulti_robot_scenario.launch`; its\nresolved package launch files and sensor xacro are summarized in\n`references\u002Flaunch-topology.md`.\n- Full ROS\u002FGazebo\u002Froscore\u002Froslaunch\u002Fcatkin native verification was unavailable in the\nextraction environment. The bundled checker is static and safe: it never starts ROS,\nGazebo, Docker, xacro, or a long-lived process. Do not report native runtime success from\nits output.\n- Do not silently change launch files, substitute a 2-D laser for the Velodyne topic, or\nclaim that a headless Docker build is a verified workaround. Route navigation state,\nreward, TD3, and policy behavior to the sibling skills.\n\n## First response to a setup request\n\n1. Identify the execution boundary: a supported Ubuntu\u002FROS host, a ROS Noetic container,\n   or a host without ROS. Ask for a supported provisioned environment when `\u002Fopt\u002Fros\u002Fnoetic`\n   and the ROS commands are absent; do not fake them with pip packages.\n2. Run the bundled, read-only check from this skill directory:\n\n   ```bash\n   python3 scripts\u002Fcheck_ros_prerequisites.py --workspace \u003Ccatkin-workspace>\n   ```\n\n   Add `--json` for machine-readable diagnostics. It checks command presence, the ROS\n   prefix, workspace paths, and environment values; it does not launch anything.\n3. In a shell intended for the run, source the installed ROS setup and then the workspace\n   setup (the latter is produced only after a successful build):\n\n   ```bash\n   source \u002Fopt\u002Fros\u002Fnoetic\u002Fsetup.bash\n   cd \u003Ccatkin-workspace>\n   source devel_isolated\u002Fsetup.bash\n   ```\n\n   Keep `ROS_MASTER_URI`, `ROS_HOSTNAME`, and the simulator port consistent across every\n   shell. If the ROS prefix is missing, follow the safe path in `references\u002Ftroubleshooting.md`.\n4. Configure the resource path before Gazebo resolves `TD3.world` and mesh assets. Preserve\n   any existing entries rather than replacing them:\n\n   ```bash\n   export ROS_HOSTNAME=localhost\n   export ROS_MASTER_URI=http:\u002F\u002Flocalhost:11311\n   export ROS_PORT_SIM=11311\n   export GAZEBO_RESOURCE_PATH=\u003Ccatkin-workspace>\u002Fsrc\u002Fmulti_robot_scenario\u002Flaunch${GAZEBO_RESOURCE_PATH:+:$GAZEBO_RESOURCE_PATH}\n   ```\n\n5. Build manually from the workspace root when the prerequisites are present:\n\n   ```bash\n   catkin_make_isolated\n   ```\n\n   Review the first package or dependency failure; do not paper over it by copying\n   generated `devel*` files from another machine.\n\n## Startup topology and expected contracts\n\n- `multi_robot_scenario.launch` includes `empty_world.launch`, which starts `gzserver`\n  with `TD3.world`, then includes `pioneer3dx.gazebo.launch` for model `r1` at the origin.\n- The robot launch expands `pioneer3dx.xacro`, spawns `r1`, and starts robot\u002Fjoint state\n  publishers. The xacro wires the diff-drive plugin (`\u002Fr1\u002Fcmd_vel`, `\u002Fr1\u002Fodom`) and the\n  CPU Velodyne VLP-16 (`\u002Fvelodyne_points`).\n- The composite also starts RViz unconditionally using `pioneer3dx.rviz`; its `gui` arg\n  does not disable that RViz node. A display-less Docker shell therefore needs an\n  explicitly headless-safe launch choice; the documented Docker path is not native\n  verification and is not automatically repaired by this skill.\n- Confirm package resolution before debugging Gazebo:\n\n  ```bash\n  rospack find multi_robot_scenario\n  rospack find velodyne_description\n  rospack find velodyne_gazebo_plugins\n  ```\n\n  The standalone `pioneer3dx.urdf.launch` contains a stale `multi_robot_tutorial` package\n  reference and is not the composite path. Prefer the composite topology unless a user\n  intentionally maintains a corrected standalone launch.\n\n## Velodyne readiness\n\nThe robot's VLP-16 macro uses CPU ray mode (`gpu:=false`), 16 vertical lasers, 360\nhorizontal samples, 10 Hz, horizontal angles `[-1.57, 1.57]`, and topic `\u002Fvelodyne_points`.\nThe plugin emits `sensor_msgs\u002FPointCloud2` with `x`, `y`, `z`, `intensity`, `ring`, and\n`time` fields. The environment subscribes to the absolute topic and therefore will not\nreceive data from an arbitrary remapped or 2-D laser topic. The plugin activates sensor\nproduction when it has a subscriber, so check the subscriber and topic before treating an\nempty cloud as a Gazebo failure. See `references\u002Fvelodyne-sensor.md` for a diagnostic order.\n\n## Headless\u002Fcontainer guidance\n\nThe README documents `docker build -t drl_noetic .`, an interactive `docker run`, and\nstarting training inside the container. The Dockerfile sets software rendering,\n`GAZEBO_HEADLESS_RENDERING=1`, an empty `DISPLAY`, ROS localhost values, and a launch\nresource path, then clones a named remote branch and builds with `catkin_make`. Treat this\nas a reproducible starting point only: it performs a network-dependent build, follows a\nbranch rather than this snapshot, has no persistence with `--rm`, and the composite still\ncontains an unconditional RViz node. Read `references\u002Fcontainer.md` before using it.\nDo not add an automatic Docker build\u002Frun helper or an infinite training\u002Flaunch script.\n\n## Handoff and evidence\n\nReport which checks passed, which are missing, and whether the result is host or container\nbased. Keep these separate:\n\n- static prerequisites and package\u002Fpath evidence;\n- successful catkin build and generated setup file;\n- actual roscore\u002Froslaunch\u002FGazebo startup;\n- live `\u002Fvelodyne_points`, `\u002Fr1\u002Fodom`, and Gazebo service evidence.\n\nThe current source snapshot supports the first category and documents the others, but the\navailable environment did not support the final three. Use the troubleshooting reference\nfor xacro\u002Fpackage errors, missing resources, Gazebo\u002FRViz display problems, plugin loading,\nand orderly shutdown. If the request is about observation binning, reward, action scaling,\nor TD3 parameters, hand it to the corresponding sibling sub-skill instead of expanding\nthis one.\n",{"name":5,"license":15,"metadata":24,"description":7,"disable-model-invocation":26},{"disco-role":25},"operating",true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fdrl-robot-navigation\u002Fsub-skills\u002Fsimulation-setup",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill simulation-setup",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill simulation-setup",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill simulation-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fdrl-robot-navigation\u002Fsub-skills\u002Fsimulation-setup\u002FSKILL.md",[48,54,58,62],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcontainer.md","REFERENCE","参考文档",4076,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fdrl-robot-navigation\u002Fsub-skills\u002Fsimulation-setup\u002Freferences\u002Fcontainer.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Flaunch-topology.md",5325,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fdrl-robot-navigation\u002Fsub-skills\u002Fsimulation-setup\u002Freferences\u002Flaunch-topology.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ftroubleshooting.md",8298,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fdrl-robot-navigation\u002Fsub-skills\u002Fsimulation-setup\u002Freferences\u002Ftroubleshooting.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fvelodyne-sensor.md",4613,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fdrl-robot-navigation\u002Fsub-skills\u002Fsimulation-setup\u002Freferences\u002Fvelodyne-sensor.md",[67,74,79,86,93,100],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":75,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]