Changeset 6123 for trunk


Ignore:
Timestamp:
01/30/05 10:44:32 (20 years ago)
Author:
gaug
Message:
*** empty log message ***
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/MagicSoft/GRB-Proposal/Monitor.tex

    r6120 r6123  
    8686\end{itemize}
    8787
    88 At the moment {\it arehucas} informs the shift crew about the alert and undergo
     88At the moment {\it arehucas} informs the shift crew about the alert and takes
    8989further steps only in case of red alerts. In this case a pop-up window
    9090appears with all the alert information received by the burst monitor.
    9191The operator has to confirm the notice by closing the pop-up window.
    9292He can decide to stop the current scheduled observation and to point the GRB.
    93 A new button in the CC will be displayed and allows to point the the telescope to
     93A new button in the CC will be displayed and allows to point the telescope to
    9494the GRB coordinates by pushing it.
    9595
    9696\subsection{GRB archive and emails to the GRB-mailing list}
    9797
    98 In case of an alert, even if it did not contain the necessary coordinates, the
    99 informations are translated into ''human language'' and stored into ASCII files.
    100 In the same time an e-mail is send to the MAGIC GRB-mailing list.
     98In case of an alert -- even if it did not contain the necessary coordinates -- the
     99information is  translated into ''human language'' and stored in ASCII files.
     100At the same time an e-mail is sent to the MAGIC GRB-mailing list.
    101101
    102102\subsection{The GRB web page}
    103103
    104 The status of the GRB Alert System and relevant informations from the last
    105 alert are displayed on a separate web page. The page is hosted on the web server in La Palma.
     104The status of the GRB Alert System and relevant informations about the lastest
     105alerts are displayed on a separate web page. The page is hosted at the web server in La Palma.
    106106The address is the following:\\
    107107
    108108\qquad \qquad http://www.magic.iac.es/site/grbm/\\
    109109
    110 The web page automatically updates itself every 10 seconds. In this way
    111 the status of the Burst Alarm System can be checked from everywhere.
     110The web page updates itself automatically every 10 seconds. In this way
     111the status of the Burst Alarm System can be checked from outside.
    112112
    113113\subsection{The acoustic alert}
     
    119119will be noticed about the alert situation. The signal will be on as long as
    120120{\it gspot} stays in alarm state, and in any case for a minimum of 1 minute.
    121 This device will keep also a display where to fast check the status
    122 of the system and of the alert.
     121This device will keep also a display to check the status of the system and the alert.
    123122
    124123\subsection{Alerts received until now}
    125124
    126 Since July, 15th 2004 {\it gspot} has been working stable.
    127 It received from HETE-2 and INTEGRAL about 100 alerts, most of them without coordinates.
    128 More precisely only 20 of them contained GRB's coordinates. Time delays
    129 were in most cases very large - in the order of of several minutes or even
    130 tens of minutes. In the beginning the Burst Monitor contained some bugs so that we can not
    131 rely on the alerts until November last year. Since the bugs were fixed we got only one red alert.
    132 This alert came from INTEGRAL with a delay of 71 seconds, it happened
    133 on December 19th at 1:44 am and the GRB zenith angle was $\sim 60^\circ$. It is a pity that the weather
     125Since July, 15th 2004 {\it gspot} has been working stably at La Palma.
     126It received about 100 alerts from HETE-2 and INTEGRAL, out of which
     127only 20 contained GRB's coordinates. Time delays
     128were of very the order of of several minutes or even
     129tens of minutes in most cases. The Burst Monitor can be considered bug-free since
     130November 2004. Since all bugs were fixed we received only one red alert from INTEGRAL on December 19th at 1:44 am
     131with a delay of 71 seconds. The GRB had a zenith angle of $\sim 60^\circ$. It is a pity that the weather
    134132conditions were very bad during this night.
    135133
    136 
    137 \subsection{Tasks to be arranged}
     134\subsection{Procedure to be defined}
    138135
    139136The Burst Alarm System is currently able to provide the minimum
    140 features needed to point and to observe a GRB. Anyway several
    141 things must be defined in order to improve our efficiency
     137features needed to point and to observe a GRB. However, several
     138procedures must be defined in order to improve our efficiency
    142139to point and observe GRBs.
    143140
    144141\begin{itemize}
    145142\item {\bf Yellow Alarm strategy}
    146 First of all the strategy to follow in case of a yellow
    147 alarm, i.e. in case of a not observable GRB, is not defined yet.
     143The strategy to follow a {\bf Yellow Alarm} is not defined yet.
    148144In such a case the CC does not undertake any steps,
    149145except confirming the alarm notice to the Burst Monitor. We do not
    150146calculate if and when the GRB will become observable.
    151147It would make sense to check if during the period of 5 hours we could point to the burst.
    152 Then the Alarm System would change to {\bf Red Alarm State}
     148Then, the Alarm System would change to the {\bf Red Alarm State}
    153149at that time and allow the observation.
    154150
    155 \item {\bf sequence of alerts}
    156 Another procedure that needs to be defined is how to deal with new alerts
    157 that are distributed during the time that {\it gspot} stands
    158 in alarm state. The status of the system now is that {\it gspot}
     151\item {\bf Sequence of alerts}
     152How to deal with new alerts that are distributed during the time
     153that {\it gspot} is in alarm state. Currently, {\it gspot}
    159154locks its alert status until it exits
    160 the alarm state. This feature was implemented in order not to
    161 loose GRB informations due to nasty events.
    162 Such situation can appear ONLY when the CC is switched off so
    163 that it cannot receive the alert. Indeed such situation can
    164 occur when more than one alert happens in the late afternoon or
    165 in the 5 hours before the beginning of the night-shift.
     155the alarm state.
     156This feature was implemented in order not to
     157loose any GRB information.
     158Such a situation can occur when the CC is switched off and thus
     159cannot receive the alert and if more than one alert happens
     160in the late afternoon or in the 5 hours before the beginning
     161of the night-shift.
    166162In such a case we propose
    167 to implement into {\it gspot} a list in which every
    168 item is a GRB's alert that expires after:
     163to implement a list of the available GRB alerts into {\it gspot} in which every
     164item expires after:
    169165
    170166\begin{itemize}
    171 \item having been noticed to the CC;
     167\item having been noticed by the CC;
    172168\item the canonical 5 hours.
    173169\end{itemize}
    174170
    175 If more than one alert is present in the list then the program
    176 gives a mark to the GRB based on the total time of observability
    177 within the canonical 5 hours, on the intensity of the
    178 burst itself and on the time to wait to get the GRB observable.
    179 Such a mark should reflect our estimation in the chances that
    180 we have to observe that GRB.
    181 The GRB with the highest mark will be noticed to the Central Control.
     171If more than one alert is present in the list, the program
     172gives a marker to the prioritary GRB -- a decision based on the
     173total time of observability within the canonical 5 hours,
     174on the intensity of the burst and on the time until the GRB becomes observable.
     175Such a marker should reflect our estimation of the chances to observe the GRB.
     176The GRB with the highest marker will be noticed to the Central Control.
    182177
    183178\end{itemize}
Note: See TracChangeset for help on using the changeset viewer.