Xeppelin contest watcher — a tool for ICPC computer time tracking

Revision en4, by KiKoS, 2025-02-27 12:21:27

Hey Codeforces!

My ICPC team Xeppelin (arzhantsev64, Akulyat, KiKoS) is currently actively training for ICPC EUC and WF. During the virtual contests, sometimes we lose track of time, especially when someone is debugging something. Even worse, if several people are changing places debugging several different problems. And afterwards it's not really clear what time was spent on what.

So we've built a small neat tool for us, but maybe it'd be of use for you as well.

Basically, it's a small script that watches the changes in the directory. So it automatically logs how our contest went. After the contest we usually plot the results in a nice timeline, where we can see the lost time.

It requires some specific workflow (the biggest one would be conventions on file naming) and a bit of manual inputs (the AC times for each of the problems), but that's it — rest is done by the scripts.

Here's an example:

The usual question is "how do you separate coding time and debugging time" — well, it is based on the fact that either ./A.cpp file or ./A file is updated heavily.

And the github, if you want to use it, is here. Should be available through pip install xeppelin. Feel free to contribute if you want!

Tags icpc, utility, tools

History

 
 
 
 
Revisions
 
 
  Rev. Lang. By When Δ Comment
en6 English KiKoS 2025-02-27 12:22:06 0 (published)
en5 English KiKoS 2025-02-27 12:21:46 10 Tiny change: 'n see the lost time.\n\nIt re' -> 'n see the time lost.\n\nIt re'
en4 English KiKoS 2025-02-27 12:21:27 171 (saved to drafts)
en3 English KiKoS 2025-02-27 12:20:03 0 (published)
en2 English KiKoS 2025-02-27 12:15:36 87
en1 English KiKoS 2025-02-27 12:14:35 1375 Initial revision (saved to drafts)