Index: trunk/MagicSoft/GRB-Proposal/Monitor.tex =================================================================== --- trunk/MagicSoft/GRB-Proposal/Monitor.tex (revision 6617) +++ trunk/MagicSoft/GRB-Proposal/Monitor.tex (revision 6618) @@ -46,5 +46,5 @@ \begin{itemize} -\item {\bf Darkness of the sky}: The Sun has to be below +\item {\bf Darkness of the sky}: The Sun has to be below the astronomical horizon or have a zenith angle larger than 108$^\circ$. \item {\bf Position of GRB}: The GRB equatorial @@ -58,7 +58,8 @@ If one or more of these conditions fail, {\it gspot} enters into a {\color[rgb]{0.9,0.75,0.}\bf Yellow Alarm State} (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 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}. -If all the mentioned conditions are satisfied from the beginning, {\it gspot} enters into a \textcolor{red}{\bf Red Alarm State} immediately.\\ +If all the mentioned conditions are satisfied from the beginning, {\it gspot} enters into a \textcolor{red}{\bf Red Alarm State} immediately. +If 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.\\ -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). +However, 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). For 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. @@ -80,5 +81,5 @@ The CC informs the shift crew about the alert and undertakes -further steps only in case of a \textcolor{red}{\bf red alerts}. +further steps only in case of a \textcolor{red}{\bf red alerts}. In this case, a pop-up window appears with all the alert information received by the burst monitor. @@ -92,5 +93,5 @@ In case of alert -- even if it did not contain the necessary coordinates -- the information is translated into ``human language'' and stored in ASCII files. -At the same time, an e-mail is sent to the MAGIC GRB-mailing list +At the same time, an e-mail is sent to the MAGIC GRB-mailing list {\it grb@mppmu.mpg.de}. @@ -119,6 +120,6 @@ Since July 15$^{\mathrm{th}}$, 2004, {\it gspot} has been working stably at La Palma. It received about 100 alerts from HETE-2 and INTEGRAL, out of which -21 contained GRB's coordinates. Time delays to the onset of the burst -were of the order of several minutes to tens of minutes. The Burst Monitor can be considered stable +21 contained GRB's coordinates. Time delays to the onset of the burst +were of the order of several minutes to tens of minutes. The Burst Monitor can be considered stable since November 2004. Since then we have received the following two significant alerts:\\ @@ -159,48 +160,12 @@ \centering \includegraphics[width=0.7\linewidth]{GCNsatellites.eps} -\caption{Orbits of the \sw (top), \he (center) and \ig (bottom) satellites: The pointed lines -show the orbit while the drawn lines show the horizon of the Sun. Here, a typical night at +\caption{Orbits of the \sw (top), \he (center) and \ig (bottom) satellites: The pointed lines +show the orbit while the drawn lines show the horizon of the Sun. Here, a typical night at La Palma is shown. The \sw satellite passes over the Roque seven times each night.} \label{fig:orbit} \end{figure} -\subsection{Routines to Be Defined} -The Burst Alarm System is currently able to provide the minimum -features needed to point and to observe a GRB. However, in order to improve the efficiency -to point and observe GRBs, several procedures have to be defined: - -\begin{itemize} -\item {\bf Yellow Alarm strategy}: -The strategy to follow a {\bf Yellow Alarm} is not defined yet. -In such a case, the CC does not undertake any steps, -except confirming the alarm notice to the Burst Monitor. We have not -calculated yet if and when the GRB will become observable. -It would make sense to check if we could point to the burst during the period of 5 hours. -The Alarm System should change to a {\bf Red Alarm State}, then. - -\item {\bf Sequence of alerts}: -How to deal with new alerts that are distributed during the time -that {\it gspot} is in alarm state? Currently, {\it gspot} -locks its alert status until it exits the alarm state (see session 2.2). -This feature was implemented to avoid any loss of GRB information. -Such a situation can occur for example if more than one burst alert is sent before -the shift crew launches the CC. -To solve this problem, we will change the {\it gspot} routine -by implementing a list of all available GRB alerts. - - -\par - -If more than one alert is present in the list, the program -will weight the possible GRBs according to the following criteria: -(1) the total time of observability within the canonical 5 hours, -(2) the intensity of the burst and -(3) the time until the GRB becomes observable. -The information of the best GRB will be sent to the CC. - -\end{itemize} - -%%% Local Variables: +%%% Local Variables: %%% mode: latex %%% TeX-master: "GRB_proposal_2005"