Chris, Following up on your point about checkpoint/restart. The split is in lattice24-assess 0.2.0: https://github.com/JJardine919/lattice24-assess/commit/54041cb A TIMEOUT is now marked as a likely restart link when the same user starts another job with the same time limit within --restart-gap hours (default 2). The report gives timeout energy, and energy at stake, both with and without those links, instead of a single number. It is still a proxy, since the tool never reads job names, so it will miss chains that change their limit or sit in the queue longer than the gap, and it will occasionally catch unrelated back-to-back jobs. On synthetic data it found every planted chain with no false matches. On data with no chains it marked about 1.5% of timeouts. The report says to read the two figures as a range. I've also taken "returns nothing" out of the README and the report. If your site's pattern doesn't fit the same-limit, short-gap shape (for example, restarts that come back with a different limit), I'd like to know, because that is where the proxy would undercount. Thanks again, Jim