Papers › Personalizing Federated Medical Image Segmentation via Local Calibration

Personalizing Federated Medical Image Segmentation via Local Calibration

11 Jul 2022arXiv:2207.04655archive 2025-07-28

Jiacheng Wang, Yueming Jin, Liansheng Wang

Medical image segmentation under federated learning (FL) is a promising direction by allowing multiple clinical sites to collaboratively learn a global model without centralizing datasets. However, using a single model to adapt to various data distributions from different sites is extremely challenging. Personalized FL tackles this issue by only utilizing partial model parameters shared from global server, while keeping the rest to adapt to its own data distribution in the local training of each site. However, most existing methods concentrate on the partial parameter splitting, while do not consider the inter-site in-consistencies during the local training, which in fact can facilitate the knowledge communication over sites to benefit the model learning for improving the local accuracy. In this paper, we propose a personalized federated framework with Local Calibration (LC-Fed), to leverage the inter-site in-consistencies in both feature- and prediction- levels to boost the segmentation. Concretely, as each local site has its alternative attention on the various features, we first design the contrastive site embedding coupled with channel selection operation to calibrate the encoded features. Moreover, we propose to exploit the knowledge of prediction-level in-consistency to guide the personalized modeling on the ambiguous regions, e.g., anatomical boundaries. It is achieved by computing a disagreement-aware map to calibrate the prediction. Effectiveness of our method has been verified on three medical image segmentation tasks with different modalities, where our method consistently shows superior performance to the state-of-the-art personalized FL methods. Code is available at https://github.com/jcwang123/FedLC.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples: 9 from 1 repository linked to this paper, 2 identical to code harvested from another paper's repository. Across all 11: 9 ran (of which 4 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 7 ran (6 with no instrument failure; 1 where Syntology's instrument failed); 2 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

jcwang123/fedlc officialmentioned in papermentioned on GitHubpytorchSyntology: 9 samples, 7 ran (1 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 9 ran (of which 4 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
1ran · our draft was wrong
1ran; the contract check could not run
6ran
2unverified

Licence: 11 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from jcwang123/fedlc. 2 samples are listed last, in a group without a repository. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

jcwang123/fedlc official repository 9 samples, 7 ran (1 instrument-failed) · 2 unverified
ConvD networks/lcrepnet.py ran · metamorphic tier: deterministic no licence file found · pointer only · 9442a3560aa8ec40 · report fixture: returned ConvD · level recorded 2026-09-22
ConvU networks/lcrepnet.py ran · metamorphic tier: deterministic no licence file found · pointer only · 0a66d833b12b0456 · report fixture: returned ConvU · level recorded 2026-09-22
HeadCalibration networks/lcrepnet.py ran · metamorphic tier: deterministic no licence file found · pointer only · 5fd57c5f0649893d · report fixture: returned HeadCalibration · level recorded 2026-09-22
MyUpsample2 networks/lcrepnet.py ran fingerprinted no licence file found · pointer only · 9fd839307b5e29d2 · report fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-24
PersonalizedChannelSelection networks/lcrepnet.py ran · metamorphic tier: deterministic no licence file found · pointer only · 754c08818291c178 · report fixture: returned PersonalizedChannelSelection · level recorded 2026-09-22
Soft networks/lcrepnet.py ran no licence file found · pointer only · 0020002c2c774535 · report fixture: signature attention:Tensor/4/float · returned Tensor · level recorded 2026-09-24
normalization in 70 papers
census: 4 implementations from 6 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
networks/lcrepnet.py ran · our draft was wrong no licence file found · pointer only · 159a52df66ac5d88 · report fixture: signature planes:int/0/int, norm:str/0/str · returned GroupNorm · level recorded 2026-09-22
LC_Fed networks/lcrepnet.py unverified no licence file found · pointer only · ddfaf71789cc7905 · report
Unet2D networks/lcrepnet.py unverified no licence file found · pointer only · c0b124432018561d · report
Repository not located 2 samples, 2 ran (1 instrument-failed) · 0 unverified
2 samples are identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
gkern in 20 papers repository not located ran · honoured contract fingerprinted licence of this copy not recorded · d6d03dafd950d6c4 · report fixture: signature kernlen:int/0/int, nsig:int/0/int · returned ndarray · level recorded 2026-09-22
min_max_norm in 19 papers
census: 3 implementations from 6 papers, 3 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 4, kind float, dtype float32
repository not located ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted licence of this copy not recorded · f11714f9833718d2 · report fixture: signature in_:Tensor/4/float · returned Tensor · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for LC-Fed (graph method: LC-Fed). 11 bricks; individually on a fixture: 9 ran (of which 4 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. LC_Fed entry · level 0 · unverified · ddfaf71789cc7905
  2. HeadCalibration model · level 1 · ran · 5fd57c5f0649893d
  3. Unet2D model · level 0 · unverified · c0b124432018561d
  4. Soft helper · level 1 · ran · 0020002c2c774535
  5. ConvD helper · level 1 · ran · 9442a3560aa8ec40
  6. ConvU helper · level 1 · ran · 0a66d833b12b0456
  7. PersonalizedChannelSelection model · level 1 · ran · 754c08818291c178
  8. gkern helper · level 1 · ran · honoured contract · d6d03dafd950d6c4
  9. min_max_norm helper · level 1 · ran; the contract check could not run (RAISES) · f11714f9833718d2
  10. normalization helper · level 1 · ran · our draft was wrong · 159a52df66ac5d88
  11. MyUpsample2 helper · level 1 · ran · 9fd839307b5e29d2

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2207.04655") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Federated LearningImage SegmentationMedical Image SegmentationSegmentationSemantic Segmentationchannel selection

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections