You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IIn the Docs, "Customizing Client Configurations"
In some cases, it may be necessary to send different configurations to individual clients. To achieve this, you can create a custom strategy by extending a built-in one, such as FedAvg:
# Modify configuration for a specific client
client_proxy, fit_ins = client_instructions[0]
fit_ins.config["special_key"] = "special_value"
return client_instructions
How can we ensure that the special_key and special_value can be correctly configured for a specific client? Relying solely on client_instructions[0] is insufficient to determine which client exactly the [0] represents.
The text was updated successfully, but these errors were encountered:
WLBRich
changed the title
How can we ensure that the special_key and special_value can be correctly configured for a specific client? Relying solely on client_instructions[0] is insufficient to determine which client exactly the [0] represents.
How can we ensure that the special_key and special_value can be correctly configured for a specific client?
Mar 20, 2025
What is your question?
IIn the Docs, "Customizing Client Configurations"
In some cases, it may be necessary to send different configurations to individual clients. To achieve this, you can create a custom strategy by extending a built-in one, such as FedAvg:
Example: Client-Specific Configuration
from flwr.server.strategy import FedAvg
class CustomClientConfigStrategy(FedAvg):
def configure_fit(self, server_round, parameters, client_manager):
client_instructions = super().configure_fit(
server_round, parameters, client_manager
)
How can we ensure that the special_key and special_value can be correctly configured for a specific client? Relying solely on client_instructions[0] is insufficient to determine which client exactly the [0] represents.
The text was updated successfully, but these errors were encountered: