Reports
PC² reports provide information about the contest data.
Contents
Location
Administrator module, Reports Tab
pc2report script
Version 8 Reports
Reports for Version 8 show a variety of information about the contest data/submissions. The Reports are:
-runs - dump run database -all - dump all probs, team names, langs and run info -complete - adds more reports than just all -prob - dump prob info -clars - dump all clarification info -1 - submissions by language -3 - number of teams that solved each problem -4 - number of correct and incorrect solutions by problem -5 - print summary of who should have balloons -6 - summary submissions, solutions, times by team/problem -7 - run listing per team by problem -8 - run summary grid -9 - fastest to solve problem -10 - account data file
Version 9 Reports
The following reports are available on Version 9 on both the server and admin
Use the Extract Replay Runs to extract run source files and a summary of the runs.
Example, note that you can use the report number 29 for Extract Replay Runs report)
pc2report --contestPassword foo 29
The 29 is from the --list option (see example below)
Reports
Report | Description |
---|---|
Account Permissions Report | For each client list their Permissions/Abilities |
Accounts | List summary of accounts per site, and individual accounts sites, logins, passwords. |
All Reports | List contents of all reports |
Balloons Delivery | List of all balloon deliveries by team, by problem and time of delivery |
Balloons Summary | List summary of which teams should have which color balloons. |
Clarifications | List all clarifications |
Client Settings | Various settings like Notification settings |
Contest | Contest settings in XML (work in progress) |
Contest Analysis | Summary of submissions, unjudged runs, various checks on runs. |
Evaluations | One line per judgement output |
Extract Replay Runs | Extract run info and submitted files |
Fastest Solved by Problem | List all run solving problems by fastest, by problem, and fastest solution showing rank, elapsed, team name |
Groups | List of Groups (Regions) |
Internal Dump | An internal dump of a bunch of config settings |
Judgement Notifications | Judgement Notifications |
Judgements | List of judgments |
Languages | List Languages |
Logins | List who is logged in |
Notification Settings | Notification Settings |
Problems | List problems |
Run 5 field | List of runs: run #, team #, problem letter, elapsed time, judgement |
Run Notifications Sent | Run Notifications Sent |
Runs | List of runs, with run#, run state, team #, team name, whether judgement sent to team and details on each judgement |
Runs (Version 8 content and format ) | List of runs with detail (see below) |
Runs grouped by team | List of runs, grouped by team, then by problem, helpful in calculating scoring. |
Solutions By Problem | For each problem show number of run with No, Yes, and percentage correct |
Standings XML | Standings in XML format |
Submissions by Language | A summary of how many teams used which languages. |
pc2report Examples
Here are a list of examples of pc2report, all these example are for version 9.0 or greater.
For these examples the Contest password is foo.
TBD describe where reports are written to and the naming convention
The report number (use --list option to show the number of a report) can be used as a shorter way to specify the report.
A partial name can be used for the report as well, for example to show All reports can be listed using:
pc2report --contestPassword foo All
List all report and their report number
pc2report --list
Report 10 Fastest Solutions Per Problem
pc2report --contestPassword foo 10
or
pc2report --contestPassword foo "Fastest Solutions Per Problem"