Changeset 6548
- Timestamp:
- 02/16/05 19:07:10 (20 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/MagicSoft/GRB-Proposal/Monitor.tex
r6478 r6548 42 42 inner pixel of the \ma camera.\\ 43 43 44 In case of a n alert{\it gspot} stores the informations and enters44 In case of alert, {\it gspot} stores the informations and enters 45 45 an {\bf Alarm State}. The duration of the alarm depends on the following parameters: 46 46 47 47 \begin{itemize} 48 48 \item {\bf Darkness of the sky}: The Sun has to be below 49 t o the astronomical horizon at 108$^\circ$ zenith.49 the astronomical horizon or have a zenith angle larger than 108$^\circ$. 50 50 \item {\bf Position of GRB}: The GRB equatorial 51 51 coordinates are transformed into local horizontal coordinates. 52 The resulting GRB zenith angle has to be smaller than 70$^\circ$. I n case that the moon is53 shining, the zenith angle limitis reduced to 65$^\circ$.54 \item {\bf Position of moon}: The angular52 The resulting GRB zenith angle has to be smaller than 70$^\circ$. If the Moon is 53 shining, the maximal zenith angle is reduced to 65$^\circ$. 54 \item {\bf Position of Moon}: The angular 55 55 distance from the GRB to the moon has to be at least 30$^\circ$. 56 56 \end{itemize} … … 60 60 Currently, the program does not calculate if and when the GRB will become observable for \ma. 61 61 If all the mentioned conditions are satisfied, 62 {\it gspot} enters into a \textcolor{red}{\bf Red Alarm State}, it means that the GRB is considered to be observable now.\\63 64 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).62 {\it gspot} enters into a \textcolor{red}{\bf Red Alarm State}, meaning that the GRB is observable.\\ 63 64 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). 65 65 For the communication with CC the format defined in~\cite{CONTROL} is used. At the same time, 66 66 the shifters and the GRB-MAGIC group is contacted. … … 69 69 70 70 An interface of {\it gspot} sends all the relevant information to the CC. 71 In the case that {\it gspot} is not in alarm state, 72 the standard packages are continuously exchanged between CC and {\it gspot}, containing the main global status 73 of the two subsystems. 74 In the alert case, {\it gspot} starts to send special alert packages to the CC, 75 containing information about the GRB and the ''color'' of the alert. 71 When {\it gspot} is not in alarm state, standard packages are continuously exchanged between CC and {\it gspot}. 72 These packages contain the main global status of the two subsystems. 73 In case of alert, {\it gspot} starts to send special alert packages to the CC, 74 containing information about the GRB and the ``color'' of the alert. 76 75 The exchange of the alert packages continues until: 77 76 … … 88 87 appears with all the alert information received by the burst monitor. 89 88 The operator has to confirm the notice by closing the pop-up window. 90 He can decide to stop the current scheduled observation and to point the GRB.91 A new button will be displayed in the CC a nd allowsto point the telescope to89 He can decide whether to stop the current scheduled observation and to point the GRB. 90 A new button will be displayed in the CC allowing to point the telescope to 92 91 the GRB coordinates. 93 92 94 93 \subsection{GRB Archive and Emails to the GRB-mailing List} 95 94 96 In case of a n alert -- even if it did not contain the necessary coordinates -- the97 information is translated into ''human language'' and stored in ASCII files.95 In case of alert -- even if it did not contain the necessary coordinates -- the 96 information is translated into ``human language'' and stored in ASCII files. 98 97 At the same time, an e-mail is sent to the MAGIC GRB-mailing list 99 98 {\it grb@mppmu.mpg.de}. … … 102 101 103 102 The status of the GRB Alert System and relevant informations about the latest 104 alert are displayed on a separate web page. The page is hosted at the web server in La Palma a103 alerts are displayed on a separate web page. The page is hosted at the web server in La Palma a 105 104 and can be accessed under:\\ 106 105 … … 117 116 even if the CC is switched off, so that persons in the counting house 118 117 can be noticed about the alert situation. The signal will be on as long as 119 {\it gspot} remains in alarm state , andfor a minimum of 1 minute.118 {\it gspot} remains in alarm state for a minimum of 1 minute. 120 119 The device features also a display with the status of the system and the alert. 121 120 122 121 \subsection{Summary of Alerts Received Until Now} 123 122 124 Since July 15$^{ th}$, 2004, {\it gspot} has been working stably at La Palma.125 It hasreceived about 100 alerts from HETE-2 and INTEGRAL, out of which123 Since July 15$^{\mathrm{th}}$, 2004, {\it gspot} has been working stably at La Palma. 124 It received about 100 alerts from HETE-2 and INTEGRAL, out of which 126 125 21 contained GRB's coordinates. Time delays to the onset of the burst 127 126 were of the order of several minutes to tens of minutes. The Burst Monitor can be considered stable … … 137 136 \subsection{Experience from SWIFT GRBs until now} 138 137 139 According to the \sw home page~\cite{SWIFT}, the satellite has detected 16 GRBs since mid-December last year. 140 The bursts were detected by chance during the commissioning phase. Since 15th of February the satellite sends 141 burst allerts to the \g in real time. The current sample contains three bursts 142 which could have been observed by \ma. The coordinates of the last burst from 15th February were send via an 143 alert within few seconds. The weather conditions did not allow any observation in this nights.\\ 138 According to the \sw home page~\cite{SWIFT}, the satellite has detected 12 GRBs since mid-December last year. 139 The bursts were detected by chance during the commissioning phase. The satellite did not send 140 the coordinates to the \g on time. The current sample contains two bursts 141 which could have been observed by \ma:\\ 144 142 145 143 \begin{tabular}{lllcc} 146 144 19th & December & 2004 & 1:42 am & Zd $\sim 65^\circ$ \\ 147 26th & December & 2004 & 8:34 pm & Zd $\sim 52^\circ$ \\ 148 15th & Februar & 2005 & 2:33 am & Zd $\sim 17^\circ$ \\ \\ 145 26th & December & 2004 & 20:34 am & Zd $\sim 52^\circ$ \\ \\ 149 146 \end{tabular} 150 147 … … 177 174 178 175 The Burst Alarm System is currently able to provide the minimum 179 features needed to point and to observe a GRB. However, in order to improve ourefficiency176 features needed to point and to observe a GRB. However, in order to improve the efficiency 180 177 to point and observe GRBs, several procedures have to be defined: 181 178 … … 215 212 %%% TeX-master: "GRB_proposal_2005" 216 213 %%% End: 214 \section{The Burst Alarm System at La Palma} 215 216 {\bf Current status:} 217 218 \par 219 220 The Burst Alarm System {\it gspot} (Gamma 221 Sources Pointing Trigger) is working in La Palma since last summer. 222 It performs a full-time survey of the {\it GRB Coordinates Network} (\g) alerts~\cite{GCN}. 223 Different satellite experiments 224 send GRB coordinates to the \g which distributes 225 the alerts to registered users. 226 The Burst Alarm System is composed of a core program which 227 manages the monitoring of the \g and the communication with the Central Control (CC). 228 It also handles three communication channels to notice the shifters 229 about an alert. It is a C based daemon running 24 230 hours a day on the {\it www} machine, our external server, in a 231 {\it stand alone} mode. It does not need to be operated and is 232 fully automatic. It manages network disconnections 233 within the external net and/or the internal one. 234 235 236 \subsection{The Connection to the GCN} 237 238 The connection to the \g is performed by {\it gspot} through a 239 TCP/IP connection to a computer at the Goddard Space Flight Center (GSFC). 240 This computer distributes the alerts from the satellite 241 experiments through an internet socket connection. {\it gspot} 242 acts as a server while the client, running at the GSFC, 243 manages the communication of the data concerning the GRBs 244 and concerning the status of the connection. \\ 245 246 The format of the data distributed through the \g differ between the individual satellites 247 and the kind of package. Currently, three satellites participate in the GRB survey: 248 HETE-2~\cite{HETE}, INTEGRAL~\cite{INTEGRAL} and SWIFT~\cite{SWIFT}. 249 The alerts include the UTC, the GRB coordinates (not always), error on coordinates 250 (not always) and intensity (photon counts) of the burst. 251 The first notices from HETE-2 and INTEGRAL usually do not include the coordinates. 252 In few cases only coordinates are distributed in refined notices. 253 The \sw alerts are predicted to arrive with coordinates between 30-80 sec after the onset of the burst. 254 The error on the coordinates from the BAT detector will be 4 arcmin which is smaller than the size of one 255 inner pixel of the \ma camera.\\ 256 257 In case of alert, {\it gspot} stores the informations and enters 258 an {\bf Alarm State}. The duration of the alarm depends on the following parameters: 259 260 \begin{itemize} 261 \item {\bf Darkness of the sky}: The Sun has to be below 262 the astronomical horizon or have a zenith angle larger than 108$^\circ$. 263 \item {\bf Position of GRB}: The GRB equatorial 264 coordinates are transformed into local horizontal coordinates. 265 The resulting GRB zenith angle has to be smaller than 70$^\circ$. If the Moon is 266 shining, the maximal zenith angle is reduced to 65$^\circ$. 267 \item {\bf Position of Moon}: The angular 268 distance from the GRB to the moon has to be at least 30$^\circ$. 269 \end{itemize} 270 271 If one or more of these conditions fail, {\it gspot} enters into a 272 {\color[rgb]{0.9,0.75,0.}\bf Yellow Alarm State}: The GRB is not observable at the moment. 273 Currently, the program does not calculate if and when the GRB will become observable for \ma. 274 If all the mentioned conditions are satisfied, 275 {\it gspot} enters into a \textcolor{red}{\bf Red Alarm State}, meaning that the GRB is observable.\\ 276 277 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). 278 For the communication with CC the format defined in~\cite{CONTROL} is used. At the same time, 279 the shifters and the GRB-MAGIC group is contacted. 280 281 \subsection{The Interface to the Central Control} 282 283 An interface of {\it gspot} sends all the relevant information to the CC. 284 When {\it gspot} is not in alarm state, standard packages are continuously exchanged between CC and {\it gspot}. 285 These packages contain the main global status of the two subsystems. 286 In case of alert, {\it gspot} starts to send special alert packages to the CC, 287 containing information about the GRB and the ``color'' of the alert. 288 The exchange of the alert packages continues until: 289 290 \begin{itemize} 291 \item {\it gspot} receives from the CC the confirmation 292 that the alert notice has been received; The CC must send back the alert in order 293 to perform a cross-check of the relevant data. 294 \item the alarm state expires after {\bf 5 hours} 295 \end{itemize} 296 297 The CC informs the shift crew about the alert and undertakes 298 further steps only in case of a \textcolor{red}{\bf red alerts}. 299 In this case, a pop-up window 300 appears with all the alert information received by the burst monitor. 301 The operator has to confirm the notice by closing the pop-up window. 302 He can decide whether to stop the current scheduled observation and to point the GRB. 303 A new button will be displayed in the CC allowing to point the telescope to 304 the GRB coordinates. 305 306 \subsection{GRB Archive and Emails to the GRB-mailing List} 307 308 In case of alert -- even if it did not contain the necessary coordinates -- the 309 information is translated into ``human language'' and stored in ASCII files. 310 At the same time, an e-mail is sent to the MAGIC GRB-mailing list 311 {\it grb@mppmu.mpg.de}. 312 313 \subsection{The GRB Web Page} 314 315 The status of the GRB Alert System and relevant informations about the latest 316 alerts are displayed on a separate web page. The page is hosted at the web server in La Palma a 317 and can be accessed under:\\ 318 319 \qquad \qquad http://www.magic.iac.es/site/grbm/\\ 320 321 The web page updates itself automatically every 10 seconds. In this way 322 the status of the Burst Alarm System can be checked by the shifters and from outside. 323 324 \subsection{The Acoustic Alert} 325 326 A further CC-independent acoustic alarm called {\it phava} 327 (PHonetic Alarm for Valued Alerts) will be installed 328 in La Palma soon. It will provide a loud acoustic signal 329 even if the CC is switched off, so that persons in the counting house 330 can be noticed about the alert situation. The signal will be on as long as 331 {\it gspot} remains in alarm state for a minimum of 1 minute. 332 The device features also a display with the status of the system and the alert. 333 334 \subsection{Summary of Alerts Received Until Now} 335 336 Since July 15$^{\mathrm{th}}$, 2004, {\it gspot} has been working stably at La Palma. 337 It received about 100 alerts from HETE-2 and INTEGRAL, out of which 338 21 contained GRB's coordinates. Time delays to the onset of the burst 339 were of the order of several minutes to tens of minutes. The Burst Monitor can be considered stable 340 since November, 2004. Since then, we have received the following two significant alerts:\\ 341 342 \begin{tabular}{lllcccl} 343 19th & December & 2004 & 1:44 am & INTEGRAL satellite & Zd $\sim 60^\circ$ & Time delay 71 sec.\\ 344 28th & January & 2005 & 5:36 am & HETE-2 satellite & Zd $\sim 65^\circ$ & Time delay 73 min. \\ \\ 345 \end{tabular} 346 347 In both cases the weather conditions at La Palma were bad. 348 349 \subsection{Experience from SWIFT GRBs until now} 350 351 According to the \sw home page~\cite{SWIFT}, the satellite has detected 12 GRBs since mid-December last year. 352 The bursts were detected by chance during the commissioning phase. The satellite did not send 353 the coordinates to the \g on time. The current sample contains two bursts 354 which could have been observed by \ma:\\ 355 356 \begin{tabular}{lllcc} 357 19th & December & 2004 & 1:42 am & Zd $\sim 65^\circ$ \\ 358 26th & December & 2004 & 20:34 am & Zd $\sim 52^\circ$ \\ \\ 359 \end{tabular} 360 361 \subsection{Comparison between the Satellite Orbits} 362 363 Figure~\ref{fig:orbit} shows the orbits of the \sw, \he and \ig satellites. 364 The \sw and \he satellites are situated in a circular orbit with 365 20.6$^\circ$ and 2$^\circ$ inclination, respectively. 366 One revolution of the \sw and \he satellites last about 100\,min. 367 The \ig satellite has a 368 highly eccentric orbit with a revolution period of three sidereal days around the Earth. 369 370 \par 371 372 It is difficult to draw strong conclusions from the individual satellites' orbits. 373 The orientation of the satellites' FOV is influenced by the scheduled targets. 374 However, \sw is the satellite with the largest inclination and overlaps mostly with the FOV of \ma. 375 This increases the chance to receive {\bf Red Alarms} from this satellite. 376 377 \begin{figure}[htp] 378 \centering 379 \includegraphics[width=0.7\linewidth]{GCNsatellites.eps} 380 \caption{Orbits of the \sw (top), \he (center) and \ig (bottom) satellites: The pointed lines 381 show the orbit while the drawn lines show the horizon of the Sun. Here, a typical night at 382 La Palma is shown. The \sw satellite passes over the Roque seven times each night.} 383 \label{fig:orbit} 384 \end{figure} 385 386 \subsection{Routines to Be Defined} 387 388 The Burst Alarm System is currently able to provide the minimum 389 features needed to point and to observe a GRB. However, in order to improve the efficiency 390 to point and observe GRBs, several procedures have to be defined: 391 392 \begin{itemize} 393 \item {\bf Yellow Alarm strategy}: 394 The strategy to follow a {\bf Yellow Alarm} is not defined yet. 395 In such a case, the CC does not undertake any steps, 396 except confirming the alarm notice to the Burst Monitor. We have not 397 calculated yet if and when the GRB will become observable. 398 It would make sense to check if we could point to the burst during the period of 5 hours. 399 The Alarm System should change to a {\bf Red Alarm State}, then. 400 401 \item {\bf Sequence of alerts}: 402 How to deal with new alerts that are distributed during the time 403 that {\it gspot} is in alarm state? Currently, {\it gspot} 404 locks its alert status until it exits the alarm state (see session 2.2). 405 This feature was implemented to avoid any loss of GRB information. 406 Such a situation can occur for example if more than one burst alert is sent before 407 the shift crew launches the CC. 408 To solve this problem, we will change the {\it gspot} routine 409 by implementing a list of all available GRB alerts. 410 411 412 \par 413 414 If more than one alert is present in the list, the program 415 will weight the possible GRBs according to the following criteria: 416 (1) the total time of observability within the canonical 5 hours, 417 (2) the intensity of the burst and 418 (3) the time until the GRB becomes observable. 419 The information of the best GRB will be sent to the CC. 420 421 \end{itemize} 422 423 %%% Local Variables: 424 %%% mode: latex 425 %%% TeX-master: "GRB_proposal_2005" 426 %%% End:
Note:
See TracChangeset
for help on using the changeset viewer.