Skip to content

URML: validating a helm-and-trim command against the sailing envelope #277

Description

@idoco2003

Hi. Disclosure first: AI-assisted prose I reviewed before posting (https://github.com/URML-MARS/URML/blob/main/VIBE.md); say the word for human-only.

I maintain URML (https://urml.dev), a small Apache-2.0 language for declaring what a vehicle can do and checking an intended action against that declaration before it runs.

A sailing robot is an unusual and instructive case, because the admissible action depends heavily on a declared operating envelope (sea state, no-go zones, sail limits) that shifts with conditions. The autonomy decides a helm and trim command to make progress; URML can check that command against the platform's sail and rudder limits and a mission-declared operating boundary or sea-state ceiling, before it reaches the actuators. It does not touch the wind estimation or the course logic.

URML does not sail, estimate wind, or steer. It declares the envelope and confirms a commanded helm-and-trim action is inside it before dispatch.

Two questions:

  1. For a sailing-vessel stack, is a declared envelope check (sail and rudder limits, operating boundary, sea-state ceiling) on a helm-and-trim command useful before dispatch, or is that already handled inside the controller?
  2. Would a small worked example mapping a sailing command onto a URML manifest, validated with no execution, be worth having?

Nothing here asks you to adopt or maintain anything. Thanks for keeping an autonomous-sailing stack in the open.

Ido Yahalomi (greenvh@gmail.com)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions