1. December 2008NMDB Kiel midterm Meeting1 Checking the simultaneous profiles on 1min data from Lomnický štít during strong CR variations R. Langer, K. Kudela

2. December 2008NMDB Kiel midterm Meeting2 GLE list registered at Lomnicky stit NM station List of GLEs detected by our GLE filter code GLE / GLE onset / GLE max  60 / 13 45 -13 50 / 14 20 -14 25  65 / 11 13 -11 14 / 11 18 -11 19  69 / 06 50 -06 55 / 07 05 -07 10  70 / 02 50 -02 51 / 03 00 -03 01

3. December 2008NMDB Kiel midterm Meeting3 GLE 060

4. December 2008NMDB Kiel midterm Meeting4 GLE 065

5. December 2008NMDB Kiel midterm Meeting5 GLE 069

6. December 2008NMDB Kiel midterm Meeting6 GLE 070

7. December 2008NMDB Kiel midterm Meeting7 ME 12

8. December 2008NMDB Kiel midterm Meeting8 ME 195

9. December 2008NMDB Kiel midterm Meeting9 Method – checking algorithm If next value is bigger than average+standard deviation of previous 10 values we check next three values to same condition, if all four values (T1.. T4) are fulfill condition, we find GLE

10. December 2008NMDB Kiel midterm Meeting10 Table 1. a) of detected increases Method based on 10 points prehistory Checking algorithm condition valid in 5 or more chanels (for condition T1)‏ For nex two point we check if condition was valid in 6 or more chanels (for T2 > T1, T3 > T1)‏ GLE 065 was not detected by the checking algorithm Mistake events are quite rare

11. December 2008NMDB Kiel midterm Meeting11 Table 1. b) of detected increases Same method as in evaluation Table 1. a)‏ From the measured data not corrected to the barometric pressure We think that barometric pressure corected data will give more mistake events (because errors in pressure measurements) during checking procedure, but result was opposite. We find more mistakes events in not corrected data (see line with DOY 341, YY 05 in table right here). Because that we are checking just corrected data.

12. December 2008NMDB Kiel midterm Meeting12 Table 2. of detected increases Method based on 6 points prehistory Checking algorithm condition valid in 5 or more chanels (for condition T1)‏ For nex three points we check if condition was valid in 5 or more chanels (for T2 > T1, T3 > T1, T4 > T1)‏ GLE 070 was not detected by the checking algorithm Mistake events are quite often

13. December 2008NMDB Kiel midterm Meeting13 Table 3. of detected increases Method based on 15 points prehistory Checking algorithm condition valid in 5 or more chanels (for condition T1)‏ For nex three points we check if condition was valid in 5 or more chanels (for T2 > T1, T3 > T1, T4 > T1)‏ GLE 070 was not detected by the checking algorithm Mistake events are quite rare

14. December 2008NMDB Kiel midterm Meeting14 Table 4. of detected increases Method based on 10 points prehistory Checking algorithm condition valid in 5 or more chanels (for condition T1)‏ For next four points we check if condition was valid in 5 or more chanels (for T2 > T1, T3 > T1, T4 > T1, T5 > T1)‏ GLE 060 and GLE 070 were not detected by the checking algorithm Mistake events are very rare.

15. December 2008NMDB Kiel midterm Meeting15 Table 5. of detected increases Method based on 10 points prehistory Checking algorithm condition valid in 5 or more chanels (for condition T1)‏ For next four points we check if condition was valid in 5 or more chanels (for T2 > T1, T3 > T1, T4 > T1)‏ All expected GLE were detected by this checking algorithm This algorithm we recoment to use in the future.

16. December 2008NMDB Kiel midterm Meeting16 Table 6. of detected increases in year 2001 Same algorith like showed for Table 5. But for next four points we check if condition was valid in 5 or more chanels (for T2 > T1, T3 > T2, T4 > T3)‏ This was just test to improve checking method GLE 060 was not detected by this checking algorithm

17. December 2008NMDB Kiel midterm Meeting17 Table 7. of detected increases Same algorith like showed for Table 5. In this case condition was T1 > average + (1.1 * standard deviation) of previous 10 values This was just test to improve checking method GLE 070 was not detected by this checking algorithm

18. December 2008NMDB Kiel midterm Meeting18 Table 8. of detected increases Same algorith like showed for Table 5. Corrected sums was taken like chanels in previous cases Condition was stricter: for T1, T2, T3 and T4 was valid for both „chanels“ simultaneously, (for T2 > T1, T3 > T2, T4 > T3)‏ GLE 065 was not detected Mistake events dont appear

19. December 2008NMDB Kiel midterm Meeting19 Table 9. of detected increases Same algorith like showed for Table 5. Corrected sums was taken like chanels in previous cases Condition for T1, T2, T3 and T4 was valid for all three „chanels“ simultaneously (for T2 > T1, T3 > T2, T4 > T3)‏ This algorithm can be used for real time detection of GLE. Result for calculation with three station taken like chanels are equivalent to results in Table 8.

20. December 2008NMDB Kiel midterm Meeting20 Ground level enhancement real-time alarm based on 8 high latitude NMs including those at high mountain is described by (Kuwabara et al, SW 2006a). Three level alarm system (by number of NMs exceeding threshold value above that of baseline) is suggested. Out of 10 GLEs in 2001-2005 archived data the system produced 9 correct alarms. GLE system gives earlier warning than satellite (SEC/NOAA) alert. Number of minutes by which GLE alert precedes earliest SEC proton alert.

21. December 2008NMDB Kiel midterm Meeting21 END