3362. Zero Array Transformation III
Description
You are given an integer array nums
of length n
and a 2D array queries
where queries[i] = [li, ri]
.
Each queries[i]
represents the following action on nums
:
- Decrement the value at each index in the range
[li, ri]
innums
by at most 1. - The amount by which the value is decremented can be chosen independently for each index.
A Zero Array is an array with all its elements equal to 0.
Return the maximum number of elements that can be removed from queries
, such that nums
can still be converted to a zero array using the remaining queries. If it is not possible to convert nums
to a zero array, return -1.
Example 1:
Input: nums = [2,0,2], queries = [[0,2],[0,2],[1,1]]
Output: 1
Explanation:
After removing queries[2]
, nums
can still be converted to a zero array.
- Using
queries[0]
, decrementnums[0]
andnums[2]
by 1 andnums[1]
by 0. - Using
queries[1]
, decrementnums[0]
andnums[2]
by 1 andnums[1]
by 0.
Example 2:
Input: nums = [1,1,1,1], queries = [[1,3],[0,2],[1,3],[1,2]]
Output: 2
Explanation:
We can remove queries[2]
and queries[3]
.
Example 3:
Input: nums = [1,2,3,4], queries = [[0,3]]
Output: -1
Explanation:
nums
cannot be converted to a zero array even after using all the queries.
Constraints:
1 <= nums.length <= 105
0 <= nums[i] <= 105
1 <= queries.length <= 105
queries[i].length == 2
0 <= li <= ri < nums.length
Solutions
Solution 1: Greedy + Difference Array + Priority Queue
We want to "remove" as many interval queries as possible, while ensuring that for each position \(i\), the number of selected queries covering it, \(s(i)\), is at least the original array value \(\textit{nums}[i]\), so that the value at that position can be reduced to 0 or below. If for some position \(i\) we cannot satisfy \(s(i) \ge \textit{nums}[i]\), it means that no matter how many more queries we select, it is impossible to make that position zero, so we return \(-1\).
To achieve this, we traverse the queries in order of their left endpoints and maintain:
- Difference array
d
: Used to record where the currently applied queries take effect—when we "apply" a query on the interval \([l, r]\), we immediately dod[l] += 1
andd[r+1] -= 1
. This way, when traversing to index \(i\), the prefix sum tells us how many queries cover \(i\). - Max heap
pq
: Stores the right endpoints of the current "candidate" interval queries (store as negative numbers to simulate a max heap in Python's min heap). Why choose the "latest ending" interval? Because it can cover farther positions. Our greedy strategy is: at each \(i\), only pick the longest interval from the heap when necessary to increase coverage, so that more intervals are available for subsequent positions.
The specific steps are as follows:
- Sort
queries
by the left endpointl
in ascending order; - Initialize the difference array
d
with lengthn+1
(to handle the decrement atr+1
), and set the current coverage counts=0
, heap pointerj=0
; -
For \(i=0\) to \(n-1\):
- First, add
d[i]
tos
to update the current coverage count; - Push all queries \([l, r]\) with left endpoint \(\le i\) into the max heap
pq
(store-r
), and advancej
; -
While the current coverage
s
is less than the required valuenums[i]
, and the heap is not empty, and the top interval in the heap still covers \(i\) (i.e., \(-pq[0] \ge i\)):- Pop the top of the heap (the longest interval), which is equivalent to "applying" this query;
- Increment
s
by 1 and dod[r+1] -= 1
(so that after passing \(r\), the coverage count automatically decreases);
-
Repeat the above steps until
s \ge nums[i]
or no more intervals can be selected; - If at this point
s < nums[i]
, it means it is impossible to make position \(i\) zero, so return \(-1\).
- First, add
-
After traversing all positions, the intervals remaining in the heap are those that were not popped, i.e., the queries that are truly retained (not used for the "zeroing" task). The heap size is the answer.
The time complexity is \(O(n + m \times \log m)\), and the space complexity is \(O(n + m)\), where \(n\) is the length of the array and \(m\) is the number of queries.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
|