The duck detector comes from the Hub, the way the policies do - #267
Merged
Merged
Conversation
mediad reads its model from /opt/robot/detector/current rather than from inside the release. The release's postinstall hook seeds that directory from a pin in [workspace.metadata.detector] (pollen-robotics/ microduck-duck-detector@duck-v1) with scripts/seed-detector.sh, which is seed-policies.sh with a fixed file list and the same rules: a floor not a ceiling, nothing partial goes live, never touch a set it did not install. `robotctl detect check` and `sudo robotctl detect update [--version]` are `policy check`/`update` against the other root — new updaterd calls detector.check / detector.install (API v28), sharing the policy set's types, provenance record and install path. An install restarts mediad, which is where the model is loaded, and reports whether that took. The 14 MB of vendored weights leave the repository and the three packaging sites; xtask holds the pin, the file list (script, updater, robotd-params) and the packaging together. The model repo shares its name with the dataset repo. The robot only addresses the model (resolve/ without a datasets/ prefix, api/models/), which is written down where the URLs are built. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Coverage71.63% lines on this branch, against a floor of 70%. Per-file |
In robotctl configure, `detect.enabled` one line from `chorale.accept` read as "detect what?". The section, its struct (DuckDetectorParams) and the robotctl namespace are named for the thing detected. A file that still says [detect] loads through a serde alias and the editor carries it to the new name on its next save, the way [imu_head] was handled. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
# Conflicts: # mediad/src/main.rs
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mediad reads its model from /opt/robot/detector/current rather than from inside the release. The release's postinstall hook seeds that directory from a pin in [workspace.metadata.detector] (pollen-robotics/ microduck-duck-detector@duck-v1) with scripts/seed-detector.sh, which is seed-policies.sh with a fixed file list and the same rules: a floor not a ceiling, nothing partial goes live, never touch a set it did not install.
robotctl detect checkandsudo robotctl detect update [--version]arepolicy check/updateagainst the other root — new updaterd calls detector.check / detector.install (API v28), sharing the policy set's types, provenance record and install path. An install restarts mediad, which is where the model is loaded, and reports whether that took.The 14 MB of vendored weights leave the repository and the three packaging sites; xtask holds the pin, the file list (script, updater, robotd-params) and the packaging together.
The model repo shares its name with the dataset repo. The robot only addresses the model (resolve/ without a datasets/ prefix, api/models/), which is written down where the URLs are built.