Prove, learn, repeat.
Each development stage is designed to reduce a specific uncertainty before the system moves into a more representative environment.
Evidence, built stage by stage.
Foundational modelling
Numerical investigation of the underlying physical system.
Computational development
Simulation used to evaluate performance and guide design decisions.
Experimental validation
Controlled testing used to compare predicted and observed behaviour.
Integrated system
Subsystems progressively combined into an energy-conversion prototype.
Representative environment
Testing under increasingly realistic hydraulic conditions.
Current development windowPilot deployment
Validation within real operating infrastructure.
Start with the physics.
Miromar uses numerical models to study the system at a high level without publicly exposing confidential equations or mechanism details.
- Hydrodynamic response
- Mechanical behaviour
- Energy conversion
- System dynamics
Interrogate the design space.
Abstracted analysis helps guide engineering decisions while protecting proprietary geometry. Public visuals are normalized and non-product-specific.
Measure what happens in water.
Controlled testing compares predicted and observed behaviour. Real Miromar imagery will replace the clearly marked development placeholder when it can be shared without disclosing confidential hardware.
Define a specific engineering question.
Create a controlled, repeatable test.
Capture physical response and uncertainty.
Compare, refine and determine the next test.
Data will speak when it is ready.
The reporting system is prepared for model comparisons, operating sweeps, repeatability and uncertainty. Public figures will appear only after they clear the release threshold.
Development confidence
Public dataset
in preparation
Bring a real site into the process.
Representative environments help turn laboratory learning into infrastructure-ready engineering.