
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
We are given an elevation map,
heights[i]
representing the height of the terrain at that index. The width at each index is 1. AfterV
units of water fall at indexK
, how much water is at each index?Water first drops at index
K
and rests on top of the highest terrain or water at that index. Then, it flows according to the following rules:Here, "eventually fall" means that the droplet will eventually be at a lower level if it moves in that direction. Also, "level" means the height of the terrain plus any water in that column.
We can assume there's infinitely high terrain on the two sides out of bounds of the array. Also, there could not be partial water being spread out evenly on more than 1 grid block - each unit of water has to be in exactly one block.
Example 1:
Example 2:
Example 3:
Note:
heights
will have length in[1, 100]
and contain integers in[0, 99]
.V
will be in range[0, 2000]
.K
will be in range[0, heights.length - 1]
.这道题说有不同高度的地面,每次都位置K有水滴落下,水滴落下后移动的方向有如下的规则:
1. 如果水滴向左移动后最终停止的位置低于落下的位置,则向左移动。
2. 否则若水滴向右移动后最终停止的位置低于落下的位置,则向右移动。
3. 否则停在原来的位置。
水滴停止后,原来的位置高度就增加1,让我们返回最后地面的高度。我们首先来分析题目中的例子1:
我们可以观察出,如果左边到的位置低的话,就先去左边,即便右边能到同样低的位置,也还是左边优先。但是这个例子没能说明,如果右边的位置更低的话,是去右边呢,还是左边,看下面这个例子:
红色表示水滴落下的位置,我们可以看到第五滴水没有去右边更低的地方,而是去了左边的位置,这说明,左边有至高优先权,只要左边的最终位置低于水滴落下的位置,一定会去左边。
还有就是,去一个方向最终要落到一个局部最低点,请看下面这个例子:
我们可以看到,水滴去了右边第一个局部最低点,而再右边的全局最低点是无法到达的。如果都是一样的高度的话,落在离水滴落下起始位置最近的点,请看下下面这两个例子:
第一个例子中水滴去了局部最低点,第二个例子中由于右边的高度都相同,水滴去了最靠近起始位置的点。
那么分析到这里,我想思路应该比较明晰了吧。首先我们尝试向左走,找到第一个局部最低点,停止条件是左边的高度大于当前高度,但是为了防止出现大家高度都一样而需要停止在靠近起始点位置的情况,我们来一个回滚操作,就是只要和右边的高度一样,就一直往右滚。同样,在尝试向右走,找第一个局部最低点,停止条件是右边的高度大于当前高度,但是为了防止出现大家高度都一样而需要停止在靠近起始点位置的情况,我们也来一个回滚操作,就是只要和左边的高度一样,就一直往左滚。那么此时我们来做比较,如果左边的局部最低点小于雨滴落下位置的高度,那么左边局部最低点高度自增1。否则如果右边的局部最低点高度小于雨滴落下位置的高度,则右边局部最低点高度自增1。如果左右高度都一样,则雨滴落下位置的高度自增1,参见代码如下:
类似题目:
Trapping Rain Water
参考资料:
https://leetcode.com/problems/pour-water/discuss/116670/My-8-Lines-C++-Solution
LeetCode All in One 题目讲解汇总(持续更新中...)
The text was updated successfully, but these errors were encountered: