L56LABY - EDITORIAL

PROBLEM LINK:

Practice
Contest

Setter: Kirill Gulin
Tester: Misha Chorniy
Editorialist: Taranpreet Singh

DIFFICULTY:

Simple

PREREQUISITES:

BFS, Max-heap/Priority Queue, Greedy

PROBLEM:

Given a N*M grid with certain forbidden cells (represented by -1) where Chef cannot enter, Empty cells (represented by 0) where chef can enter and exit, and Escape Cells (represented by x>0) using which Chef can escape from grid if he can reach escape cell from any cell within x seconds, i.e. the distance from escape cell must be at most x.
Chef can only move from one cell to another if they share an edge.

Find out from which Non-Forbidden cells from where the chef escape and print it in specified format.

STRATEGY TO SOLVE

A Tempting greedy but Wrong solution

The intuitive idea to solve this problem is For every node with value Greater than 0, run a BFS, mark the node as visited and terminating BFS when distance become greater than x. This strategy fail for following test case:

1
5 5
0 0 0 0 0
0 0 0 0 0
0 0 0 2 4
0 0 0 0 0
0 0 0 0 0

In this case, if we visit the position with value 2 first, we will either have to reprocess the same position with value 3 (while processing 4), thus getting either TLE or WA, depending upon implementation.

Why above solution doesn’t work

Suppose we process a position with lower grid value first. Then later, it might happen, that we visit the same node with higher value of x. Here, if we choose to process it again, we will get TLE in 2nd subtask, because our solution become O((N*M)^2) in worst case. If we choose not to process this vertex again, there is a the possibility that a node earlier not reachable with initial grid value, now become reachable with higher value of x, thus giving us WA.

This gives shape to the ideal strategy to get the correct solution.

Correct Solution:

The element with maximum value should be processed first of all.

Now, this way, whenever we reach a position already visited, we can simply ignore it because we have already processed this position with a higher value of x, Thus, keeping Time Complexity to O(N*M*log(N*M)) (Log factor added for insert and delete operations of Max-heap.

Our final solution become to maintain a max-heap, running a BFS. Due care must be taken to ensure that a position does not get inserted into heap twice, to keep our solution within time limit.

Tester’s implementation: An O(N*M + maxA) spproach.

With the same idea, Tester made a vector V array of size max(A) , storing all the position (i,j) in V[grid[i][j]] for grid[i][j]>0. This way, we run a loop from maxA to 0, and for each position in V[x], we add all its neighbours which are not already processed into V[x-1] and also mark them as visited.

This way, we save the Log factor associated with insertion in max-heap, thus, getting O(N*M+maxA) runtime.

Complexity:
Time Complexity is O(N*M+maxA) or O(M*N*log(M*N)), depending upon implementation.

AUTHOR’S AND TESTER’S SOLUTIONS:

Setter’s solution
Tester’s solution
Editorialist’s solution

4 Likes

solution are not visible @admin

I have dropped a message, will be visible soon.

1 Like

Weak test cases in the problem. https://discuss.codechef.com/questions/122121/wrong-solutions-passing-weak-test-cases-in-jan-lunchtime-l56laby

I used the same approach as the one described in the editorial but getting wrong answer. Can someone help in finding the error. Thanks in advance.

Link to solution

I couldn’t understand this part “Now, this way, whenever we reach a position already visited, we can simply ignore it because we have already processed this position with a higher value of x”,

Lets say for this grid:

-1 3 -1 -1

-1 0 -1 -1

-1 0 -1 -1

-1 0 2 -1

-1 0 -1 -1

How does it works in this test case.3 would reach till 2nd last row,then when bfs strts from 2 it’ll see that (3,1) is visited and stops ,so (4,1) never got included.

I know i am missing something.

Thank you!!

The use of max-heap process the positions in following order (i,j,x).

(2,1,3)

(4,3,2)

(2,2,2)

(2,4,1)

(2,3,1).

Note that actual order among tuples with same values of x may vary from above mentioned, but doesn’t affect our solution.

@vivek 3 node (0,1) is processed that gives value 2 to (1,1) then it is processed which gives value 1 to (2,1). now node (3,2) is processed which gives value 1 to (3,1) which when processed marks (4,1) as Y. there might be insertions needed while processing any node that’s why we use a priority queue instead of a static array to get nmlog(nm) complexity.
My sol:https://www.codechef.com/viewsolution/17173110

1 Like

Thanx mate!!!

Refer the TC mentioned above, run it with your solution, and pay special attention to position (3,1).

Don’t mark nodes visited as you input them.

Thanx mate!!

Thanks mate. Understood my mistake. Initially I tried marking visited after processing but it gave TLE because of multiple entries in max heap. Thanks

Can someone point out why I am getting wrong answer pls…
Here’s my solution

I tried to solve this question by recursion but i am getting TLE.
Can anybody help me to optimise this solution… thanks in advance.
solution link
link text

I constructed a binary maze matrix and applied bfs on it…then I saved all those i,j which were >0 and than ran a source to destination bfs for every i,j and the saved i,j(obviously on those i,j which equal 0). I should have sorted the saved i,j according to max value…would have got a right answer…

My solution gives WA even for the 1st subtask . Can anyone provide me a test case ?

Link .

I store the position of each element with value > 0 and then do a dfs .

can someone give some tricky test cases so that it can help everyone who got wrong. thanks in advance

after reading the editorial and seeing tester’s solution i finally got ac , so thought this might help i’ve heavily commented the code inorder to understand better. Anyone not getting anystep of tester’s solution can see my code here

1 Like

Could someone point out the error[link text][1] in my code. It is giving TLE in task2.
Solution Link


[1]


  [1]: https://www.codechef.com/viewsolution/17186562

Avoid repeated processing of same position.