Skip to content

Phase 4: typed visualizations and offboard messages, configuration, restart, ok_skew - #23

Merged
tsaubergine merged 4 commits into
mainfrom
advanced-features
Nov 13, 2026
Merged

tsaubergine merged 4 commits into
mainfrom
advanced-features

Conversation

@tsaubergine

@tsaubergine tsaubergine commented Nov 13, 2026 •

Copy link
Copy Markdown
Member

Phase 4 (ADVANCED) of the Goby helm plan. Most of the phase was already in place from Phase 1: deferred initialize, helm-start postings, life events, comms policy, refresh, goals_mandatory and behavior directories. This PR adds the rest and the m11_kahuna fixtures.

Changes

  • Visualization:
    • Behaviors' VIEW_POINT, VIEW_SEGLIST, VIEW_POLYGON and VIEW_SEGLR posts come out as Visualization, parsed with MOOS-IvP's XYPoint/XYSegList/XYPolygon/XYSeglr.
    • Other VIEW_* stay Postings.
  • OffboardMessage: NODE_MESSAGE_LOCAL comes out as OffboardMessage, parsed with NodeMessage.
  • goby_moos_gateway turns both back into the MOOS variables, so pMarineViewer still draws them. conversions.{h,cpp} holds the conversions both ways.
  • Configuration:
    • It covers domains, mode set, state and update variables, and subscriptions.
    • It comes out at startup and whenever it changes.
    • IVPHELM_STATEVARS and IVPHELM_UPDATEVARS are posted as pHelmIvP posts them.
  • Restart:
    • RESTART_HELM (or Command.restart) rebuilds the behaviors from their files.
    • Type 2 also posts the initialize variables again, and IVPHELM_RESTARTED follows on the next decision.
    • The helm keeps its contact manager and its own state.
    • Unlike pHelmIvP, the behavior file list is kept.
  • ok_skew:
    • Inputs further than ok_skew from the helm's clock are ignored, with a warning and IVPHELM_SKEW.
    • HELM_MAP_CLEAR is the exception, as in pHelmIvP.
    • Contacts are exempt, since the ledger ages them itself.
  • replay:
    • It parses VIEW_* and NODE_MESSAGE_LOCAL on both sides before comparing.
    • Reading a pContactMgrV20 block, it drops white space as MOOS's mission reader does without verbatim quoting. That's what pContactMgrV20 posts for a configured alert.
  • m11_kahuna: recorded, covering offboard messages, BHV_Trail and collision avoidance.
  • init.sh: everything from apt.oceansoft.org, nothing from packages.gobysoft.org.
    • apt.oceansoft.org's continuous channel now has Goby3 3.7.0, which depends on its release channel's DCCL, libais, Wt and MOOS.
    • If apt can't install IvPico's packages, init.sh adds both channels, checking each key's fingerprint.
    • MOOSDB is moos10-mit-db there.
    • main's CI fails without this, since apt.oceansoft.org's Goby3 stopped init.sh from adding packages.gobysoft.org.

Testing

  • New scenario tests:
    • typed outputs;
    • VIEW_* and NODE_MESSAGE_LOCAL round trips;
    • Configuration;
    • restart type 1 and type 2;
    • ok_skew.
  • All 29 replays, m11_kahuna's two vehicles included.
    • With the helm's own alerts, the trail and collision-avoidance spawns land within an iteration of pHelmIvP's.
  • The alpha launch with goby_moos_gateway and pLogger: VIEW_POINT and VIEW_SEGLIST reach the MOOSDB.
  • init.sh:
    • apt's resolution simulated on noble and resolute, amd64 and arm64, from apt.oceansoft.org alone;
    • run in clean ubuntu:24.04 and ubuntu:26.04 containers, then all 37 tests, closed loops included.
  • CI.

Generated by Claude Code

…estart, ok_skew

- Behaviors' VIEW_POINT, VIEW_SEGLIST, VIEW_POLYGON and VIEW_SEGLR posts
  come out as Visualization, and NODE_MESSAGE_LOCAL as OffboardMessage,
  parsed with MOOS-IvP's own classes. Other VIEW_* stay Postings.
  goby_moos_gateway turns them back into the MOOS variables, so
  pMarineViewer still draws them.
- A Configuration (domain, mode set, state and update variables,
  subscriptions) comes out at startup and whenever it changes, and
  IVPHELM_STATEVARS and IVPHELM_UPDATEVARS are posted as pHelmIvP does.
- RESTART_HELM (or Command.restart) rebuilds the behaviors from their
  files; type2 also posts the "initialize" variables again. The helm
  keeps its contact manager and its own state, as pHelmIvP's MOOS
  neighbours do.
- Inputs more than ok_skew from the helm's clock are ignored with a
  warning, as pHelmIvP ignores skewed mail.

replay parses the VIEW_* and NODE_MESSAGE_LOCAL posts on both sides
before comparing them. Reading a pContactMgrV20 block, it drops white
space as MOOS's mission reader does without verbatim quoting, so a
configured alert's flag matches what pContactMgrV20 posted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VLcYK4e29B5FiPbDDJy5fp
It exercises offboard messages, BHV_Trail and collision avoidance.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VLcYK4e29B5FiPbDDJy5fp
apt.oceansoft.org now has Goby3 3.7.0, so libgoby3-dev had a candidate
and init.sh skipped packages.gobysoft.org, leaving libais-dev and
dccl5-compiler uninstallable. Oceansoft's Goby3 also needs packages
neither repository has (libmoos10-mit, libwt4.15.0, a newer libais1).

Check that apt can install every Goby and MOOS package instead, and pin
packages.gobysoft.org over another source's Goby3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VLcYK4e29B5FiPbDDJy5fp
Open Ocean Software's continuous Goby3 depends on its release channel's
DCCL, libais, Wt and MOOS. If apt can't install everything, add both the
continuous and release channels, each key checked against its
fingerprint. MOOSDB is moos10-mit-db there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VLcYK4e29B5FiPbDDJy5fp
@tsaubergine
tsaubergine added this pull request to stack #25 November 13, 2026 06:56
@tsaubergine
tsaubergine merged commit 7a00b93 into main Nov 13, 2026
4 checks passed
@tsaubergine
tsaubergine deleted the advanced-features branch November 13, 2026 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants