Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Deeper guide: FL algorithms, FL setups, and worked sketches beyond MNIST

Aperta
  • Qualcosa non va?
#240 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
48/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
documentation

Direzione di ricerca

Start with Documentation/public/what-can-be-trained.md and services.md, then inspect client.py and aggregator.py to map the listed algorithms and FL setups to the train → audit → aggregate loop. Keep tested behavior distinct from untested sketches, and cover evaluation beyond MNIST. Done when the companion page is linked from both existing pages and gives model owners the requested service map and two non-MNIST sketches.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

documentation good first issue

Related: issue No. 157, PR No. 189, P3-DOC1, P3-DOC4

Why this would help

Issue No. 157 produced Documentation/public/what-can-be-trained.md, merged in PR No. 189. That page deliberately stays short and separates what has been tested from what is only possible. The proposed outline on issue No. 157 also had deeper sections that weren't shipped. A model owner who already knows FL can't yet see how a particular algorithm or FL setup maps onto DIN's train → audit → aggregate loop, or what a non-MNIST task would look like in practice.

Suggested next step

Write a companion page for readers who want more detail, linked from what-can-be-trained.md and services.md. Keep the tested-vs-possible labeling the current page uses, and cover:

  • FL algorithms: how FedAvg, FedProx, FedOpt (FedAdam/FedYogi/FedAdagrad), SCAFFOLD, FedNova and q-FFL fit the GI loop, and which service file each one touches (client.py, aggregator.py). Also how Byzantine-robust aggregators (Krum, trimmed mean, coordinate-wise median) sit alongside auditor scoring.
  • FL setups: horizontal (the default), vertical (entity alignment, split-model services), heterogeneity-aware (HeteroFL/FjORD-style sub-models), personalized, and federated transfer learning. For each, what changes in the services.
  • Worked sketches, each clearly labeled as untested:
    • a FedLoRA/FedQLoRA LLM fine-tune where only adapter weights move through IPFS
    • a tabular regression model with its own scoring function
  • How results are evaluated beyond MNIST: choosing a held-out test set and a scoring function that fits the task, and how that relates to auditor/BlockFLow scoring.

Expected outcome

A model owner can see which service changes their algorithm or FL setup needs, and has at least two non-MNIST sketches to start from. Nothing untested is presented as supported.

Turning any of these sketches into a tested reference implementation is a separate task.

Lingua principale
Python
Stelle
4
Fork
7
Merge medio
3g 58m
PR unite (30g)
39

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di InfiniteZeroFoundation/DevNet

Tutte le issue di InfiniteZeroFoundation/DevNet

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.