Neighbor set
The adjacent nodes of v are the nodes joined to it by one edge.
Concept module
Keep one live graph, one local neighborhood, and one frontier cue visible together so graph structure feels readable before traversal rules get formal.
The simulation shows one labeled graph with the current node, the frontier nodes, and the visited nodes colored differently so local neighborhoods stay visible. A readout card reports the traversal mode, the current node, the frontier size, and the target, while a cue panel shows the frontier order and the current neighbor list. Breadth-first search is running on the layered campus graph from A toward H. The start node is waiting on the frontier. The frontier currently holds 1 node, and 0 nodes have already been visited.
Interactive lab
Graph traversal bench
Keep one live graph, the current frontier, and the visited state visible together so breadth-first and depth-first search read like different process choices on the same structure.
Controls
Swap among a few bounded graph scenes without leaving the shared bench.
Choose where the traversal begins.
Mark the node the search is trying to reach.
Compare queue-like breadth-first expansion with stack-like depth-first branching.
More tools
Secondary controls, alternate presets, and less-used toggles stay nearby without crowding the main bench.
More presets
Presets
Time
0.00 s / 20.3 sLivePause to inspect a specific moment, then step or scrub through it.Predict -> manipulate -> observe
Keep the active prompt next to the controls so each change has an immediate visible consequence.
Graphs
Switch graph views without breaking the live stage and time link.
Visited nodes versus frontier size
Watch how many nodes have already been expanded while the waiting frontier grows or shrinks.
Equation map
Select a symbol to highlight the matching control and the graph or overlay it most directly changes.
Switches among the bounded graph scenes on the same traversal bench.
Equations in play
Choose an equation to sync the active symbol, control highlight, and related graph mapping.
More tools
Detailed noticing prompts, guided overlays, and challenge tasks stay available without taking over the main bench.
What to notice
Keep the graph and one traversal graph visible together.
Guided overlays
Focus one overlay at a time to see what it represents and what to notice in the live motion.
Overlay focus
Keep the current node's neighbor list visible.
What to notice
Why it matters
It keeps graph reading local and visual instead of turning the diagram into a vague picture.
Neighbor set
The adjacent nodes of v are the nodes joined to it by one edge.
Degree
The degree counts how many direct neighbors a node has.
First frontier
The first frontier is the neighborhood of the chosen start node.
Progress
Not startedMastery: NewLocal-firstStart exploring and Open Model Lab will keep this concept's progress on this browser first. No finished quick test, solved challenge, or completion mark is saved yet.
Try this setup
Jump to a named bench state or copy the one you are looking at now. Shared links reopen the same controls, graph, overlays, and compare context.
Current bench
Layered campus BFS preset
This bench still matches one named preset, so the copied link will reopen that same starting point along with the current graph, overlays, and inspect context.
Open default benchSaved setups
Premium keeps named exact-state study setups in your account while stable concept links stay public below.
Checking saved setup access.
This concept can keep using stable links while the saved-setups capability resolves for this browser.
Copy current setup
Stable concept and section links stay public below while exact-state setup sharing stays behind premium.
Stable links
Starter track
Step 3 of 60 / 6 completeEarlier steps still set up Graph Representation and Adjacency Intuition.
Previous step: Binary Search / Halving the Search Space.
Short explanation
A graph should feel like a live neighborhood map, not an abstract list of circles and lines. This bench keeps one labeled graph, one active frontier, and one adjacency readout together so local connections stay readable before the search language gets more formal.
Adjacency is the first honest question: which nodes can the current node touch directly right now? Once that local neighborhood is visible, breadth-first and depth-first search become different ways of organizing the same next-step options.
Key ideas
Worked example
Live worked examples are available on Premium. You can still read the full frozen walkthrough on the free tier.
View plansLayered campus
A
B, C
1. Read only the direct neighbors first
2. Turn that neighborhood into a frontier
3. Name what stays the same later
First neighborhood read
Common misconception
Reading a graph means looking at the whole diagram at once and guessing a path globally.
The honest first move is local: read the neighbors of the current node.
Search grows from one neighborhood to the next, not from a magical full-map scan.
Mini challenge
Prediction prompt
Check your reasoning
Quick test
Reasoning
Question 1 of 2
Choose one answer to reveal feedback, then test the idea in the live system if a guided example is available.
Accessible description
The simulation shows one labeled graph with the current node, the frontier nodes, and the visited nodes colored differently so local neighborhoods stay visible.
A readout card reports the traversal mode, the current node, the frontier size, and the target, while a cue panel shows the frontier order and the current neighbor list.
Graph summary
One graph tracks visited nodes against frontier size, a second tracks the current depth against the deepest claimed depth, and a third compares new discoveries with repeat skips.
The graph hover and the step-through-time rail stay tied to the same live traversal bench.
Turn local neighborhoods into a live search frontier
These suggestions come from the concept registry, so the reason label reflects either curated guidance or the fallback progression logic.
Keep the queue frontier, visited count, and graph layers visible together so breadth-first search reads as a layered process instead of a procedure list.
Keep the stack frontier, current depth, and branch order visible together so depth-first search feels like disciplined backtracking instead of random wandering.
Keep repeat skips, waiting frontier nodes, and already-expanded nodes visible together so cycle handling feels like honest bookkeeping on one graph bench.