grance 

Monitoring Solar Neutron events in real time using Neutron Monitor

The monitoring of high resolution NM data is carried out with the aim of selection solar proton and neutron ground level enhancement. Selection of neutron enhancement is difficult because of:
1) those enhancements are very rare and very short (one- several minutes);
2) they should be selected with very low threshold (4
σ);
3)  they may be observed practically at one-two of several low latitude mountain stations;
     It is impossible to pick up such events automatically with certain assurance.
Thus, the system creates a list of stations pretending on the SN registration at every moment.
The system calculates an efficiency of each station in most the favorable moment (close to local noon, accounting inclination of the Earth axis to the equator…) for SN registration. Besides, only the enhancements followed by X-ray flares of >X3 class are accounted.
    This list is useful also giving an imagination about station ‘noise’, i.e. when system gives the pretenders accounting not only real enhancements above 4
σ, but also all apparatus peaks.

The Table is formed for each station, where:
A,%                            CR variation relatively base level of tested station,
Apole
,%                     CR variation relatively base level of polar station
Xray
, MkW/cm2        powerful of the X-Ray flux,
Index
                          indicator:
Index
= 10 – increase in the favorable geometric cone,
Index
=-10 – increase out of favorable cone,
Index
= 01 – Index of control (when an enhancement is observed at the polar station but is not observed at tested station).

An example of Table is presented below.

nSigma=4  <m>=1.4      A: %     sigma  Apole: % sigma Index  Xray,MkW/cm2  ALERT
2009-03-28 10:59:00+00    9.600   14.1  -7.98     -7.4    10  1100000.00000       TEST
2009-03-29 01:23:00+00    2.880    4.2    -0.43    -0.4   -10        0.00373              N 
2009-03-29 06:26:00+00    2.720    4.0     1.28      1.2   -10        0.00373              N 
2009-03-29 09:53:00+00    2.780    4.1     1.66      1.5    10        0.00373              N 
2009-03-29 10:02:00+00    0.00      0.0     4.70      4.3      1        0.00373              POLE
2009-03-29 10:31:00+00    2.730    4.0     0.63      0.6    10        0.00373              N 
2009-03-29 10:37:00+00    3.450    5.1    -0.57    -0.5    10        0.00373              N 
2009-03-29 10:59:00+00   11.820  17.3   -9.97    -9.2    10  1100000.00000        TEST
2009-03-29 14:19:00+00    2.740    4.0     0.67      0.6   -10        0.00373              N 
2009-03-29 16:35:00+00    2.860    4.2     0.96      0.8   -10        0.00373              N 
2009-03-30 02:15:00+00    2.870    4.2     0.52      0.5   -10        0.00373              N 
2009-03-30 06:51:00+00    3.260    4.8     1.60      1.4   -10        0.00373              N 
2009-03-30 10:59:00+00    8.470  12.4    -7.91    -7.0    10  1100000.00000        TEST
2009-03-30 13:23:00+00    3.130    4.6    -0.28    -0.2   -10        0.00373              N 
2009-03-30 13:36:00+00    2.900    4.2     1.00      0.9   -10        0.00373              N 
2009-03-30 13:57:00+00    3.080    4.5    -0.36    -0.3   -10        0.00373              N


When you enter “Example of code” you will get the following list:

2009-03-07  08:49          aatb.01v.txt
2009-03-07   08:49         apty.01v.txt
2009-03-07   08:49         LastData.01c.txt
2009-03-07   08:49         LastData.01v.txt
2009-03-07   07:39         main.pl!
2009-03-07   11:52         name.txt
2009-03-07   08:22         Protokol.txt
2009-03-07   08:49         Stop.txt

There is an example of the working program (main.pl!) and some auxiliary files
for the date shown on the left side of list.
When the program find the increase really identified with the CR enhancement
it should send out warning signal to users.