WWW-POSIM v0.6.16Simulator documentation
Documentation menu
WWW-POSIM / Simulator documentation

Specifications

Default runtime, data, physics and robot interfaces for WWW-POSIM. Platform- and world-specific settings are identified separately.

Software

Item Specification
ROS ROS 2 Lyrical
Gazebo Jetty · Gazebo Sim 10; macOS package: 10.5.0
Surface autopilot ArduRover 4.7.2 · SITL
Underwater autopilot ArduSub 4.7.2 · SITL
ArduPilot source fb773567896014da007bca58358704d4a0d8516f
Browser graphics Three.js 0.186.1 · React Three Fiber 9.8.1

Simulation time

Item Specification
Default speed target 1×
macOS physics timestep 10 ms
Windows/Linux app physics timestep 20 ms
Competition evaluation timestep 10 ms
Web server timestep Server configuration

Rates use simulation time. Actual real-time factor (RTF), physics update rate, sensor rate and display FPS are separate measurements.

Physics and rendering

Item Specification
Rigid-body motion and contact Gazebo Physics; default DART backend
Marine dynamics Wave Sim wavefield, buoyancy and hydrodynamics
BlueROV2 hydrodynamics Wave-aware buoyancy and linear/angular damping
Gazebo views and sensors Ogre2 on the engine host; Metal on macOS
Browser scene Three.js/WebGL renders terrain, robots and water from simulator state
Browser wave geometry Samples from the physical wave solver

Terrain, waves and seabed extents

Item Specification
WAM-V demo terrain Prepared Hong Kong harbour; 2 × 2 km centre within 6 × 6 km surroundings; numeric elevation/depth and aerial imagery
Custom world default Fixed 1 × 1 km area; on-demand terrain is optional
On-demand seed region 1,000 × 1,000 m · 129 × 129 samples
On-demand numeric spacing 7.8125 m
Default streaming tile 1,000 × 1,000 m
Personal workspace required seabed 5 × 5 tiles; 5 × 5 km
LIVE required seabed 7 × 7 tiles; 7 × 7 km with default tiles
Fixed-region default when streaming is disabled 1 × 1 km · 513 × 513 samples · 1.953125 m spacing
Periodic physical wave tile 256 × 256 m · 64 × 64 cells
Personal Gazebo detailed water surface 3 × 3 repeated tiles; 768 × 768 m
LIVE configured wave visual tiles 15 × 15 tiles; 3,840 × 3,840 m

The wave calculation tile, visible water surface, numeric terrain and loaded collision seabed have different extents. Repeated wave tiles share a periodic field; they are not independent ocean simulations. The WAM-V demo uses the prepared Hong Kong field. Challenges use a separate authored arena with a flat seabed at 20 m depth. See the terrain-mode and Terrain LOD: detail near the vehicle.

On-demand terrain generation

Item Specification
Data preparation Fetch numeric elevation/depth and available land imagery; project to a local metric grid
Tile construction Build visual and collision meshes from shared grid samples; two-cell sampling halos preserve boundary continuity
Gazebo spawning Spawn real SDF terrain entities at their local coordinates
Readiness checks Verify entities and RGBD depth; a 0.25 m radius, 10 kg sphere tests contact using slope-aware mesh distance · Terrain readiness checks
Prefetch Prepare the next outer row using position and speed; 120 s lookahead, at least 250 m, capped at 40% of a tile
Pause and resume Hold when required coverage is missing; resume after the full current square passes checks
Cache and residency Reuse cached samples and recently visited tiles; remove distant entities under a bounded residency budget

Datasets

Item Specification
GEBCO 2026 Global elevation and bathymetry; native 15 arc-second grid
Copernicus GLO-30 Land elevation; nominal 30 m
Copernicus Marine 202511 Regional coastal bathymetry where available
EMODnet DTM 2024 Regional bathymetry, primarily European waters
KHOA BADA2024 Optional Korean bathymetry
Cesium World Bathymetry Preferred when licensed numeric access is configured
OpenStreetMap coastline Land/water boundary refinement
Sentinel-2 RGB Land imagery; nominal 10 m

The world records the sources actually used. Generated mesh spacing does not increase the accuracy of source measurements.

Vehicle models

