Changeset 6248 for trunk/MagicSoft/GRB-Proposal

Timestamp:

02/03/05 19:17:29 (20 years ago)

Author:

gaug

Message:

*** empty log message ***

File:

• trunk/MagicSoft/GRB-Proposal/Monitor.tex (modified) (6 diffs)

trunk/MagicSoft/GRB-Proposal/Monitor.tex

@@ -21 +21 @@
 
 
-\subsection{The connection to the GCN}
+\subsection{The Connection to the GCN}
 
 The connection to the \g is performed by {\it gspot} through a
@@ -43 +43 @@
 
 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:
+an {\bf Alarm State}. The duration of the alarm depends on the following parameters:
 
 \begin{itemize}
-\item {\bf Darkness of the sky}: Determined from the distance of the sun
-to the astronomical horizon of 108$^\circ$ zenith;
+\item {\bf Darkness of the sky}: The Sun has to be below 
+to the astronomical horizon at 108$^\circ$ zenith.
 \item {\bf Position of GRB}: The GRB equatorial
 coordinates are transformed into local horizontal coordinates.
 The resulting GRB zenith angle has to be smaller than 70$^\circ$. In case that the moon is
-shining, the zenith angle limit is reduced to 65$^\circ$;
+shining, the 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 fail, {\it gspot} enters into a \text
-{yellow}{\bf Yellow Alarm State}. It means that the GRB is not observable at the moment.
-Currently the program does not calculate if and when the GRB will become observable for \ma.
-If all conditions mentioned above are satisfied, {\it gspot} enters into a \textcolor{red}{\bf Red Alarm State}, it means that the GRB is considered to be observable now.\\
-
-In both cases (in \textcolor{red}{RED} and \textcolor{yellow}{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. In the same time
-the shifters and the GRB-MAGIC group is contacted in different ways as described in the next sessions.
-
-\subsection{The interface to the Central Control}
-
-An interface of {\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 continuously exchanged between CC and {\it gspot}.
-In the alert case {\it gspot} starts to send to CC special alert packages,
-containing information about of the GRB and the ''color'' of the alert.
-The exchange of the alert packages continues until the following steps occur:
+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.
+Currently, the program does not calculate if and when the GRB will become observable for \ma.
+If all the  mentioned conditions are satisfied, 
+{\it gspot} enters into a \textcolor{red}{\bf Red Alarm State}, it means that the GRB is considered to be observable now.\\
+
+In both cases (in \textcolor{red}{\bf RED} and {\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 is contacted.
+
+\subsection{The Interface to the Central Control}
+
+An interface of {\it gspot} sends all the relevant information to the CC.
+In the case that {\it gspot} is not in alarm state, 
+the standard packages are continuously exchanged between CC and {\it gspot}, containing the main global status
+of the two subsystems.
+In the alert case, {\it gspot} starts to send  special alert packages to the CC,
+containing information about the GRB and the ''color'' of the alert.
+The exchange of the alert packages continues until:
 
 \begin{itemize}
-\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 cross-check of the relevant data
-\item the alarm state expire after {\bf 5 hours}
+\item {\it gspot} receives from the CC the confirmation
+that the alert notice has been received; The CC must send back the alert in order
+to perform a cross-check of the relevant data.
+\item the alarm state expires after {\bf 5 hours}
 \end{itemize}
 
-At the moment {\it arehucas} informs the shift crew about the alert and takes
-further steps only in case of red alerts. In this case a pop-up window
+The CC informs the shift crew about the alert and undertakes
+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.
 The operator has to confirm the notice by closing the pop-up window.
 He can decide to stop the current scheduled observation and to point the GRB.
-A new button in the CC will be displayed and allows to point the telescope to
-the GRB coordinates by pushing it.
-
-\subsection{GRB archive and emails to the GRB-mailing list}
+A new button will be displayed in the CC and allows to point the telescope to
+the GRB coordinates.
+
+\subsection{GRB Archive and Emails to the GRB-mailing List}
 
 In case of an 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.
-
-\subsection{The GRB web page}
-
-The status of the GRB Alert System and relevant informations about the lastest
-alert are displayed on a separate web page. The page is hosted at the web server in La Palma.
-The address is the following:\\
+At the same time, an e-mail is sent to the MAGIC GRB-mailing list 
+{\it GrB@magic.iac.es}.
+
+\subsection{The GRB Web Page}
+
+The status of the GRB Alert System and relevant informations about the latest
+alert are displayed on a separate web page. The page is hosted at the web server in La Palma a
+and can be accessed under:\\
 
 \qquad \qquad http://www.magic.iac.es/site/grbm/\\
@@ -106 +110 @@
 the status of the Burst Alarm System can be checked by the shifters and from outside.
 
-\subsection{The acoustic alert}
+\subsection{The Acoustic Alert}
 
 A further CC-independent acoustic alarm called {\it phava}
 (PHonetic Alarm for Valued Alerts) will be installed
-in La Palma very soon. It will provide a loud acoustic signal
-even if {\it arehucas} is switched off, so that persons in the counting house
-will be noticed about the alert situation. The signal will be on as long as
-{\it gspot} stays in alarm state, and in any case for a minimum of 1 minute.
-This device feature also a display with the status of the system and the alert.
-
-\subsection{Summary of alerts received until now}
-
-Since July, 15th 2004 {\it gspot} has been working stably at La Palma.
-It received about 100 alerts from HETE-2 and INTEGRAL, out of which
-only 21 contained GRB's coordinates. Time delays
-were in the order of several minutes to tens of minutes. The Burst Monitor can be considered bug-free since
-November 2004. From this moment we received the following two significant alerts:\\
+in La Palma soon. It will provide a loud acoustic signal
+even if the CC is switched off, so that persons in the counting house
+can be noticed about the alert situation. The signal will be on as long as
+{\it gspot} remains in alarm state, and for a minimum of 1 minute.
+The device features also a display with the status of the system and the alert.
+
+\subsection{Summary of Alerts Received Until Now}
+
+Since July 15$^{th}$, 2004, {\it gspot} has been working stably at La Palma.
+It has 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 
+since November, 2004. Since then, we have received the following two significant alerts:\\
 
 \begin{tabular}{lllcccl}
@@ -129 +133 @@
 \end{tabular}
 
-In both cases the weather conditions at La Palma were very bad.
-
-\subsection{Experience of SWIFT GRBs until now}
-
-According to the \sw homepage~\cite{SWIFT} the satellite detected 12 GRBs since mid December last year.
-The bursts were detected by chance during the comissioning phase. The satellite did not send
-the coordinates on time to \g. Anyhow, in the current sample are two bursts
-which in principle could have been observed by \ma:\\
+In both cases the weather conditions at La Palma were bad.
+
+\subsection{Experience from SWIFT GRBs until now}
+
+According to the \sw home page~\cite{SWIFT}, the satellite has detected 12 GRBs since mid-December last year.
+The bursts were detected by chance during the commissioning phase. The satellite did not send
+the coordinates to the \g on time. The current sample contains two bursts
+which could have been observed by \ma:\\
 
 \begin{tabular}{lllcc}
@@ -143 +147 @@
 \end{tabular}
 
-\subsection{Comparison between the satellite orbits}
-
-Figure~\ref{fig:orbit} show the difference between the orbits of the \sw, \he and \ig satellite.
-The \sw and \he satellites are situated in a circular orbit with 20.6$^\circ$ respectivly 2$^\circ$ inclination. The revolution period of the \sw and \he satellite add up to 100min. The \ig satellite is situated in an highly eccentric orbit with a revolution period around the Earth of three sidereal days.
+\subsection{Comparison between the Satellite Orbits}
+
+Figure~\ref{fig:orbit} shows the orbits of the \sw, \he and \ig satellites.
+The \sw and \he satellites are situated in a circular orbit with 
+20.6$^\circ$ and 2$^\circ$ inclination, respectively.
+One revolution of the \sw and \he satellites last about 100\,min. 
+The \ig satellite has a 
+highly eccentric orbit with a revolution period of three sidereal days around the Earth.
 
 \par
 
-It is difficult to make strong conclusions from the individual satellite orbit. The orientation of the satellite FOV is influenced by the scheduled targets. Hovewer, \sw is the satellite with the largest inclination and overlaps mostly with the FOV of \ma. This increases the chance to recive {\bf Red Alarm} from this satellite.
+It is difficult to draw strong conclusions from the individual satellites' orbits. 
+The orientation of the satellites' FOV is influenced by the scheduled targets. 
+However, \sw is the satellite with the largest inclination and overlaps mostly with the FOV of \ma. 
+This increases the chance to receive {\bf Red Alarms} from this satellite.
 
 \begin{figure}[htp]
 \centering
 \includegraphics[width=0.7\linewidth]{GCNsatellites.eps}
-\caption{Orbits of the \sw, \he and \ig satellites}
+\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}
+\subsection{Routines to Be Defined}
 
 The Burst Alarm System is currently able to provide the minimum
@@ -168 +181 @@
 \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 do not
-calculate if and when the GRB will become observable.
-It would make sense to check if during the period of 5 hours we could point to the burst.
-Then, the Alarm System should change to the {\bf Red Alarm State}
-at that time and allow the observation.
+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}
+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 loose of the GRB information.
-Such a situation can occur when for example more than one burst alert is send before
-the shift crew starts the CC. To solve the problem we will change the {\it gspot} routine by implementing a list of the available GRB alerts.
+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 on the following criteria:
+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 send to the CC.
+The information of the best GRB will be sent to the CC.
 
 \end{itemize}