How chaitali771/mlops_telecom_customer_churnpredictionmodel works
This is a telecom-customer-churn ML pipeline template. The visible runtime entry point reads the raw CSV, then cleans, splits, transforms, and resamples it; later training, evaluation, and prediction modules exist but are empty in the supplied excerpts. The README describes a broader CLI, model registry, REST API/web console, and Docker deployment, but several documented paths and capabilities are not present in the tree. Those branches are represented only where paths are supported; links rely on README documentation where source wiring is unavailable.
Main entry points: main.py Pipeline entry · index.html Web console · processed Train/test data · models Model registry
Components 18
Pipeline workflow
- Pipeline entry
main.py - Data ingestion
src/data_ingestion.py - Preprocessing
src/data_preprocessing.py - Model training
src/model_building.py - Model evaluation
src/model_evaluation.py - Model prediction
src/model_prediction.py
Serving interface
- Web console
frontend/index.html - Console styling
frontend/css/style.css - REST API
src
Configuration and state
- Raw churn CSV
data/raw/churn.csv - Train/test data
data/processed - Model registry
models - Evaluation reports
reports - Pipeline config
config.yaml
Deployment
- Container services
docker/docker-compose.yml
Other components
- CLI user
- Browser user
- API client
Connections 17
- CLI user → Pipeline entry: runs
README.md - Pipeline entry → Data ingestion: calls
main.py - Data ingestion → Raw churn CSV: reads
src/data_ingestion.py - Pipeline entry → Preprocessing: calls
main.py - Preprocessing → Train/test data: produces
README.md - Train/test data → Model training: trains from
README.md - Model training → Model registry: saves model
README.md - Train/test data → Model evaluation: evaluates data
README.md - Model registry → Model evaluation: evaluates model
README.md - Model evaluation → Evaluation reports: writes metrics
README.md - Model registry → Model prediction: loads model
README.md - Pipeline config → Pipeline entry: configures
README.md - Browser user → Web console: opens
README.md - Web console → REST API: HTTP requests
README.md - API client → REST API: REST requests
README.md - Container services → Pipeline entry: runs stages
README.md - Web console → Console styling: uses styles
README.md