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
Copy file name to clipboardExpand all lines: docs/about/features_index/workflowinterface.rst
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -236,6 +236,9 @@ Some important points to remember while creating callback function and private a
236
236
- If no Callback Function or private attributes is specified then the Participant shall not have any *private attributes*
237
237
- In above example multiple collaborators have the same callback function or private attributes. Depending on the Federated Learning requirements, user can specify unique callback function or private attributes for each Participant
238
238
- *Private attributes* needs to be set after instantiating the participant.
239
+
- **Known Limitations**: When using a `callable` to initialize *private attributes* that are **not serializable**, users should be aware of following limitations:
240
+
* `checkpoint` should not be enabled with `LocalRuntime`. Users should ensure that default (disabled) setting of checkpoint is used or it is explicitly disabled :code:`flow = FederatedFlow( ..., checkpoint = false)`
241
+
* filtering of attributes (via `include` or `exclude`) cannot be used during the transition from aggregator step to collaborator steps. This limitation applies to **all attributes** if any non-serializable private attribute is present in aggregator. The flow logic must be updated to avoid filtering in steps that transition control from aggregator to collaborators
239
242
240
243
Now let's see how the runtime for a flow is assigned, and the flow gets run:
241
244
@@ -558,6 +561,7 @@ In a distributed environment consisting of Director, Envoys and User Node (where
558
561
559
562
**IMPORTANT**: While this information is useful for debugging, depending on your workflow it may require significant disk space. For this reason, checkpoint is disabled by default.
560
563
564
+
561
565
Future Plans
562
566
==============
563
567
Following functionalities are planned for inclusion in future releases of the Workflow Interface:
assertlen(steps_present_in_cli) ==len(expected_flow_steps), "Number of steps fetched from Datastore through CLI do not match the Expected steps provided"
95
-
assertlen(missing_steps_in_cli) ==0, f"Following steps missing from Datastore: {missing_steps_in_cli}"
96
-
assertlen(extra_steps_in_cli) ==0, f"Following steps are extra in Datastore: {extra_steps_in_cli}"
0 commit comments