Q&A: Configuring SurpriseDetector — strategy selection, thresholds, and CognitiveCycle wiring #379
Unanswered
web3guru888
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Configuration and wiring questions for
SurpriseDetector(Phase 13.4, issue #377).Q1: Which detection strategy should I use?
THRESHOLDZ_SCORE(default)IQRISOLATION_FORESTStart with
Z_SCORE(default) unless you have domain knowledge suggesting otherwise.Q2: What Z-score thresholds should I set?
Default values:
z_low=1.5,z_medium=2.5,z_high=3.5(standard deviation multiples).z_lowz_mediumz_highQ3: What does
alert_cooldown_stepsdo?alert_cooldown_steps=50preventsAlertCallbackfrom firing on every single HIGH-severity step during a sustained anomaly burst. After one callback fires at step N, the next callback won't fire until step N+50, even if severity stays HIGH.Increase if callbacks are expensive (e.g. network calls). Decrease for faster alerting.
Q4: How do I wire
SurpriseDetectorintoCognitiveCycle?Q5: What happens if I set
enabled=False?detect()immediately returns aSurpriseEpisodewithseverity=NORMALandscore=0.0, without callingWorldModel.surprise(). No callbacks fire, no curiosity gating occurs. Zero overhead.Q6: Can I register multiple callbacks for the same severity?
Yes. All callbacks registered at or below the episode's severity level fire concurrently:
Q7: How do I visualise surprise detections in Grafana?
Beta Was this translation helpful? Give feedback.
All reactions