- Timestamp:
- 01/29/05 17:27:52 (20 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/MagicSoft/GRB-Proposal/Monitor.tex
r6118 r6119 77 77 In the alert case {\it gspot} starts to send to CC special alert packages, 78 78 containg information about of the GRB and the ''colour'' of the alert. 79 The exchange of the alert packages continues until lthe following steps occur:79 The exchange of the alert packages continues until the following steps occur: 80 80 81 81 \begin{itemize} … … 122 122 of the system and of the alert. 123 123 124 \subsection{Alerts recived until lnow}124 \subsection{Alerts recived until now} 125 125 126 126 Since July, 15th 2004 {\it gspot} has been working stable. … … 129 129 were in most cases very large - in the order of of several minutes or even 130 130 tens of minutes. In the beginning the Burst Monitor contained some bugs so that we can not 131 rely on the alerts until lNovember last year. Since the bugs were fixed we got only one red alert.131 rely on the alerts until November last year. Since the bugs were fixed we got only one red alert. 132 132 This alert came from INTEGRAL with a delay of 71 seconds, it happened 133 133 on December 19th at 1:44 am and the GRB zenith angle was $\sim 60^\circ$. Pitty that the weather … … 157 157 that are distributed during the time that {\it gspot} stands 158 158 in alarm state. The status of the system now is that {\it gspot} 159 locks its alert status until lit exits159 locks its alert status until it exits 160 160 the alarm state. This feature was implemented in order not to 161 161 loose GRB informations due to nasty events.
Note:
See TracChangeset
for help on using the changeset viewer.