- This topic has 4 replies, 3 voices, and was last updated 11 years, 10 months ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
Example:
Detect: Two sensors within 500km rise out of normal.
Act: Send eMail, send Twitter
I ask because I think
1) the network should act, but
2) I’d understand if one tests his sensor with grandfathers old swiss luminous wristwatch.
So, shall we start a public discussion, how the urad-network should detect and then act on an incident?
Vinz
Yes!
We should start this discussion and decide how to handle such events / alarms.
I think it would be good to have a discussion about this. As I have said to Radu previously, I think it would also be helpful if there was a way for users to flag known anomalous readings due to testing with sources etc so that these are excluded from any alarm algorithm.
so, did it: https://www.uradmonitor.com/topic/how-to-detect-and-act-on-an-incident/
Think peoples tests will normaly not be longer than 6h (-> single sensor alarm).
And messages should not be nervous and excited, but rather technical.
6hr is probably a sensible cut off which will exclude short-term artefacts but will not miss a gradually rising trend due to spreading contamination etc. Maybe it would be possible to implement a moving average function which could trigger an alarm if an agreed threshold or a given rate of increase is acheived from more than 1 adjacent stations.
There is another kind of phenomenon which I am interested in (not accident related) which could be flagged by an alarm and that is brief but very large positive excursions in count rate at multiple stations caused by CME or even GRBs. It would be neat if we could capture these events as they happen.