Ω-SAIL
reveals the dynamics
A new signal for sailing instrumentation
Ω-SAIL reads the standard instrument stream and continuously computes how much usable margin is left on three load paths — and how fast that margin is closing. No new sensors. It runs on board.
Actual kernel output on a recorded upwind sequence with two gusts, played at ten times real speed. The warning on the sail-and-hull path fires with 75% of its margin still available; the margin then falls to 53%.
Ω-SAIL on the water.
Where the gap is
Speed, wind, heel, rig load — every channel is an instantaneous value. Reading a developing situation out of them is work the crew does, in their heads, while sailing.
Networked instruments, wireless load cells and multifunction displays made the data available everywhere on board. They did not change what the number on the screen means.
How close a load path is to its limit, and how fast it is getting there, is not a channel that exists on the bus today. That is the channel Ω-SAIL adds.
What it measures
Ω-SAIL does not track sensors. It tracks the three relationships a sailing boat is always negotiating, and reports how much room is left in each.
Is the sail still converting the wind?
Speed is being lost while the wind is there and the boat is not heeling further. The sail plan has stopped turning pressure into drive.
Is the hull still carrying the power?
Heel builds, the helm loads up and the rudder starts working to hold the line. The boat is going over its balance before anyone on deck calls it overpowered.
Is the hull still holding its line in the water?
The boat is sliding — leeway opens up between heading and track, or sea state is taking more out of the hull than the water is giving back.
Heel is the pivot. The same loss of speed means three different things depending on what heel is doing at that moment. Heel is what separates a sail that has stopped converting from a boat that is overpowered from a hull that is sliding — which is why the attribution is made on heel and not on speed.
What it needs
The minimum set produces a global signal. The recommended set separates the three paths.
Sample rate is handled as an interval, not as a count of samples: the same sequence read at 1 Hz and at 10 Hz produces the same lead time.
Evidence
Each row is one developing condition: when the warning fired, how much margin was still available at that moment, how far the condition then went, and when the trend turned.
| Warning at | Range left at warning | Lowest reached | Smoothed low | Trend reversal |
|---|---|---|---|---|
| 1 290 s | 78.8% | 50.4% | 63.0% | +12 s |
| 5 234 s | 85.6% | 56.1% | 66.7% | +24 s |
| 5 314 s | 75.4% | 57.1% | 72.1% | +34 s |
| 5 496 s | 78.2% | 59.7% | 73.5% | +29 s |
| 5 996 s | 75.5% | 51.2% | 69.3% | +41 s |
| 7 032 s | 85.0% | 59.9% | 70.0% | +86 s |
| 7 399 s | 85.0% | 58.4% | 72.0% | +27 s |
| 9 730 s | 87.6% | 52.0% | 70.3% | +35 s |
| 13 528 s | 84.2% | 65.7% | 62.5% | +16 s |
| Mean | 81.7% | 56.7% | 68.8% | +34 s |
Status: software prototype, tested on recorded data. These figures describe the recorded sequences that were processed. They are not universally validated performance values, and nothing here has yet been produced in real time at sea.
The next step is real-time validation on signals acquired directly from onboard instrumentation, with attention to data availability, acquisition frequency, synchronisation and processing latency. That is the work we are at METSTRADE to arrange.
The prototype
The display is diagnostic only. It shows where the margin is going and how fast — never what manoeuvre to make, because that depends on the boat, the sails and the crew's intention.
Where it earns its place
Solo and doublehanded crews have no one free to watch a number develop. Thirty seconds of notice is the difference between easing a sheet and repairing something.
A pilot today reacts to heading error. A margin that is closing in thirty seconds is a feed-forward input — a channel an anticipating pilot does not currently have.
A vendor-neutral derived channel that sits alongside load, rig and wind data, and logs where the boat was actually close to its limit rather than where it felt fast.
A visible, objective reason for what the boat is doing — for the student learning to read it, and for the fleet that would rather avoid the damage.
What we are looking for
Ω-SAIL does not replace instrumentation. It increases the value of data the partner's equipment already generates.
Ω-SAIL is designed to be cross-platform. A product first developed and validated inside one partner's technical environment can afterwards run on boats equipped by other manufacturers.
Contact
Tell us what your instruments publish, at what rate, and on which bus. We will tell you straight away whether Ω-SAIL can read it and what it would produce.
Ω-SAIL — Carpi (MO), Italy