How 1iekki/cempu works
CEMPU measures classroom engagement from microphone audio and presents group results in a dashboard. The principal workflow is: a device records audio, computes a live volume-based engagement measure, and uploads recordings; the backend accepts recordings and exposes analysis and device-control endpoints; analysis transcribes speech, derives semantic context features, diarizes speakers, and classifies on-topic discussion; results and live measurements are surfaced to the dashboard. MQTT carries device commands and measurements, while WebSockets relay device messages. Several dashboard-to-backend details and unsampled analysis internals are not shown, so those links are marked unverified or omitted.
Main entry points: backend/main.py HTTP and WebSocket API · client/main.py Raspberry Pi · +page.svelte Group results · cempuMQTT.py MQTT bridge
Components 20
Device capture
- Raspberry Pi
client/main.py - Volume measure
client/volumeAnalysis.py - Device MQTT
client/cempuMQTT.py
Backend services
- HTTP and WebSocket API
backend/main.py - MQTT bridge
backend/cempuMQTT.py - WebSocket connections
backend/connectionManager.py - Audio recordings
backend/analysisParams.py
Audio analysis
- Analysis configuration
backend/analysisParams.py - Context processing
backend/contextProcessor.py - Speech transcription
backend/transcriber.py - Semantic search
backend/semanticSearch.py - Speaker diarization
backend/speakerDiarization.py - On-topic classifier
backend/contextClassifier.py
Dashboard
- Dashboard overview
dashboard/src/routes/+page.svelte - Group results
dashboard/src/routes/group/[id]/+page.svelte - Group state
dashboard/src/lib/stores/groupStore.ts - Analysis state
dashboard/src/lib/stores/analysisStore.ts - Group information
dashboard/src/lib/components/groupInfo/groupInfo.svelte
Other components
- Instructor
- MQTT broker
Connections 22
- Instructor → Raspberry Pi: controls recording
client/main.py - Raspberry Pi → Volume measure: measures audio
client/main.py - Raspberry Pi → Device MQTT: sends engagement
client/main.py - Raspberry Pi → HTTP and WebSocket API: uploads audio
client/main.py - Device MQTT → MQTT broker: publishes and subscribes
- HTTP and WebSocket API → Audio recordings: writes uploads
backend/main.py - HTTP and WebSocket API → Analysis configuration: uses settings
backend/main.py - HTTP and WebSocket API → Context processing: runs analysis
backend/main.py - HTTP and WebSocket API → Speaker diarization: runs analysis
backend/main.py - HTTP and WebSocket API → On-topic classifier: scores analysis
backend/main.py - HTTP and WebSocket API → MQTT bridge: routes device messages
backend/main.py - MQTT bridge → WebSocket connections: broadcasts messages
backend/cempuMQTT.py - MQTT bridge → MQTT broker: exchanges MQTT messages
- HTTP and WebSocket API → WebSocket connections: manages WebSockets
backend/main.py - Context processing → Speech transcription: transcribes audio
backend/contextProcessor.py - Context processing → Semantic search: encodes and compares
backend/contextProcessor.py - HTTP and WebSocket API → Dashboard overview: serves results
- HTTP and WebSocket API → Group results: serves group data
- Dashboard overview → Group state: uses group state
- Group results → Group state: uses group state
- Group results → Analysis state: uses analysis state
- Group results → Group information: renders details