Marine dynamics & rendering
WWW-POSIM assembles Gazebo rigid-body simulation, Wave Sim hydrodynamics, POSIM robots and rendering, and application-specific environment controls. The tables identify the technology used by the running models and the assumptions that affect maritime robotics experiments. Sensor measurement algorithms and their SDF parameters have a separate Sensor models & parameters.
Force and observation pipeline
- SDF model + environment
Link masses, inertia, collisions, joints and actuator mounts define the body. The wave field and current profile provide water conditions.
- Actuators + water forces
Propulsion, buoyancy and enabled drag/damping terms act on links. Current changes velocity relative to the water.
- Gazebo physics step
The selected physics engine advances bodies and contacts. Controller feedback and sensors use the resulting state.
- Measurements + rendering
Sensors produce stamped observations. Ogre2 or the browser draws the scene; visual water and optical effects have separate settings.
Dynamics technology catalogue
| Component | Implemented method | Model boundary |
|---|---|---|
| Rigid body and contact | Gazebo loads link mass/inertia, collision geometry and joints from SDF and integrates their response to forces. | Collision meshes and simplified boxes determine contact, even when a visual model is more detailed. Specifications distinguish them. |
| WAM-V hull and propulsion | The application assembles Wave Sim's WAM-V, two propellers and wave-aware hydrodynamics. Commands act through the selected thruster/control path. | A rendered canopy is appearance; it does not independently change mass, drag or buoyancy. |
| BlueROV2 hull | The six-thruster POSIM model is adapted to the Wave Sim hydrodynamics system. Its existing hull collision box supplies the geometric basis. | The app removes the stock Gazebo Hydrodynamics plugin from this copy. Its stock added-mass/drag settings therefore do not describe the active application's hull forces. |
| Buoyancy | Wave Sim samples the water surface around collision geometry and computes submerged-geometry forces and moments. | This geometry-based model does not solve a full three-dimensional fluid field around the vehicle. |
| Drag and damping | Wave Sim provides viscous drag, pressure drag and linear/quadratic damping, enabled per model. | Coefficients and enabled terms are model parameters; they are not a measured identification of every real vessel. |
| Propulsion | Gazebo thruster systems apply force at configured joints. ArduPilot converts actuator channels into commands; ROS direct control bypasses the flight controller. | Thruster coefficients, direction, saturation and command units belong to the final model. A topic name alone does not establish a PWM-to-newton calibration. |
| World-voyage control | POSIM-Control adds speed/heading policies and native leader/follower feedback. | Automatic-voyage recovery and arrival policies differ from personal experiments; see Controller paths and feedback. |
The BlueROV2 application's hydrodynamics block enables damping with cDampL1=0.1, cDampL2=40, cDampR1=0.1, cDampR2=4; viscous_drag_on and pressure_drag_on are off for this model. These are the plugin's translational/rotational coefficient conventions, not interchangeable entries of a complete identified Fossen model. Preserve the generated SDF when comparing controllers.
Waves and currents
| Model / parameter | Application behaviour |
|---|---|
| Wave solver | Wave Sim's fft path produces a periodic wave field. The app selects a 256 m tile, cell_count=64 and steepness=1; wind speed/direction drive its spectral sea state. |
| Sea-state presets | Levels 0–4 select wind speeds 0, 1, 3, 6 and 8 m/s. These are application presets, not a claim of a certified sea-state scale or a fixed significant-wave-height measurement. |
| Physical field / visible extent | Repeated surface tiles display the same periodic field. Extending visible water does not create independent wave realizations or increase the physical FFT resolution. |
| Current coupling | Personal/competition hydrodynamics subtract horizontal current from each link's world linear velocity before water-force calculations. Current starts at zero in personal sessions. LIVE uses its selected voyage system. |
| Uniform current | One horizontal flow vector; GUI speed 0–1 m/s. Direction is flow toward east at 0° and north at 90°. |
| Depth profile | 2–8 layers, first depth 0 m, strictly increasing to at most 11,000 m. Interpolate x/y velocity components at each hydrodynamic link's centre-of-mass depth; clamp to end vectors outside the profile. |
| Interpretation | The profile changes horizontal flow with depth. It does not add density stratification, vertical flow, turbulence or current feedback into the wave spectrum. |
Environment changes are applied as complete revisions and confirmed by native readback. The browser's drawn heightfield can arrive later than the physical field; a screen image is not the acknowledgement of a force-setting change. Assigned competition conditions have their own activation and scoring rules.
Underwater rendering
POSIM's Ogre2 material extension applies optical appearance while shading surfaces. It affects RGB and RGB-D colour; numeric depth and collision geometry keep their underlying values. The Browser scene is a separate renderer with its own visual implementation.
| Technology / setting | What is implemented |
|---|---|
| Water-path haze | Mixes surface colour with a water-colour contribution according to the segment travelled through water. |
| RGB absorption | Channel-dependent attenuation changes colour with water path length. It is an appearance approximation, not a calibrated radiative-transfer solution for a particular water sample. |
| Sunlight fading | Depth-dependent sunlight attenuation; local lights retain their direct illumination, with attenuation along the viewing water path. |
| Caustics / suspended specks | Procedural seabed light patterns and optional particles. Specks occupy shared world positions, drift uniformly with simulation time and are occluded by opaque surfaces. Their visible interval is 0.05–3 m, clipped by the scene and mean water level. The visual drift is independent of currents and acoustic scattering. |
| Surface boundary | Optical water paths use the mean plane z=0. The physical wave surface can vary around it; near-surface optical and immersion boundaries are therefore different models. |
| Seabed texture / grid / contours | Texture and measurement overlays affect appearance. Grid spacing defaults to 10 m (1–500 m); contours to 5 m (1–50 m). They do not modify the numeric bathymetry. |
Water optics |
Groups haze, absorption, sunlight and related appearance choices; texture and measurement-overlay selections remain separate. |
Appearance changes are acknowledged after rendering. Sensor images should be checked from their actual lens and depth, not inferred from an above-water observer view. POSIM underwater-rendering implementation.
Interpreting an experiment
Record the final world/model SDF, active controller path, plugin identities, mass/inertia/collisions, force coefficients, environment profile and native readback. Also retain physics timestep, sensor acquisition rates and measured RTF: sensor Hz, video FPS and physics progress measure different workloads.
This stack is useful for testing algorithms under explicit model assumptions. Vehicle-specific hydrodynamic identification, fluid–structure interaction, breaking-wave loads, sediment resuspension and calibrated water optics require additional models and evidence. A convincing image or successful mission alone does not establish those properties.
Visual wake and propeller wash
WWW-POSIM builds foam meshes from measured horizontal motion and propeller thrust. At low speed, propeller wash spreads as rounded patches. As speed rises, it forms a narrower trail. Motion-generated foam fades with speed so small position changes do not draw bright lines.
| Input or setting | Implementation |
|---|---|
| Motion history | Up to 96 samples, 0.22 s spacing and 20 s lifetime |
| Propeller wash | Separate thrust direction for each propeller; up to 12 samples per side and 2.5 s lifetime |
| Speed transition | Rounded wash below 0.35 m/s; smooth transition to a narrow footprint by 2.35 m/s |
| Surface following | The visible Wave Sim ocean mesh supplies the foam vertices and transforms; a 1.5 cm offset keeps foam on the surface. |
| Observation scope | RGB cameras see the foam. Depth, LiDAR, thermal, segmentation and bounding-box sensors exclude its visibility layer. It applies no forces or collisions. |
| Render budget | A 512×512 opacity mask; up to nine shared 64×64 ocean tiles per vessel. No extra FFT or CPU wave-vertex copy. |
Without a compatible ocean mesh, the renderer uses nine wave-height samples per patch with a 0.2 s visual transition. Missing snapshots retain the last field; this fallback can lag or differ from the visible surface.
WWW-POSIM owns this C++ visual plugin and its shaders.
Implementation references: Wave Sim, POSIM robot models, POSIM-Control. WWW-POSIM owns the model assembly, selected hydrodynamics adaptation, environment control and session integration. Components & libraries · Sensor models & parameters.