ROS 2 fault diagnosis
A missing topic message becomes a diagnostic casebook. Compare rules and optional Jev Choice on fabricated events while preserving unknown and review outcomes.
Explore ROS 2, Kubernetes, cloud–edge AI, agentic systems and Jev through animated conceptual traces, rigorous research questions and contributor-ready experiments.
This is a set of proposed research scenarios on ROS 2, Kubernetes and cloud-edge AI robotics; none has a measured result yet.
It is for students, teachers and researchers who want to study these questions. The synthetic starting points need no robot, GPU or paid account.
These pages are crawlable, technical and honest about their status. An animated walkthrough explains a **proposed** data flow; it is not a model demonstration or evidence of a working robot fleet.
6 scenarios shown
A missing topic message becomes a diagnostic casebook. Compare rules and optional Jev Choice on fabricated events while preserving unknown and review outcomes.
Explore which inference location is eligible when latency budgets, cloud disconnects, model resources and action freshness matter.
Trace how an LLM's high-level robot skill proposal is checked in code before any optional Jev second opinion.
Study a fictional scout, carrier and arm; rank only eligible candidates while deterministic scheduling retains authority.
Investigate whether Choice and Score improve the classification and human routing of synthetic ROS 2/Kubernetes alerts beyond labelled monitoring rules.
Propose a scoped subtaskAsk whether Jev adds useful advisory context after deterministic checks of robot embodiment, action space, camera geometry, license and hardware.
Review prerequisite #57No matching scenario. Try another topic.
Define the null hypothesis, task, fixture split, deterministic baseline, model revision, metrics, confidence limits and failure conditions before testing.
Record raw predictions, abstentions, timeouts, run manifests, seeds and licenses. Keep model calls opt-in and never run a paid provider in default CI.
Require raw data, analysis scripts, independent review and explicit limitations before showing measured outcomes. Negative and inconclusive results count.
Per-scenario experiment IDs, a clearly labelled status, comparable baseline/JeV runs, measurable outcomes, uncertainty, reproducibility manifests and links to raw evidence.
Today every listed experiment is planned and every performance value is N/A. Those are intentional, not omitted success stories.
See the status of all four flagship research tracks and the requirements for publishing verified data. Contribute a reproducible result or a negative finding through an issue/PR.
View experiments & results ↗Improve a ROS 2 casebook, catch ambiguous labels, repair an example or evaluate readability. No hardware or paid account required.
Start with #84Build a deterministic baseline, a simulator contract or a network fault matrix; publish tests and explicit run conditions.
Explore #85Preregister a hypothesis on calibration, placement regret, agent review or scheduling fairness and analyze honest evidence.
Explore #88Every scenario issue includes a bounded task prompt, dependencies, validation expectations and safety boundaries. Read AGENTS.md before editing. AI coding assistance is optional and does not replace human review.
Follow the epic & open issues ↗ Help audit SEO & accessibility ↗No for the synthetic casebooks, design exercises and offline rules. Actual accelerated inference, live Jev and any robot/simulator benchmarks require separately documented equipment, licenses and permission.
No. The walkthrough uses preauthored educational text and client-side highlighting, never hosted inference. Jev's role is optional research only. It is not a motor controller or permission oracle.
Start with the experiment registry and evidence issue #88. Include a reproducible manifest, raw outcomes, code and negative cases. Unverified claims will not appear as measured results.
Yes, the scenarios are designed as research prompts and teaching starting points, but feasibility, novelty, ethics approval, licensing and academic supervision must be established for each proposed project.