Add AI/control, navigation, concepts, and manipulation sections (use-case gap closure)#5131
Draft
btshrewsbury-viam wants to merge 10 commits into
Draft
Add AI/control, navigation, concepts, and manipulation sections (use-case gap closure)#5131btshrewsbury-viam wants to merge 10 commits into
btshrewsbury-viam wants to merge 10 commits into
Conversation
Fills concept gaps surfaced by a use-case coverage analysis (Playbook 11): learned/policy control, VLA and LLM integration, simulation; localization, SLAM, base navigation, sensor fusion, multi-robot coordination; the platform mental model, confidence scores, inference latency, capture frequency; and force control and moving-object picking. 19 new pages across 4 sections. Passes prettier, markdownlint, and vale.
Verified against RDK source: - MoveOnMap/MoveOnGlobe are async, return an execution ID (not a bool) - merged movement sensor selects a source per property at configure time, not per-read failover - color_detector emits a constant 1.0 confidence - built-in webcam model triplet is rdk:builtin:webcam; clarify family slot - scope the ML model service Infer note to ML-backed detectors - open-vocabulary detection is a model you deploy, not a built-in - fix SLAM and object-tracker/detect link targets
- Repoint /operate/* and nonexistent SLAM-reference links to valid targets (/motion-planning/frame-system/, /navigation/slam-and-mapping/, registry) - Rename link text off 'How a robot knows where it is' (the render-link hook errors on link text containing 'here', which 'where' matches) - Drop the removed navigation-service tombstone link Validated: 0 broken internal links, vale + markdownlint clean, Hugo content render clean (only the PostCSS asset step needs npm, handled in CI).
Documents the use-case coverage analysis behind the four new sections: the 50 IoT/robotics use-cases, the ownership-sweep method, the before/after gap closure, and a link to the full spreadsheet.
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
viambot
added
the
safe to build
…ts section Per review, a concept page belongs in the section of the thing it is about, not a catch-all bucket: - platform-model -> what-is-viam/ - confidence-scores -> vision/ (ML/detector output) - capture-frequency -> data/ (capture vs sensor sample rate) - inference-latency -> ai-control/ Deletes docs/concepts/. Updates section landings, cross-links, and README.
…olute htmltest found 8 broken targets (IA-reorg paths and relative sibling links that don't resolve from leaf pages): - /operate/* and /components/base/sensor-controlled/ -> real /reference and /hardware and /build-modules targets - slam-and-mapping relative localization//navigate links -> absolute /navigation/... targets
…ents/ The /components/* alias paths render as directories without an index page. Repoint all bare /components/ links in the new pages to the real /reference/components/* pages (base, movement-sensor, and the index).
The reorg moved the concepts/ pages; the Netlify no-more-404 plugin flagged the old URLs as 404s. Preserve them as Hugo aliases (301) to their new homes.
The use-case coverage analysis is methodology/run-output, not docs-site content. It now lives in viam-code-map (playbook-11-example-run.md). This PR keeps only the documentation pages.
Collaborator
|
Glad to see this coming together, btshrewsbury-viam ! Two things I noted as I saw this in my inbox:
How are you planning to assess whether we do, in fact, need a page that Claude has produced as part of this work? I don't see anything that we definitely don't need, but it's worth considering. |
|
Hey btshrewsbury-viam — CI is green and no reviewer is assigned yet. Could you request one when you have a chance? Auto-comment from overwatch. Will not re-nudge for 7 days. |
Collaborator
Author
|
Shannon Bradshaw (@shannonbradshaw) I think this probably went too far, and should be a report instead of creating an automatic PR, that lets you guide what to create. I think a few pages could be useful, but as you mentioned, the organization feels off and the content needs tighter control. |
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
3 participants
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.
What
Four new documentation sections (19 pages) that close concept gaps found by a use-case → concept coverage analysis (Playbook 11) run over 50 real IoT/robotics product use-cases (VLAs, policy-based control, mobile robots, industrial manipulation, fleet ops, IoT sensing, CV, data pipelines).
docs/ai-control/— inference latency, learned & policy-based control, run a VLA, integrate an LLM, simulation & sim-to-realdocs/navigation/— localization, SLAM & mapping, navigate a mobile base, sensor fusion, coordinate a fleetdocs/manipulation/— force & compliance control, track & pick moving objectsConcept pages placed in their topical homes (not a generic bucket):
what-is-viam/platform-model,vision/confidence-scores,data/capture-frequency.Use-cases, method, and details
The use-case analysis behind these pages (the 50 use-cases, the method, and the measured gap closure) lives in viam-code-map, not this repo: see
playbook-11-example-run.md. The complete matrix (per-task concepts, gaps, learning objectives, before/after) is the spreadsheetplaybook11-use-case-coverage.xlsxin the shared Drive folder.Gap closure (63 concepts)
The 7 BURIED concepts (kinematics, frames, motion-planning) are intentionally deferred — they are owned inside the motion-planning section, which is under active edit.
Quality
MoveOn*return types,mergedconfigure-time selection,color_detectorconstant confidence,rdk:builtin:webcamtriplet, etc.Notes
_index.mdweights.🤖 Generated with Claude Code