Shortest Path in DAG Using Topological Order in DSA Go - Time & Space Complexity

Time Complexity: Shortest Path in DAG Using Topological Order

O(n + m)

Understanding Time Complexity

We want to understand how the time needed to find the shortest path in a Directed Acyclic Graph (DAG) grows as the graph gets bigger.

Specifically, how does the algorithm using topological order handle larger graphs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

func shortestPathDAG(graph [][]Edge, start int) []int {
    n := len(graph)
    dist := make([]int, n)
    for i := range dist {
        dist[i] = math.MaxInt32
    }
    dist[start] = 0

    order := topologicalSort(graph)

    for _, u := range order {
        if dist[u] != math.MaxInt32 {
            for _, e := range graph[u] {
                if dist[u]+e.Weight < dist[e.To] {
                    dist[e.To] = dist[u] + e.Weight
                }
            }
        }
    }
    return dist
}

This code finds shortest paths from a start node to all others in a DAG using topological sorting and edge relaxation.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The nested loops: outer loop over all nodes in topological order, inner loop over edges from each node.
• How many times: Outer loop runs once per node (n times), inner loop runs once per edge (total m times across all nodes).

How Execution Grows With Input

As the graph grows, the algorithm visits each node once and checks all edges once.

Input Size (n nodes, m edges)	Approx. Operations
10 nodes, 15 edges	~25 operations (10 + 15)
100 nodes, 200 edges	~300 operations (100 + 200)
1000 nodes, 5000 edges	~6000 operations (1000 + 5000)

Pattern observation: The total work grows roughly in proportion to the sum of nodes and edges.

Final Time Complexity

Time Complexity: O(n + m)

This means the time grows linearly with the number of nodes plus the number of edges in the graph.

Common Mistake

[X] Wrong: "The algorithm checks all paths, so it must be exponential in time."

[OK] Correct: Because the graph is acyclic and we use topological order, each edge and node is processed only once, avoiding repeated work.

Interview Connect

Understanding this time complexity shows you can analyze graph algorithms that efficiently handle special cases like DAGs, a valuable skill in many coding challenges.

Self-Check

"What if the graph had cycles? How would the time complexity and approach change?"

Practice

1. What is the main advantage of using topological order to find the shortest path in a Directed Acyclic Graph (DAG)?

easy

A. It finds the longest path instead of the shortest.

B. It guarantees the graph has cycles.

C. It sorts vertices by their weights.

D. It allows processing vertices in a linear order without revisiting nodes.

Solution

1. Step 1: Understand topological order in DAG

   Topological order arranges vertices so that all edges go from earlier to later vertices, ensuring no cycles.

2. Step 2: Use topological order for shortest path

   Processing vertices in this order means each vertex is processed after all its predecessors, so shortest paths can be updated without revisiting.

3. Final Answer:

   It allows processing vertices in a linear order without revisiting nodes. -> Option D

4. Quick Check:

   Topological order = linear processing without revisits [OK]

Hint: Topological order processes nodes once in DAG [OK]

Common Mistakes:

• Thinking topological order applies to graphs with cycles
• Confusing topological order with sorting by weights
• Assuming it finds longest path by default

2. Which Go code snippet correctly initializes the distance array for shortest path calculation in a DAG with 5 vertices, starting from vertex 0?

easy

A. dist := make([]int, 5); for i := range dist { dist[i] = 1<<31 - 1 }; dist[0] = 0

B. dist := make([]int, 5); for i := range dist { dist[i] = 0 }; dist[0] = 1<<31 - 1

C. dist := make([]int, 5); for i := range dist { dist[i] = -1 }; dist[0] = 0

D. dist := make([]int, 5); dist[0] = 0

Solution

1. Step 1: Initialize distances with max int

   We set all distances to a large number (infinity) to represent unknown paths, here 1<<31 - 1 for max int.

2. Step 2: Set source distance to zero

   The starting vertex distance is zero because the shortest path from source to itself is zero.

3. Final Answer:

   dist := make([]int, 5); for i := range dist { dist[i] = 1<<31 - 1 }; dist[0] = 0 -> Option A

4. Quick Check:

   Initialize with max int, source zero [OK]