Item Specification
WAM-V propulsion 2; left and right
BlueROV2 propulsion 6
WAM-V mass Hull link 180 kg; all model links 211.151 kg
BlueROV2 mass Hull link 10 kg; all model links approximately 10.0132 kg
WAM-V hull collision bounds 5.006 × 2.487 × 1.291 m
BlueROV2 hull collision box 0.457 × 0.338 × 0.065 m
BlueROV2 front lights Two forward spotlights; default ON; model attenuation range 25 m
BlueROV2 manufacturer overall size 0.457 × 0.338 × 0.254 m

Collision dimensions describe the simulation geometry, not the complete physical product. Mass totals are sums of SDF link masses.

Default sensors and state outputs

Item Specification
WAM-V GNSS Default; 5 Hz; 0.2 s latency; GPS_INPUT → ArduPilot EKF
BlueROV2 satellite GNSS Default enabled; can be disabled explicitly; antenna immersion gate; 3 s reacquisition
WAM-V IMU 200 Hz
BlueROV2 IMU 1,000 Hz configured; bounded by physics stepping
Forward RGB, both vehicles 640 × 480 px · 5 Hz · horizontal FOV 1.05 rad (60.2°)
BlueROV2 inspection RGB-D 640 × 480 px; 5 Hz; horizontal FOV 60.2°; 45° downward
WAM-V 2D LiDAR 5 Hz; 360 samples over 360°; 0.2–50 m; range resolution 0.02 m
BlueROV2 magnetometer 20 Hz · Gazebo
WAM-V odometry 20 Hz
BlueROV2 odometry 100 Hz

Cameras activate on demand. The standard ROS connector delivers JPEG images at up to 1 Hz in simulation time. Odometry is simulator state, not an error-bearing physical positioning sensor. Published frequency can be lower than the configured sensor rate.

GNSS & navigation defines measurement quality, antenna frames, loss and recovery.

A saved vehicle-builder configuration can change the sensor set, topics, mounts and settings. Generated payload topics use /vehicle/sensors/{sensor_id} with output-specific suffixes. Check the running ROS topics list and exported sensor-manifest.json for actual names and frames. See Optional sensors and providers for DVL, Ping and multibeam distinctions.

For the implementation, SDF parameter names, noise, frames and validity rules behind each measurement, see Sensor models & parameters.

Camera clipping and visibility

Item Specification
Built-in WAM-V forward RGB near 0.1 m · far 5,000 m
Built-in BlueROV2 forward RGB near 0.1 m · far 5,000 m
BlueROV2 inspection RGB-D near 0.1 m · far 80 m
Vehicle-builder cameras Use the saved sensor settings; separate from the built-in cameras above
Personal Gazebo scene camera Near 0.1 m; far = max(5,000 m, 16 × terrain 3D diagonal)
LIVE Gazebo scene cameras Near 0.1 m; far 5,000 m; 1280 × 720 pixels
Browser World/Vehicle camera Adaptive near 0.03–40 m; far at least 8,000 m, expanded with world size and view distance

Clipping is the geometric drawing range. Underwater attenuation, occlusion, loaded terrain and imagery coverage can reduce useful visibility within that range. Scene cameras and robot sensors are separate.

ROS topics and messages

Item Specification
/clock rosgraph_msgs/msg/Clock
/model/{robot}/odometry nav_msgs/msg/Odometry
/model/{robot}/imu sensor_msgs/msg/Imu
/model/{robot}/camera/compressed sensor_msgs/msg/CompressedImage · JPEG, ≤1 Hz
/model/wamv/scan sensor_msgs/msg/LaserScan
/model/bluerov2/inspection/image/compressed sensor_msgs/msg/CompressedImage · RGB
/tf, /tf_static tf2_msgs/msg/TFMessage
/mavros/battery sensor_msgs/msg/BatteryState; ArduPilot mode
/wwos/cmd_vel geometry_msgs/msg/TwistStamped; WAM-V direct ROS control
/wwos/thrusters std_msgs/msg/Float64MultiArray; direct ROS control, force in N

{robot} is wamv or bluerov2. The connector exposes the inspection RGB image; RGB-D sensor depth is a separate native output. Command updates stop after a 0.75 s watchdog timeout.

Coordinates, units and model assumptions

Item Specification
Geographic coordinates WGS 84 · latitude/longitude in degrees
Local world axes ENU · east / north / up
Gazebo body axes FLU · forward / left / up
ArduPilot body axes FRD · forward / right / down
ArduPilot navigation axes NED · north / east / down
ROS motion units m · s · m/s · rad/s · m/s² · N

Frame conversions occur at the autopilot boundary. Simulation parameters describe a model: manufacturer endurance, depth ratings and sensor accuracy are not implied.

References

Search documentation