Basically, you are given an array of size and queries. Each query can be of two types -
And all the indexes are -based.
So how can we solve this problem. Let’s try bruteforce approach. Here is a sample implementation in Python 3.
Here we are simply iterating over the queries. And depending on whether the query is of type or type , we either update the corresponding entry in the array or loop over all the elements to find the odd number.
But this approach would only work when the input size is small. For this problem, the input array could be as large as and the number of queries could also be as large as . In the worst case (that would occur when the odd number doesn’t exists and all the queries are of type ), this would mean iterating over whole of the array of size , times. Which is clearly not gonna cut it.
Thankfully, we can solve this problem under the given constraints with a neat little technique called Square root decomposition.
Main idea behind the Square root decomposition method is to divide our original array into buckets of equal size, usually where is the size of the original array.
Dividing the array into the buckets allows us to precompute some information about those buckets and later reuse them when given some query over the array.
For example, suppose we have to find some information about a range to . Now the given query range would be covering some of the buckets partially and others completely. Now the thing to note is that there could only be at most partially covered buckets. One on the left and one on the right of the query range.
For all the completely covered buckets, we won’t have to compute anything. We could directly use the precomputed information from above.
Only for these partially covered buckets, we would have to go inside those buckets, and compute the necessary information.
Finally, we can merge the collected information from these buckets to answer the given query.
In case we need to update the value of some array element, we would only need to recompute the information for the corresponding bucket only. And that could be done in time.
Now having gone through the basic idea of the Square Root Decomposition, let’s see how we can use this to solve our original problem statement.
First we will divide the original array into buckets. Here is at most , so number of buckets could be atmost and there would be numbers in each bucket with the last bucket having just elements.
Now for each bucket, we can compute the count of odd numbers in that bucket. As there can be maximum of buckets, we will have counts of odd numbers.
Now whenever we will receive the query of type 1, we can update the corresponding number in the original array and depending upon whether the new number is odd or even, we can either increase or decrease the odd number count of the corresponding bucket. This operation can be done time.
When we receive a query of type 2, instead of iterating over whole array like we were doing in the brute force approach, we can instead take use of our odd number count that we precalculated.
Suppose we need to find the odd number and assume that it exists at position . We will iterate over our decomposed counter array and maintain a cumulative sum of the total odd numbers seen till now. When we have seen at least odd numbers, we can then break and loop for that particular bucket which caused the sum to exceed and find the corresponding element position. This way we will just have to iterate for buckets, then over atmost elements inside that last bucket. Compare that to the lookups done by the brute force approach.
Time complexity for this operation will be thus . Since number of buckets and bucket size are almost the same, we can say that complexity is .
Overall complexity of the algorithm will be thus the time for precomputation of the buckets odd counts plus the time to answer the queries. The complexity then is .
Here is a sample implementation of the above strategy in Python 3.
You can find more problems related to Square root decomposition here.
Thank you for reading my article. Let me know if you liked my article or any other suggestions for me, in the comments section below. And please, feel free to share :)