Added pros and cons

Author: AkshitRaizada

wiki/robotics-project-guide/choose-a-sim.md

@@ -14,20 +14,30 @@ By the end of this section, you will understand:
 - How to determine the type of simulator you require based on your project's specifications.  
 - The pros and cons of various simulators tailored for robotics, machine learning/reinforcement learning, and visualization.  
 
-## Why Are Simulators Important in Robotics Projects?
+## Should You Simulate? Why Are Simulators Important in Robotics Projects?
+
+Say that you want to deploy our quadruped robot `Tod` in a shopping mall. You already developed the software that will be running on `Tod` and integrated the peripheral hardware such as a camera for vision. But you're not sure whether everything will work nicely together when you actually put it into use. Will the perception work as intended and recognize obstacles? Will the planner output an optimal path based on the perceived obstacles and goal points? Will the controller move the robot as intended along the path given by the planner?
+
+It's hard to tell, and you most certainly do not want to test this out for the first time in a crowded shopping mall! Here, a simulator can help. 
+When developing a software component for your robot, you can use readily available open-source simulators to test out how your software might work in the real world. You can simulate the robot's behavior, such as the sensor measurements and controller gains, and also the environment, such as friction, gravity, wind, etc. Once you simulate the robot in this "fake world", you may detect some problems with your current software stack and choose to improve them. You can keep iterating this until you get the desirable performance. 
 
 Simulators play a crucial role in robotics for several reasons:
 
+### 1. Logistics
 - **Cost Efficiency**: Developing and testing in a virtual environment reduces the need for expensive hardware prototypes.  
 - **Safety**: Allows for the testing of potentially dangerous scenarios without risk to humans or equipment.  
-- **Accelerated Development**: Facilitates rapid prototyping and debugging, enabling quicker iterations.  
-- **Accessibility**: Provides a platform for learning and experimentation without the necessity of physical robots.  
-- **Reproducibility**: Ensures consistent testing conditions, which is essential for algorithm validation.
+- **Accessibility**: Facilitates rapid prototyping and debugging, enabling quicker iterations. Allows team members to develop and test code in parallel. 
 
-Say that you want to deploy our quadruped robot `Tod` in a shopping mall. You already developed the software that will be running on `Tod` and integrated the peripheral hardware such as a camera for vision. But you're not sure whether everything will work nicely together when you actually put it into use. Will the perception work as intended and recognize obstacles? Will the planner output an optimal path based on the perceived obstacles and goal points? Will the controller move the robot as intended along the path given by the planner?
+### 2. Algorithmic Validation and Data Generation
+- **Reproducibility & Ground Truth**: Ensures deterministic testing conditions. Simulators provide perfect state estimation, which is invaluable for isolating whether an issue is a sensor error or a controller error.
+- **Domain Randomization for Robustness**: Can procedurally vary physical constraints (friction, mass), visual parameters (lighting, textures) and locations of items in an environment to force the model to learn a more robust policy.
+- **Exploration**: Simulators allow you to safely test specific situations like sensor failures, extreme weather conditions or complex human-robot/multi-robot interactions.
+- **Synthetic Data Generation**: For computer vision tasks, simulators can generate thousands of perfectly labeled images (segmentation masks, depth maps, bounding boxes) in seconds, eliminating the massive bottleneck of manual data labeling.
 
-It's hard to tell, and you most certainly do not want to test this out for the first time in a crowded shopping mall! Here, a simulator can help. 
-When developing a software component for your robot, you can use readily available open-source simulators to test out how your software might work in the real world. You can simulate the robot's behavior, such as the sensor measurements and controller gains, and also the environment, such as friction, gravity, wind, etc. Once you simulate the robot in this "fake world", you may detect some problems with your current software stack and choose to improve them. You can keep iterating this until you get the desirable performance. 
+### 3. Performance Scaling and System Design
+- **Massive Parallelization & Time Scaling**: Simultaneously run thousands of simulation instances to compress years of robot learning into hours. Additionally, physics can be "overclocked" to run at multiple times real-time speed or slowed down to sub-millisecond intervals to debug high-speed contact dynamics.
+- **Environment Design & Planning**: Helps determine the optimal layout of a environment before anything is built, identifying traffic bottlenecks or "blind spots" for static sensors.
+- **Hardware-in-the-Loop (HIL) Testing**: Modern simulators allow you to connect actual embedded microcontrollers or flight controllers to the virtual environment. This enables testing of real embedded C++ code and communication latency while the physics remain virtual.
 
 
 ```mermaid
@@ -69,6 +79,27 @@ graph TD
 ```
 (Graph based on [Robotics simulation in Unity is as easy as 1, 2, 3](https://unity.com/blog/engine-platform/robotics-simulation-is-easy-as-1-2-3))
 
+## When to Avoid Simulation & Common Pitfalls
+
+While simulators are powerful tools, they are not a silver bullet. Over-committing to simulation can sometimes drain resources and introduce entirely new categories of bugs. 
+
+### 1. The Sim-to-Real Gap & Modeling Limits
+- **Inaccurate Contact Dynamics:** Physics engines use rigid bodies and numerical solvers, often struggling with soft-body deformations, complex contact or high-frequency loops.
+- **Unrealistic Sensor Noise:** Real-world sensors suffer from environmental interference, specular reflections and dropout. Perception pipelines tested only on synthetic data often fail entirely when fed noisy, real-world inputs.
+- **Unstructured Terrains and Fluids:** While modeling flat indoor floors is easier, accurately simulating unstructured environments such as loose gravel, mud, tall grass or fluid dynamics for underwater robotics is computationally prohibitive and often highly inaccurate.
+- **Hardware Wear and Degradation:** Simulators default to factory-perfect conditions. They rarely account for gradual mechanical realities over an operational shift, such as gear backlash, thermal throttling of motors under heavy load or nonlinear battery voltage drops.
+- **Human Unpredictability:** Simulating authentic human behavior (unpredictable crowd dynamics, sudden interventions, emergencies) is notoriously difficult, often leading to falsely optimistic safety validations.
+
+### 2. Resource Drains & Project Management
+- **The Cost of Simulation Accuracy:** For computer vision tasks, building a high-fidelity environment is a massive undertaking. For contact-rich tasks, it requires significant CPU/GPU resources to achieve highly accurate simulation. If a project's goals are heavily hardware-centric, over-investing in virtual modeling may become a distraction from actual deliverables.
+- **Runaway Compute Costs:** Spinning up thousands of virtual environments on commercial cloud infrastructure can quietly accumulate costs that exceed the price of simply building and testing a physical prototype.
+- **Skillset Requirements:** Constructing high-fidelity virtual worlds requires expertise akin to video game development. This can force a robotics team to divert critical headcount and focus away from core robotics engineering.
+
+### 3. Software Health & Algorithmic Pitfalls
+- **Volatility:** The robotics simulation landscape is highly unstable. Platforms frequently follow a cycle of corporate acquisition, industry-wide migrations or architectural resets that force developers to pivot workflows. Repositories often stagnate and reach EOL, quickly losing compatibility with modern operating systems.
+- **Network and Latency Abstraction:** High-level simulators frequently abstract away internal robot communication. They often assume instant data transfer between nodes, masking real-world embedded issues like communication congestion, dropped network packets or variable processing lag.
+- **Black Box Effects:** Many commercial physics engines utilize proprietary, closed-source algorithms with undocumented shortcuts designed to maintain real-time rendering speeds.
+
 ## How do Physics Simulators Work?
 
 Before we get into what simulators are out there for robotics (and ML/RL), we need to talk about how they simulate the world for our use. What makes them comparable (although not nearly identical) to the real world?