Ocean Lab

Two surfaces: a harvest siting console (energy budgets, seasonal gap analysis, storage sizing) and a blade studio (NACA sections, panel-method polars, Cp sweeps, STL/OBJ/SCAD/DXF export). Every model runs in-process and deterministically; every site parameter is illustrative, not surveyed, and no hardware was built.

• Ocean Lab Capabilities. Report the lab's domains, surfaces, and the exact bound tables the routes reject on
• Harvest Site Catalogue. List the illustrative tidal sites and soil profiles the harvest simulation accepts, with the route's bound table
• Simulate Energy Budget. Integrate a marine (tidal/current) or ground (soil-thermal) energy budget over time — harvest, loads, state of charge, seasonal gaps, and the perpetual verdict
• Solve Rotor (BEMT). Solve a blade with blade-element momentum theory — per-station induction, section polars from a vortex panel method, Prandtl tip and hub loss, Glauert high-induction correction, and the…
• Cp vs Tip-Speed Ratio. Sweep tip-speed ratio and return the Cp curve plus the peak operating point for a blade
• Rotor-Fed Harvest Budget. Run the marine energy budget with the turbine's power coefficient taken from a solved BEMT blade instead of an assumed constant
• Export Blade Geometry. Loft a blade to a watertight triangle mesh and export it as STL (ascii or binary), OBJ, OpenSCAD or DXF, with the mesh validation report

1. 01

   You open it, or the assistant does

   Opening ?app=ocean-lab loads its 2 screens into the shared cockpit, starting on ocean-lab-harvest-console. The ribbon, the ticket list and the assistant are already there — the app contributes views, not a second application to log into.

2. 02

   The result lands where you can check it

   Back on the app's own screens, as state you own — not as a chat message you have to scroll back to find.

All 12 engineering apps →