Index: trunk/MagicSoft/GRB-Proposal/Monitor.tex =================================================================== --- trunk/MagicSoft/GRB-Proposal/Monitor.tex (revision 6117) +++ trunk/MagicSoft/GRB-Proposal/Monitor.tex (revision 6118) @@ -11,15 +11,15 @@ in their wide FOV and send immediately the coordinates of the GRBs to the GCN network. The network send the alerts to registered users and allows other satellites as well as -ground based observatories to observe the GRBs and their afterglows at different wavelenghts. -The Burst Alarm System is composed by a main program - -the core of the system - which acts in two ways: on the +ground based observatories to observe the GRBs and their afterglows at different wavelengths. +The Burst Alarm System is composed by a core program - +which acts in two ways: on the one hand it manages the monitoring of the GCN, on the other it manages the communication with the Central Control (CC). Then it also manages three communication channels to notice the shifters -about a alert situation. The program is called {\it gspot} (Gamma +about an alert situation. The program is called {\it gspot} (Gamma Sources POinting Trigger). It is a C based daemon running 24 -hours a day onto the {\it www} machine, our external server, in a -{\it stand alone} mode. It do not need to be operated and is -fully automatically able to manage network diconnections +hours a day on the {\it www} machine, our external server, in a +{\it stand alone} mode. It does not need to be operated and is +fully automatic. It manages network diconnections within the external net and/or the internal one. @@ -27,22 +27,22 @@ \subsection{The connection to GCN} -The connection to GCN is performed by {\it gspot} through a -TCP/IP connection within a computer at Goddard Space Flight -Center (GSFC). This computer distributes the informations it is recieving from the satellite -experiments through the normal internet socket connection. The {\it gspot} onto our +The connection to {\it GRB Coordinates Network} (GCN)~\cite{GCN} is performed by {\it gspot} through a +TCP/IP connection to a computer at the Goddard Space Flight Center (GSFC). +This computer distributes the information it recieves from the satellite +experiments through the normal internet socket connection. The {\it gspot} on our side acts as a server while the client, running at the GSFC, manages the communication of the data concerning the GRBs and concerning the status of the connnection. \\ -The format of the data distributed through GCN differ between the individual satellites +The format of the data distributed through the GCN differ between the individual satellites and the kind of package. There are three satellites participating in the GRB survey: HETE-2, INTEGRAL and SWIFT. All are sending alerts which include the UTC, coordinates (not always), error on coordinates (not always) and intensity (photon counts) of the burst. -The first notice from HETE-2 and INTEGRAL usually do not include the coordinates. -In only few cases coordinates are distibuted delayed in more refined notices.\\ +The first notices from HETE-2 and INTEGRAL usually do not include the coordinates. +In few cases only coordinates are distributed in more refined notices.\\ -In case of an alert {\it gspot} stores the informations and enters into -an {\bf Alarm State}. The duration of the alert state depends on the following parameters: +In case of an alert {\it gspot} stores the informations and enters +an {\bf Alarm State}. The duration of the alarm state depends on the following parameters: \begin{itemize} @@ -50,14 +50,14 @@ to the astronomical horizon of 108$^\circ$ zenith; \item {\bf position of GRB}, the GRB equatorial -coordinates are transformed into local horizontal coordinates and comparised whether the -GRB zenith angle is smaller than 70$^\circ$; in the case that moon is -shining in the sky, we propose to reduce this zenith limith to 60$^\circ$; -\item {\bf position of moon}, checking whether the angular -distance from the GRB to the moon is at least 30$^\circ$. +coordinates are transformed into local horizontal coordinates. +The resulting GRB zenith angle has to be smaller than 70$^\circ$; in the case that the moon is +shining, this zenith angle limit is reduced to 65$^\circ$; +\item {\bf position of moon} The angular +distance from the GRB to the moon has to be at least 30$^\circ$. \end{itemize} -If one or more of these conditions failed then {\it gspot} +If one or more of these conditions fail, {\it gspot} enters into a {\bf Yellow Alarm State}. It means that the GRB is not observable -at the moment. Currently the program do not calculate if and when the GRB will +at the moment. Currently the program does not calculate if and when the GRB will become observable at La Palma. If all conditions mentioned above are satisfied, @@ -65,21 +65,21 @@ the GRB is considered to be observable at the current time.\\ -In both cases (in RED and YELLOW alarm state) {\it gspot} assamble the communication -with the CC and sends the GRB equatorial coordinates (RA/DEC J2000). -For the communication to CC the format defined in \cite{CONTROL} is used. In the same time +In both cases (in RED and YELLOW alarm state) {\it gspot} establishes the communication +with the Central Control and sends the GRB equatorial coordinates (RA/DEC J2000). +For the communication to CC the format defined in~\cite{CONTROL} is used. In the same time the shifters and the GRB-MAGIC group is contacted in different ways described in the next sessions. \subsection{The interface to the Central Control} -An interface of {\it gspot} sends all the relevant informations about it's status to {\it arehucas}. +An interface to {\it gspot} sends all the relevant information to {\it arehucas}. In the case of {\bf NO Alarm State} the standard packages, containing the main global status of the two subsystems, are continuosly excanged between CC and {\it gspot}. In the alert case {\it gspot} starts to send to CC special alert packages, -containg major informations of the GRB and on the ''colour'' of the alert. +containg information about of the GRB and the ''colour'' of the alert. The exchange of the alert packages continues untill the following steps occur: \begin{itemize} -\item {\it gspot} get from {\it arehucas} the confirmation -that it recived the alert notice; {\it arehucas} must send the alert back in order to +\item {\it gspot} receives from {\it arehucas} the confirmation +that it has received the alert notice; {\it arehucas} must send the alert back in order to perform a crosscheck of the relevant data; \item the alarm state expire after {\bf 5 hours}.