PC2 Details
This is the PC2 Details section of the PC2 Developer's Wiki. It contains articles about specific low-level design and implementation details for the PC2V9 system, including:
- PC2v9 Module Startup, a description of the code flow when a PC² module is started.
- Transport Layer, which covers details on how PC² modules communicate using PC2 Packets.
- PC2v9 Run Execution, a description of how the system actually executes submissions from teams.
- CLICS Validator Implementation, a description of how PC2V9 supports the CLICS Validator specification.
- Web Team Interface Implementation, giving technical details about how the EWU "Web Team Interface" works.
- Contest Clock, which describes various things about how PC² manages "contest time"
- Technical Debts, a list of "technical deficits" -- places that should be fixed/improved in the code.
- Evil Programs, a description of PC2V9 sample submissions designed to cause a Security Violation.
- Exit Code, an overview of what OS exit codes are and how they different between platforms.
- Creating a Custom Module, an explanation of how to create custom PC2v9 modules with arbitrary characteristics.
- Using the PC2v9 API to Start a Contest, which explains what its title describes.
- Notes on YAML Loading, which provides some details about how PC2v9 handles loading contest configurations via YAML files.
- Test Case Results Table, which gives a narrative explanation of how the Judge's Test Results Table is populated.
- UI Design Elements, which gives insight into aspects of the UI design of PC2v9.
- Realm.properties - a configuration file for managing access to PC2v9 web services such as the Event Feed
- Replay Contest Submissions, an explanation of how a previous contest can be "re-run".
- Undocumented Features, which describes a collection of, well, features that are (otherwise) undocumented -- shortcuts that might make life easier and so forth.
- Detailed Design Elements, containing miscellaneous additional low-level design details.
