Papers › Federated Domain Generalization for Image Recognition via Cross-Client Style Transfer

Federated Domain Generalization for Image Recognition via Cross-Client Style Transfer

3 Oct 2022arXiv:2210.00912archive 2025-07-28

Junming Chen, Meirui Jiang, Qi Dou, Qifeng Chen

Domain generalization (DG) has been a hot topic in image recognition, with a goal to train a general model that can perform well on unseen domains. Recently, federated learning (FL), an emerging machine learning paradigm to train a global model from multiple decentralized clients without compromising data privacy, brings new challenges, also new possibilities, to DG. In the FL scenario, many existing state-of-the-art (SOTA) DG methods become ineffective, because they require the centralization of data from different domains during training. In this paper, we propose a novel domain generalization method for image recognition under federated learning through cross-client style transfer (CCST) without exchanging data samples. Our CCST method can lead to more uniform distributions of source clients, and thus make each local model learn to fit the image styles of all the clients to avoid the different model biases. Two types of style (single image style and overall domain style) with corresponding mechanisms are proposed to be chosen according to different scenarios. Our style representation is exceptionally lightweight and can hardly be used for the reconstruction of the dataset. The level of diversity is also flexible to be controlled with a hyper-parameter. Our method outperforms recent SOTA DG methods on two DG benchmarks (PACS, OfficeHome) and a large-scale medical image dataset (Camelyon17) in the FL setting. Last but not least, our method is orthogonal to many classic DG methods, achieving additive performance by combined utilization.

PaperPDFCodeCode Syntology ran

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 12 code samples harvested from 1 repository linked to this paper: 3 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 1 where Syntology's instrument failed) · 9 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 12 samples from 1 repository, 3 ran (2 with no instrument failure; 1 where Syntology's instrument failed). 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-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

JeremyCJM/CCST officialmentioned on GitHubpytorchCC0-1.0Syntology: 12 samples, 3 ran (1 instrument-failed) · 9 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

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

1ran · our draft was wrong
2ran
9unverified

Licence: 2 of the 12 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from JeremyCJM/CCST. “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”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.

JeremyCJM/CCST official repository 12 samples, 3 ran (1 instrument-failed) · 9 unverified
test_transform in 10 papers style_transfer/AdaIN/CCST_OverallStyleTransfer.py ran · our draft was wrong CC0-1.0 (permissive) here; the stored copy is pointer only · 44b1906941c2c3ed · report fixture: signature size:int/0/int, crop:bool/0/bool · returned Compose · level recorded 2026-09-24
validate in 313 papers reconstruct_img/imagenet_reconstruct.py ran CC0-1.0 (permissive) · 7114e27587038e77 · report fixture: returned float · level recorded 2026-09-25
validate in 313 papers reconstruct_img/imagenet_reconstruct_lpips.py ran CC0-1.0 (permissive) · a5faead5c0894c58 · report fixture: signature val_loader:list/1/tuple, model:callable/0/?, vgg:callable/0/?, criterion:tuple/1/callable, epoch:int/0/int, args:Args/0/?, writer:SummaryWriter/0/? · returned float · level recorded 2026-09-25
calc_mean_std in 64 papers reconstruct_img/imagenet_reconstruct.py unverified CC0-1.0 (permissive) · 2d434599536522ee · report
calc_sum style_transfer/AdaIN/CCST_SingleStyleTransfer.py unverified CC0-1.0 (permissive) · c72f36159b491762 · report
cast_to_image reconstruct_img/imagenet_reconstruct.py unverified CC0-1.0 (permissive) · b1dd5c49ef99e5a4 · report
classifier in 9 papers utils/rsc_utils_densenet.py unverified CC0-1.0 (permissive) · f6256149c0715845 · report
featurizer utils/rsc_utils_densenet.py unverified CC0-1.0 (permissive) · 95bbc26484035020 · report
max_test read_log.py unverified CC0-1.0 (permissive) · 9d5f72743fd7ee70 · report
train_fedprox federated/fed_run.py unverified CC0-1.0 (permissive) here; the stored copy is pointer only · 3c6e4c6321f0a002 · report
train_meta federated/fed_run.py unverified CC0-1.0 (permissive) · 660e83a7dc5113e8 · report
update in 31 papers utils/rsc_utils_densenet.py unverified CC0-1.0 (permissive) · 69f7b99ec0fda254 · report

Tasks

Domain GeneralizationFederated LearningStyle Transfer

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