| # | User | Rating |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | jiangly | 3670 |
| 3 | Kevin114514 | 3657 |
| 4 | maroonrk | 3355 |
| 5 | Um_nik | 3353 |
| 6 | squareOf105 | 3346 |
| 7 | tourist | 3343 |
| 8 | strapple | 3324 |
| 9 | heuristica | 3322 |
| 10 | jiangbowen | 3291 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 158 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | AmShZ | 143 |
| 5 | Um_nik | 141 |
| 6 | Errichto | 139 |
| 7 | adamant | 137 |
| 8 | BledDest | 133 |
| 8 | maroonrk | 133 |
| 10 | qwexd | 130 |
|
+18
I think I have some ideas that can further reduce the $$$\sum n$$$ in Div. 1 D2. The main observation is that when $$$W$$$ is small, instead of only using copies of $$$1$$$, we can actually insert $$$2$$$ in our second query (If $$$W=1$$$ we'd just get a $$$0$$$). By choosing $$$N=10800$$$ and $$$B=150$$$, we can yield a $$$\sum n\leq21598$$$ solution. There's most likely room to reduce it even more by picking different $$$N,B$$$ and the article that deals with small $$$W$$$ . (In fact when I was first solving this I mistakenly used a $$$n=3(R-L)$$$ query in the big $$$W$$$ case, but was somehow still able to pass with this optimization...) |
| Name |
|---|


