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/pybeamline/integration.md
+42-21Lines changed: 42 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,44 +22,65 @@ In this case, we built two logs (`log_original` and `log_after_drift`) which inc
22
22
After that we can use the capabilities of pyBeamline and reactivex to construct a pipeline that produce a sequence of frequencies corresponding to the frequency of directly follows relation `BC` in window with length 40 (which is chosen as all our traces have length 4). Also note that we leverage the fact that in all our events when `B` and `C` appear they are always in the same trace (because of how `log_source` generates the observable). We will later define a function `check_for_drift`:
ops.filter(lambdax: x[0].get_trace_name() == x[1].get_trace_name() and x[0].get_event_name() =="B"and x[1].get_event_name() =="C"),
77
+
ops.count()
78
+
)
79
+
)),
80
+
drift_detector
81
+
).sink(collector)
61
82
```
62
-
With this function available, `check_for_drift` can now be piped to the previous computation. Plotting the frequencies and the concept drifts will result in the following:
83
+
With this class available, `CheckForDrift` can now be piped to the previous computation. Plotting the frequencies and the concept drifts will result in the following:
0 commit comments