How ahmadalameri-0/codexion works
Codexion is a command-line POSIX-thread simulation of coders competing for adjacent dongles. The workflow parses parameters, initializes shared simulation state, runs one coder thread per participant, arbitrates atomic dongle acquisition using FIFO or EDF request heaps, and monitors burnout or completion before joining workers. Cooldowns, synchronized logging, and stop signaling support that workflow. The excerpts show the main calls and synchronization paths; unsampled build and peripheral details are omitted.
Main entry points: main.c Simulation Entry · routine.c Coder Workers · monitor.c Burnout Monitor · dongle.c Dongle Arbitration
Components 10
Simulation Lifecycle
- Simulation Entry
main.c - Argument Parsing
src/parse.c - State Initialization
src/init.c - Coder Workers
src/routine.c - Burnout Monitor
src/monitor.c
Resource Arbitration
- Dongle Arbitration
src/dongle.c - Request Heaps
src/scheduler.c
Timing and State
- Simulation State
Codexion.h - Timing Utilities
src/utils.c
Other components
- CLI User
Connections 13
- CLI User → Simulation Entry: runs
README.md - Simulation Entry → Argument Parsing: parses arguments
main.c - Simulation Entry → State Initialization: initializes
main.c - Simulation Entry → Coder Workers: starts threads
main.c - Simulation Entry → Burnout Monitor: runs monitor
main.c - Simulation Entry → Coder Workers: joins threads
main.c - State Initialization → Simulation State: initializes fields
src/init.c - Coder Workers → Dongle Arbitration: requests and releases
src/routine.c - Dongle Arbitration → Request Heaps: updates heaps
src/dongle.c - Coder Workers → Timing Utilities: uses time and waits
src/routine.c - Dongle Arbitration → Timing Utilities: waits for cooldown
src/dongle.c - Burnout Monitor → Timing Utilities: checks time
src/monitor.c - Burnout Monitor → Simulation State: stops simulation
src/monitor.c