Greedy Challenge (APCS 2025-06 Advanced)

2.0s 256M

There are \(n\) ordered stages with positive sandbag counts. Repeatedly choose the unfinished stage with the fewest bags, breaking ties by smallest index. Stop if its count \(w\) exceeds \(t\). Otherwise score \(w\), transfer its bags to the next unfinished stage on its right (or remove them if none exists), and permanently finish the chosen stage. Find the total score.

Input

Read \(n,t\), then the \(n\) initial counts.

Constraints

\(1\le n\le300000\); \(1\le t,w_i\le10^9\).

Output

Print the score, or \(0\) if no move is possible.

Scoring

Each scored test independently awards 5 points, totaling 100. Samples award no points.

  • 1: 20% — \(n\le100\) and \(t\le1000\)
  • 2: 80% — No additional restrictions.

Sample Input 1

6 8
4 4 2 1 9 3

Sample Output 1

18

Sample Input 2

5 4
4 4 3 2 1

Sample Output 2

10

Source

q838 · 2025-06 APCS.

Problem page help

Keyboard shortcuts

Main features

  • Sample tests — Runs the sample cases bundled with the problem and auto-compares against the expected output.
  • Custom test — Run your code with your own stdin. Optionally tick the "Compare with expected (diff)" box to verify against expected output line-by-line.
  • Template — Paste the default code template you set on your profile page.
  • Collab — Edit this problem together with classmates in real time.
  • Auto-draft — Editor contents auto-save to your browser every 1.5 seconds (per account / problem / language).
  • Submit — Send your code to the judge for grading; returns AC / WA / TLE etc.

Limits

  • Source code: at most 65,536 characters
  • Custom test stdin and expected output: at most 1 MB each (≈1 million characters)
  • Custom test and sample test share the sandbox; about 1 request per 3 s per user (sample test: 1 per 1 s)
  • Custom test and sample test both have a 15 second wall-clock cap (the official judge still uses the problem time limit)
  • Interactive problems do not offer custom test (cannot simulate interaction with the judge).
  • Submitting has no rate limit, but rapid repeated submissions on the same problem are treated as score farming.