2.1 km · fails vehicle checks
Market access: Requires 18 cm clearance; vehicle profile has 15 cm.Robotics for Nigeria.
Start with evidence.
Test Nigerian English and Pidgin commands, explore local road scenarios, and build reproducible robotics experiments. Run the tools in your browser and export the evidence.
Take the controlsInteractive navigation lab
A small hotel. A simple mission.
Say it your way.
Give the robot a destination in English or Pidgin. Watch it find a clear route.
Command history00
- Your commands will appear here.
A deterministic grid simulator with predefined English and Pidgin commands. No physical robot or live AI model is connected.
Put the map
inside the mission.
A map-aware scenario layer for Nigerian places and conditions. Explore a route here, then carry its declared context into a Webots world when hardware and a physics model are available.
Lagos Island loop
Lagos Island loop
Market edges, junctions and pedestrian hand-offs.
A geometric path replay. No route planning or physics is applied.
Carry the scene into
a robot world.
Export an editable, inspectable Webots .wbt starter world with local geometry and source notes. It is a starting contract for a future robot controller, not a live connector or a physics simulation.
// Lagos Island loop / authored study
place = "Lagos, Nigeria"
source = "9jaRobotics local-context fixture"
layers = ["roads", "landmarks"]
webots = "editable world export ready"Scope: Stylised, authored geography for scenario design. The Webots export contains static geometry. Add a robot, controller and validated physical properties before conducting robot trials.
Measure the instruction.
Before the movement.
Compare predicted actions with explicit expectations in Nigerian English and Pidgin. This sample measures instruction interpretation; the navigation lab tests routes.
“Go to reception.”
A fictional indoor map has four destinations: reception, room 01, store and charger. “Room one” means room 01. No other rooms are defined. The robot is stationary, awaiting one instruction. Interpret the full instruction; a correction replaces the earlier destination. This is a language annotation, not a physical execution result.
A small test.
Every miss visible.
Run the existing rule parser, or import predictions from a model you evaluated separately. The rule baseline reads the instruction only and does not use scene context.
Files stay in this browser. Maximum 1 MB. Missing predictions count as misses. Template actions are placeholders to replace with your model’s output.
Sample provenance: 24 authored, unreviewed examples; 12 in Nigerian English and 12 in Pidgin. These are development fixtures, not collected human demonstrations. Both split labels are public. No model is called here, and these scores do not measure physical robot performance.
A shortcut can
cost more.
Compare a fastest assumed route with one that respects vehicle clearance, flood depth, surface quality, observation freshness and battery reserve.
Human observations are the moat. 9jaTesters can collect road surface, flood and charger reports with contributor review attached.
Vehicle-suitable route
4.1 km · arrival 18.6%
+2.0 km to avoid the riskier shortcutWhy the fastest route is rejected
- Market access: Requires 18 cm clearance; vehicle profile has 15 cm.
- Low crossing: Requires 16 cm clearance; vehicle profile has 15 cm.
- Low crossing: Flood depth 18 cm exceeds the 6 cm test limit.
These observations and coordinates are fictional fixtures. A suitable result is conditional on the inputs; it is not live navigation, EV telemetry, a safety guarantee or a real ETA. Real collection can be versioned through 9jaTesters and evaluated through 9jaBench.
Language. Perception. Action.
Test what connects them.
A command only makes sense in context. Use scene-grounded Nigerian English and Pidgin tasks to compare intended actions with model predictions, then test routes in a controlled grid. The current sample contains authored examples with declared provenance and review status.
LOCAL CONTEXT.REAL-WORLD AMBITION.
From human context
to robot action.
Three kinds of evidence, each with a different role. Human video is a starting point; robot sensor and action data comes later.
Capture human tasks.
Use 9jaBots to annotate permissioned phone videos and describe the scene, instruction and intended action. Record provenance and permission status.
Explore the task studioEvaluate the system.
Run a rule baseline, import your model’s predictions and inspect task errors. Edit navigation scenarios and export reproducible grid results.
Run the task benchmarkConnect robot evidence.
With hardware access, collect synchronised robot observations and actions. Richer simulation and physical trials will test what the grid cannot.
How the evidence connectsNigerian expertise.
Connected tools.
9jaRobotics is the robotics venture of Ranked Technologies Ltd, founded by author and builder Eruo Fredoline. Ranked.ng and 9jaTesters are established businesses serving paying customers. The lab connects local task knowledge with repeatable software experiments and a path to hardware research.
Read. Download. Reproduce.
Keep the task, source and result together as your experiment develops.
Run your first robotics experiment.
A practical guide to commands, obstacles and reproducible navigation checks.
DATASET / JSONNigerian English and Pidgin tasks.
24 authored examples with scene context and explicit expected actions.
COLLECTION GUIDEPlan a Nigerian mobility study.
100 assignment templates covering road scenes, objects, chargers and review.
Put a system
to the test.
Start with the authored task pack and compare a baseline with your own predictions. Every result should be traceable to a task.
Run a task benchmarkLearn how to start without hardware