source: trunk/MagicSoft/GRB-Proposal/Monitor.tex@ 6636

Last change on this file since 6636 was 6619, checked in by garcz, 20 years ago
*** empty log message ***
File size: 9.2 KB
Line 
1\section{The Burst Alarm System at La Palma}
2
3{\bf Current status:}
4
5\par
6
7The Burst Alarm System {\it gspot} (Gamma
8Sources Pointing Trigger) is installed and working in La Palma since last summer.
9It performs a full-time survey of the {\it GRB Coordinates Network} (\g) alerts~\cite{GCN}.
10Different satellite experiments
11send GRB coordinates to the \g which distributes
12the alerts to registered users.
13The Burst Alarm System is composed of a core program which
14manages the monitoring of the \g and the communication with the Central Control (CC).
15It also handles three communication channels to notice the shifters
16about an alert. It is a C based daemon running 24
17hours a day on the {\it www} machine, our external server, in a
18{\it stand alone} mode. It does not need to be operated and is
19fully automatic. It manages network disconnections
20within the external net and/or the internal one.
21
22
23\subsection{The Connection to the GCN}
24
25The connection to the \g is performed by {\it gspot} through a
26TCP/IP connection to a computer at the Goddard Space Flight Center (GSFC).
27This computer distributes the alerts from the satellite
28experiments through an internet socket connection. {\it gspot}
29acts as a server while the client, running at the GSFC,
30manages the communication of the data concerning the GRBs
31and concerning the status of the connection. \\
32
33The format of the data distributed through the \g differ between the individual satellites
34and the kind of package. Currently three satellites participate in the GRB survey:
35HETE-2~\cite{HETE}, INTEGRAL~\cite{INTEGRAL} and SWIFT~\cite{SWIFT}.
36The alerts include the UTC, the GRB coordinates (not always), error on coordinates
37(not always) and intensity (photon counts) of the burst.
38The first notices from HETE-2 and INTEGRAL usually do not include the coordinates.
39In few cases only coordinates are distributed in refined notices.
40The \sw alerts are predicted to arrive with coordinates between 30-80 sec after the onset of the burst.
41The error on the coordinates from the BAT detector will be 4 arcmin which is smaller than the size of one
42inner pixel of the \ma camera.\\
43
44In case of alert, {\it gspot} stores the informations and enters
45an {\bf Alarm State}. The duration of the alarm depends on the following parameters:
46
47\begin{itemize}
48\item {\bf Darkness of the sky}: The Sun has to be below
49the astronomical horizon or have a zenith angle larger than 108$^\circ$.
50\item {\bf Position of GRB}: The GRB equatorial
51coordinates are transformed into local horizontal coordinates.
52The resulting GRB zenith angle has to be smaller than 70$^\circ$. If the Moon is
53shining, the maximal zenith angle is reduced to 65$^\circ$.
54\item {\bf Position of Moon}: The angular
55distance from the GRB to the Moon has to be at least 30$^\circ$.
56\end{itemize}
57
58If one or more of these conditions fail, {\it gspot} enters into a
59{\color[rgb]{0.9,0.75,0.}\bf Yellow Alarm State} (it means the GRB is not observable at the moment). In this case the program saves the alert in a list and calculates when the GRB will become observable for \ma. In the moment when the criteria listed above will be fulfilled for this burst, and the time intervall after the burst onset is smaller than 5 hours, {\it gspot} enters into \textcolor{red}{\bf Red Alarm State}.
60If all the mentioned conditions are satisfied from the beginning, {\it gspot} enters into Red Alarm State immediately.
61If more than one alert is recived and the burst can not be observed immediately, the alert information are saved in a list. The software is weightning the alerts in respect to the time when they will became observable, the delay after the onset and the strenght of the burst. The best candidate will be send to the CC when it will enter the Red Alarm state.\\
62
63However, in both cases (\textcolor{red}{\bf RED} or {\color[rgb]{0.9,0.75,0.}\bf YELLOW} Alarm State), {\it gspot} establishes the communication with the CC and sends the GRB equatorial coordinates (RA/DEC J2000).
64For the communication with CC the format defined in~\cite{CONTROL} is used. At the same time, the shifters and the GRB-MAGIC group are contacted.
65
66\subsection{The Interface to the Central Control}
67
68An interface of {\it gspot} sends all the relevant information to the CC.
69When {\it gspot} is not in alarm state, standard packages are continuously exchanged between CC and {\it gspot}.
70These packages contain the main global status of the two subsystems.
71In case of alert, {\it gspot} starts to send special alert packages to the CC,
72containing information about the GRB and the ``color'' of the alert.
73The exchange of the alert packages continues until:
74
75\begin{itemize}
76\item {\it gspot} receives from the CC the confirmation
77that the alert notice has been received. (The CC must send back the alert in order
78to perform a cross-check of the relevant data.)
79\item the alarm state expires after {\bf 5 hours}
80\end{itemize}
81
82The CC informs the shift crew about the alert and undertakes
83further steps only in case of a \textcolor{red}{\bf red alerts}.
84In this case, a pop-up window
85appears with all the alert information received by the burst monitor.
86The operator has to confirm the notice by closing the pop-up window.
87He can decide whether to stop the current scheduled observation and to point the GRB.
88A new button will be displayed in the CC allowing to point the telescope to
89the GRB coordinates.
90
91\subsection{GRB Archive and Emails to the GRB-mailing List}
92
93In case of alert -- even if it did not contain the necessary coordinates -- the
94information is translated into ``human language'' and stored in ASCII files.
95At the same time, an e-mail is sent to the MAGIC GRB-mailing list
96{\it grb@mppmu.mpg.de}.
97
98\subsection{The GRB Web Page}
99
100The status of the GRB Alert System and relevant informations about the last
101alert are displayed on a separate web page. The page is hosted at the web server in La Palma and can be accessed under:\\
102
103\qquad \qquad http://www.magic.iac.es/site/grbm/\\
104
105The web page updates itself automatically every 10 seconds. In this way
106the status of the Burst Alarm System can be checked by the shifters and from outside.
107
108\subsection{The Acoustic Alert}
109
110A further CC-independent acoustic alarm called {\it phava}
111(PHonetic Alarm for Valued Alerts) will be installed
112in La Palma soon. It will provide a loud acoustic signal
113even if the CC is switched off, so that persons in the counting house
114can be noticed about the alert situation. The signal will be on as long as
115{\it gspot} remains in alarm state for a minimum of one minute.
116The device features also a display with the status of the system and the alert.
117
118\subsection{Summary of Alerts Received Until Now}
119
120Since July 15$^{\mathrm{th}}$, 2004, {\it gspot} has been working stably at La Palma.
121It received about 100 alerts from HETE-2 and INTEGRAL, out of which
12221 contained GRB's coordinates. Time delays to the onset of the burst
123were of the order of several minutes to tens of minutes. The Burst Monitor can be considered stable
124since November 2004. Since then we have received the following two significant alerts:\\
125
126\begin{tabular}{lllcccl}
12719th & December & 2004 & 1:44 am & INTEGRAL & Zd $\sim 60^\circ$ & time delay 71 sec.\\
12828th & January & 2005 & 5:36 am & HETE-2 & Zd $\sim 65^\circ$ & time delay 73 min. \\ \\
129\end{tabular}
130
131In both cases the weather conditions at La Palma were bad.
132
133\subsection{Experience from SWIFT GRBs until now}
134
135According to the \sw home page~\cite{SWIFT}, the satellite has detected 16 GRBs since mid-December last year. The bursts were detected by chance during the commissioning phase. Since February 15$^{\mathrm{th}}$ the satellite sends burst allerts to the \g in real time. The current sample contains three bursts which could have been observed by \ma. The coordinates of the last burst from February 15$^{\mathrm{th}}$ were send via an alert within few seconds. Also in this cases the weather conditions did not allow any observation.\\
136
137\begin{tabular}{lllcc}
13819th & December & 2004 & 1:42 am & Zd $\sim 65^\circ$ \\
13926th & December & 2004 & 8:34 pm & Zd $\sim 52^\circ$ \\
14015th & Februar & 2005 & 2:33 am & Zd $\sim 17^\circ$ \\ \\
141\end{tabular}
142
143\subsection{Comparison between the Satellite Orbits}
144
145Figure~\ref{fig:orbit} shows the orbits of the \sw, \he and \ig satellites.
146The \sw and \he satellites are situated in a circular orbit with
14720.6$^\circ$ and 2$^\circ$ inclination, respectively.
148One revolution of the \sw and \he satellites last about 100\,min.
149The \ig satellite has a
150highly eccentric orbit with a revolution period of three sidereal days around the Earth.
151
152\par
153
154It is difficult to draw strong conclusions from the individual satellites' orbits.
155The orientation of the satellites' FoV is influenced by the scheduled targets.
156However, \sw is the satellite with the largest inclination and overlaps mostly with the FoV of \ma.
157This increases the chance to receive {\bf Red Alarms} from this satellite.
158
159\begin{figure}[htp]
160\centering
161\includegraphics[width=0.7\linewidth]{GCNsatellites.eps}
162\caption{Orbits of the \sw (top), \he (center) and \ig (bottom) satellites: The pointed lines
163show the orbit while the drawn lines show the horizon of the Sun. Here, a typical night at
164La Palma is shown. The \sw satellite passes over the Roque seven times each night.}
165\label{fig:orbit}
166\end{figure}
167
168
169%%% Local Variables:
170%%% mode: latex
171%%% TeX-master: "GRB_proposal_2005"
172%%% End:
Note: See TracBrowser for help on using the repository browser.