Hint: Set all distances max int, source distance zero [OK]

Common Mistakes:

• Setting all distances to zero initially
• Not setting source distance to zero
• Using -1 as initial distance

3. Given the following DAG edges with weights: 0->1 (2), 0->2 (4), 1->2 (1), 1->3 (7), 2->3 (3). What is the shortest distance array from source vertex 0 after running shortest path using topological order?

dist := []int{0, 2147483647, 2147483647, 2147483647}
// After processing edges in topological order

medium

A. [0, 4, 5, 8]

B. [0, 2, 4, 7]

C. [0, 2, 3, 6]

D. [0, 3, 4, 7]

Solution

1. Step 1: Relax edges from source 0

   dist[1] = min(inf, 0+2) = 2; dist[2] = min(inf, 0+4) = 4

2. Step 2: Relax edges from vertex 1 and 2

   From 1: dist[2] = min(4, 2+1) = 3; dist[3] = min(inf, 2+7) = 9
   From 2: dist[3] = min(9, 3+3) = 6

3. Final Answer:

   [0, 2, 3, 6] -> Option C

4. Quick Check:

   Relax edges in topological order = [0,2,3,6] [OK]

Hint: Relax edges in topological order to update distances [OK]

Common Mistakes:

• Not updating dist[2] to 3 after relaxing from vertex 1
• Ignoring relaxation from vertex 2 to 3
• Using initial distances without updates

4. Consider this Go code snippet for shortest path in DAG:

dist := make([]int, 4)
for i := range dist {
    dist[i] = 1<<31 - 1
}
dist[0] = 0
for _, u := range topoOrder {
    for _, edge := range graph[u] {
        if dist[u]+edge.weight < dist[edge.to] {
            dist[edge.to] = dist[u] + edge.weight
        }
    }
}

If the graph contains a cycle, what problem will occur?

medium

A. The code will produce correct shortest paths regardless.

B. The code will skip some vertices but finish normally.

C. The code will run infinitely because topological order is invalid.

D. The code will panic due to nil pointer dereference.

Solution

1. Step 1: Understand topological order requirement

   Topological order exists only if the graph has no cycles. If a cycle exists, topoOrder is invalid or partial.

2. Step 2: Effect of cycle on code execution

   Standard topological sort algorithms produce a partial order (not all vertices included), so the loop will skip some vertices but finish normally since topoOrder is a finite slice.

3. Final Answer:

   The code will skip some vertices but finish normally. -> Option B

4. Quick Check:

   Cycle causes partial topoOrder, skips vertices [OK]

Hint: DAG must be acyclic; cycles break topological order [OK]

Common Mistakes:

• Assuming code works fine with cycles
• Expecting panic instead of infinite loop
• Ignoring the need for cycle detection

5. You have a DAG with 6 vertices and weighted edges: 0->1(5), 0->2(3), 1->3(6), 1->2(2), 2->4(4), 2->5(2), 2->3(7), 3->4(-1), 4->5(-2). Using shortest path with topological order from vertex 0, what is the shortest distance to vertex 5?

hard

A. 5

B. 4

C. 3

D. 7

Solution

1. Step 1: Initialize distances

   dist = [0, inf, inf, inf, inf, inf]

2. Step 2: Relax edges in topological order

   From 0: dist[1]=5, dist[2]=3
   From 1: dist[3]=min(inf,5+6=11)=11, dist[2]=min(3,5+2=7)=3
   From 2: dist[4]=min(inf,3+4=7)=7, dist[5]=min(inf,3+2=5)=5, dist[3]=min(11,3+7=10)=10
   From 3: dist[4]=min(7,10+(-1)=9)=7
   From 4: dist[5]=min(5,7+(-2)=5)=5

3. Step 3: Check final distance to vertex 5

   dist[5] = 5

4. Final Answer:

   5 -> Option A

5. Quick Check:

   Relax edges carefully to get dist[5] = 5 [OK]

Hint: Relax edges in topo order, watch negative weights carefully [OK]

Common Mistakes:

• Ignoring negative edge weights
• Not updating distances after relaxation
• Assuming negative weights cause cycles