How subin31-j/electricity-consumption-anamoly-detection-ml works
ECAD is a historical electricity-consumption anomaly-analysis web application, not a live meter service. Users authenticate, then submit a demo consumer number or upload a dataset; the backend normalizes the data, runs anomaly models, and exposes results, visualizations, comparisons, history, and reports. Admins use a role-protected console. The README documents the shared analysis pipeline; sampled API and entrypoint files establish several dispatches, but unsampled implementations limit evidence for some internal links.
Main entry points: main.py API application · session.py Database sessions · analysis.py Analysis routes · analysis_runner.py Analysis runner
Components 25
Web application
- React application
frontend/src/App.jsx - Auth context
frontend/src/auth/AuthContext.jsx - API client
frontend/src/services/apiClient.js - Analysis views
frontend/src/components/analysis/AnalysisResultsView.jsx - Consumer service
frontend/src/services/consumerService.js - Analysis service
frontend/src/services/analysisService.js - Dataset service
frontend/src/services/datasetService.js
Backend API
- API application
backend/app/main.py - Authentication routes
backend/app/api/auth.py - Consumer routes
backend/app/api/consumers.py - Dataset routes
backend/app/api/datasets.py - Analysis routes
backend/app/api/analysis.py - Report routes
backend/app/api/reports.py - Admin routes
backend/app/api/admin.py - Report generation
backend/app/services/reporting.py
Analysis pipeline
- Preprocessing
backend/app/services/preprocessing.py - Feature engineering
backend/app/services/feature_engineering.py - Analysis runner
backend/app/services/analysis_runner.py - Anomaly models
backend/app/services/anomaly_detection.py
Identity and access
- Token security
backend/app/core/security.py - User and role guards
backend/app/core/deps.py
Persistent records
- Database sessions
backend/app/db/session.py - Analysis records
backend/app/models/analysis.py - User records
backend/app/models/user.py
Other components
- User
Connections 36
- User → React application: uses
- React application → Auth context: provides auth
frontend/src/App.jsx - React application → API client: calls API services
- User → Consumer service: submits consumer
- User → Dataset service: uploads dataset
- Consumer service → API client: sends requests
frontend/src/services/consumerService.js - Analysis service → API client: sends requests
frontend/src/services/analysisService.js - Dataset service → API client: sends requests
- API client → API application: HTTP requests
- Analysis views → Analysis service: loads results
- API application → Authentication routes: registers router
backend/app/main.py - API application → Consumer routes: registers router
backend/app/main.py - API application → Dataset routes: registers router
backend/app/main.py - API application → Analysis routes: registers router
backend/app/main.py - API application → Report routes: registers router
backend/app/main.py - API application → Admin routes: registers router
backend/app/main.py - Authentication routes → Token security: verifies and signs
backend/app/api/auth.py - Authentication routes → User and role guards: resolves current user
backend/app/api/auth.py - User and role guards → Token security: decodes token
backend/app/core/deps.py - User and role guards → User records: loads user
backend/app/core/deps.py - Authentication routes → Database sessions: uses session
backend/app/api/auth.py - Consumer routes → Analysis runner: starts analysis
backend/app/api/consumers.py - Consumer routes → Preprocessing: preprocesses input
backend/app/api/consumers.py - Dataset routes → Preprocessing: preprocesses upload
backend/app/api/datasets.py - Analysis routes → Analysis runner: runs analysis
backend/app/api/analysis.py - Analysis routes → Preprocessing: preprocesses input
backend/app/api/analysis.py - Analysis runner → Feature engineering: engineers features
- Analysis runner → Anomaly models: scores models
- Analysis runner → Analysis records: persists results
- Analysis routes → Database sessions: uses session
backend/app/api/analysis.py - Analysis routes → Analysis records: reads analysis
backend/app/api/analysis.py - Consumer routes → Database sessions: uses session
backend/app/api/consumers.py - Dataset routes → Database sessions: uses session
backend/app/api/datasets.py - Report routes → Report generation: generates report
backend/app/api/reports.py - Report routes → Database sessions: uses session
backend/app/api/reports.py - Admin routes → Database sessions: uses session
backend/app/api/admin.py