How capooo2224/measure-manage works
Measure-Manage is a face-recognition attendance tracker with a desktop session workflow and a separate web registration workflow. An operator selects a group, configures attendance and grace timers, starts a session, and the engine processes webcam frames to log recognized students as present or late; the operator can dismiss remaining students as absent or export the session CSV. Registration adds student images and manages group folders used by recognition. The excerpts show the main GUI-to-engine calls and registration writes; details of some engine internals and the HTML template are not sampled.
Main entry points: app_14.py Tracker engine · gui_11.py Attendance GUI · registration2.py Registration routes · Expected_faces_db Group folders
Components 11
Desktop attendance
- Attendance GUI
gui_11.py
Face recognition
- Tracker engine
app_14.py
Student registration
- Registration routes
registration2.py - Registration form
templates/registration.html - Page styles
static/styles.css
Attendance data
- Group folders
Expected_faces_db - Session CSV logs
Expected_faces_db - Student images
Expected_faces_db
Other components
- Operator
- Webcam
- Registrar
Connections 11
- Operator → Attendance GUI: uses
gui_11.py - Attendance GUI → Tracker engine: controls sessions
gui_11.py - Attendance GUI → Tracker engine: requests frames
gui_11.py - Attendance GUI → Tracker engine: exports CSV
gui_11.py - Tracker engine → Webcam: captures frames
app_14.py - Tracker engine → Group folders: loads group faces
app_14.py - Tracker engine → Session CSV logs: writes attendance
app_14.py - Registrar → Registration routes: submits registration
registration2.py - Registration routes → Registration form: renders form
registration2.py - Registration routes → Group folders: lists groups
registration2.py - Registration routes → Student images: saves uploaded images
registration2.py