How akshayts968/federated-backend works
This repository implements a federated brain-tumor image-classification system: hospital nodes train locally on private image data, while a central service coordinates model updates. The graph preserves the principal client/server training path and the distinct client and server implementations present in the repository. It also shows model definition, authentication and node authorization, and the audit-ledger capability visible in the excerpts. There is no README, and several server excerpts are incomplete, so relationships not directly supported by shown calls or imports are omitted.
Main entry points: server.py Federation server · model.py Brain tumor CNN · client.py Hospital client · clientt.py Training listener
Components 16
Federation services
- Federation server
server.py - Audited server
sd.py - Prototype server
s.py - Audit ledger
sd.py - Cloud database setup
init_cloud_db.py - Tamper utility
tamper.py
Hospital clients
- Hospital client
client.py - FedProx client
c2.py - Training listener
clientt.py - Listener variant
clienttt.py - Encrypted client
c.py - Hospital A node
HosA.py - Hospital B node
HosB.py
Model runtime
- Brain tumor CNN
model.py
Other components
- Admin
- Hospital operator
Connections 23
- Hospital operator → Federation server: registers and logs in
- Admin → Federation server: manages federation
- Hospital client → Federation server: checks in and fetches model
client.py - Hospital client → Federation server: submits updates
client.py - Hospital client → Brain tumor CNN: instantiates
client.py - FedProx client → Brain tumor CNN: instantiates
c2.py - Training listener → Brain tumor CNN: instantiates
clientt.py - Listener variant → Brain tumor CNN: instantiates
clienttt.py - Encrypted client → Brain tumor CNN: instantiates
c.py - Hospital A node → Brain tumor CNN: instantiates
HosA.py - Hospital B node → Brain tumor CNN: instantiates
HosB.py - FedProx client → Federation server: checks in
c2.py - Training listener → Federation server: checks in
clientt.py - Listener variant → Federation server: checks in
clienttt.py - Hospital A node → Federation server: verifies node
HosA.py - Hospital B node → Federation server: verifies node
HosB.py - Prototype server → Training listener: dispatches training
s.py - Prototype server → Brain tumor CNN: uses model
s.py - Audited server → Audit ledger: loads and validates
sd.py - Audited server → Brain tumor CNN: uses model
sd.py - Federation server → Brain tumor CNN: uses model
server.py - Cloud database setup → Federation server: configures database
- Tamper utility → Audit ledger: alters ledger