Validate the live boat physics built on the DSH calm-water backbone with bounded follow-on lanes. Save the profile. Sail lofts overlay their calibration on your foundation.
Photo: Don Ramey Logan / CC BY-SA 3.0
SailEdge runs a VPP-class force-balance computation at every point in the wind matrix — the same discipline used by ORC and naval architecture firms. Your role is to validate the boat side of that equation — now live on a DSH-backed calm-water backbone with bounded follow-on lanes — and save it as a calibration that every sailmaker builds on.
ORC certificate in, hull geometry out. Displacement, stability, rig dimensions — verified against your design data.
Every parameter shows its source. ORC, Derived, Estimated — color-coded and traceable. Confirm it matches your numbers.
Open point review or any Edge Map cell. Drive, side force, heel moment, CE position, whole-boat outcome, and hydro-lane disclosure are all visible for any condition.
One cell isn’t enough. Check upwind, reaching, downwind. When it converges across the range, the calibration is validated.
Load the boat from its ORC certificate. Hull geometry, stability data, polar performance — everything the certificate provides. Review the measurements, confirm they match your design data, and identify where the model needs refinement. The righting moment curve is retained directly from the certificate and drives heel equilibrium at every point of sail — no substitution, no generic approximation.
Open any Edge Map cell and inspect the force breakdown. Drive force, side force, heel moment, Center of Effort position — the full picture of how the model resolves that condition. Compare against your design data. Where the model diverges from known behavior, you know where to tune.
The hull response layer now runs through a live DSH-backed runtime backbone: upright hull, appendage, heel influence, sideforce/leeway, rudder interaction, and approved wave resistance where the boat data supports it. Heel equilibrium is still solved iteratively — the model finds the angle where heeling force from the sails matches the boat’s righting moment, then reports exactly how much drive was sacrificed if the rig depowered. These are the diagnostics you check against your design data.
Per-cell RM supplement and crew mode across the full polar — validation-grade resolution for stability review. See how crew weight changes the edge →
Boat Tuning now includes a Delft-style RM stability profile. Three knobs control the heel-dependent righting moment correction: Form stability fraction, RM correction onset, and GZ rolloff rate. These seed automatically when you select a Delft hull family, then you adjust for your specific hull. Every tuning knob now explains what it controls, what happens when you move it, and when to adjust it. Learn more →
The Hull Efficiency Index normalizes hull resistance across platforms — a single metric that lets you compare drag characteristics across designs regardless of displacement class.
Crew weight operates as a bounded what-if within the Edge Map. More weight means more righting moment upwind but more displacement to drag downwind, so the sensitivity is course-dependent. The certificate stays anchored. The what-if shows you where it matters and where it doesn’t.
Open Boat Tuning and review the bounded DSH runtime families first: upright hull, heel influence, appendage, sideforce/leeway, and rudder interaction. Adjust those before reaching for transitional residual overlays, and shape the hull physics until the Edge Map converges with your design data across conditions.
Every adjustment recomputes immediately. The ORC baseline stays anchored.
One cell isn’t enough. Check the force balance across the polar — upwind, reaching, downwind, light air, heavy air. When the model converges with your data across the full range, the calibration is validated.
When a cell hits a physical constraint — hull speed cap, depower ceiling, or rudder margin — the model flags it. Amber shading marks the cell and the detail card identifies which constraint was active. That distinction matters: a divergence caused by a model guardrail is different from a divergence caused by a calibration gap. One tells you the model is protecting the result. The other tells you where to tune.
Every cell in the Edge Map contains 107 computed attributes. At the professional tier, you see roughly 65 of them — per-sail force attribution, CE geometry, effective areas, confidence scoring, and clamp diagnostics. Engineering-grade access under NDA surfaces the full set. The depth scales with the conversation.
A validated calibration is only useful if it’s reproducible. Load the same ORC certificate, apply the same boat tuning profile, specify the same conditions — the Edge Map produces the same output. No drift. No randomness. No “it depends on the run.”
That’s what makes the calibration auditable. You can hand it to a partner loft, a class measurer, or a client — and they can verify the result independently.
Save your work as a Boat JSON artifact or NA tuning profile — your IP, portable and independent. Send it to your loft partners. They overlay their sail calibration on your validated hull physics. The result: every Edge Map for that platform is built on a foundation you approved.
Your calibration plus their calibration. Neither works as well alone.
Approve a class calibration and every owner in the fleet benefits. Lofts building on your platform know the hull physics are validated. Owners shopping for sails see Edge Maps built on builder-approved data.
Your work multiplies across the ecosystem. One calibration, every boat in the class, every sailmaker who serves them.
Builder-validated physics for every boat in the class. Tell us about your design.
Talk to Us See the physics behind it →