Changeset 6804
- Timestamp:
- 03/10/05 15:01:38 (20 years ago)
- Location:
- trunk/MagicSoft/GRB-Proposal
- Files:
-
- 2 added
- 2 edited
-
GRB_proposal_2005.tex (modified) (3 diffs)
-
Monitor.tex (modified) (6 diffs)
-
PreparatoryWork.tex (added)
-
ScientificCase.tex (added)
Legend:
- Unmodified
- Added
- Removed
-
trunk/MagicSoft/GRB-Proposal/GRB_proposal_2005.tex
r6791 r6804 56 56 \title{Proposal for the Observation of Gamma-Ray Bursts with the MAGIC Telescope} 57 57 % {\it \Large DRAFT 2.1 }} 58 \author{N. Galante\\ \texttt{<nicola.galante@pi.infn.it>}\\ 59 D. Bastieri\\ \texttt{<denis.bastieri@pd.infn.it>}\\ 60 M. Garczarczyk\\ \texttt{<garcz@mppmu.mpg.de>}\\ 61 M. Gaug\\ \texttt{<markus@ifae.es>}\\ 62 S. Mizobuchi\\ \texttt{<satoko@mppmu.mpg.de>}\\ 63 } 58 \author{{PI: Nicola Galante, Universit\`a degli Studi di Siena}} 59 % \coauthor{{Co-I:} , {Denis Bastieri} , {Universit\`a degli Studi di Padova}}\\ 60 % & Luigi Peruzzo & Universit\`a degli Studi di Padova\\ 61 % & Riccardo Paoletti & Universit\`a degli Studi di Siena\\ 62 % & Markus Gaug & IFAE\\ 63 % & Markus Garczarczyk & MPI\\ 64 % & Satoko Mizobuchi & MPI\\ 65 % Co-Th: & Steve Shore & Universit\`a degli Studi di Pisa 66 %}\\ 64 67 65 68 \date{March, 2005\\} 66 \TDAScode{MAGIC-TDAS 05-0 2\\ 050314/NGalante}69 \TDAScode{MAGIC-TDAS 05-03\\ 050321/NGalante} 67 70 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 68 71 %% title %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 69 72 \maketitle 70 73 71 %% abstract%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%74 %% Summary %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 72 75 \begin{abstract} 73 We present a detailed strategy for the observation of Gamma Ray Bursts (GRBs) for the first 74 half year of 2005. Because of similarities, X-Ray Flashes (XRFs) and Soft Gamma Repeaters (SGR) 75 are also included in our proposal. 76 All observations will be mainly triggered by alerts from \sw. 76 We ask for observations of Gamma-Ray Bursts (GRBs) for the next six months of year 2005. 77 Therefore we present a detailed strategy for the observation of GRBs. 78 X-Ray Flashes (XRFs) and Soft Gamma Repeaters (SGR) 79 are also included in our proposal, given their similarities to GRB phenomena. 80 All observations will be mainly triggered by \sw. 77 81 In addition, the \he and \ig satellites can contribute a small number of alerts. 78 82 The \sw collaboration expects a total alert rate of about 15 per months -- 79 although with big uncertainties -- out of which 1--2 should be observable due to our 83 although with big uncertainties -- out of which 1--2 should be 84 observable by \ma due to our 80 85 duty cycle. The overlap in sky converages between \sw and \ma seems to be favorable for \ma. 81 As it is still unknown how many alerts \sw will deliver exactly, and how its sky coverage matches82 w ith the one of \ma, we cannot predict the alert frequency now to better than 100\% uncertainty.83 This leads to an {\bf expected observation time of 5$\pm$5 hours per month}.86 As it is still unknown how many alerts \sw will deliver exactly, 87 we cannot predict the alert frequency now to better than 100\% uncertainty. 88 This leads to an expected observation time of 5$\pm$5 hours per month. 84 89 This number includes observation during the moon-time. 85 90 We give a detailed description of the observation procedures in La Palma and … … 90 95 %% contents %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 91 96 \newpage 92 93 97 \thetableofcontents 94 98 95 99 %% body %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 96 \include{ Introduction}100 \include{ScientificCase} 97 101 \include{Alerts} 98 102 \include{Monitor} … … 190 194 \bibitem{GRB030329} Spectra of the burst: http://space.mit.edu/HETE/Bursts/GRB030329/ 191 195 \bibitem{ecl} Private communication with Lorenz E. 192 196 \bibitem{JUAN} Private communication with Cortina J. 193 197 194 198 %References used in Timing -
trunk/MagicSoft/GRB-Proposal/Monitor.tex
r6791 r6804 6 6 7 7 The Burst Alarm System {\it gspot} (Gamma 8 Sources Pointing Trigger) is installed and working in La Palma since last summer.8 Sources Pointing Trigger) is installed and working in La Palma since last Summer. 9 9 It performs a full-time survey of the {\it GRB Coordinates Network} (\g) alerts~\cite{GCN}. 10 10 Different satellite experiments 11 send GRB coordinates to the \g which distributes11 send GRB coordinates to the \g which in its turn broadcasts 12 12 the alerts to registered users. 13 13 The Burst Alarm System is composed of a core program which 14 14 manages the monitoring of the \g and the communication with the Central Control (CC). 15 15 It also handles three communication channels to notice the shifters 16 about an alert. It is a Cbased daemon running 2416 about an alert. It is a c-based daemon running 24 17 17 hours a day on the {\it www} machine, our external server, in a 18 18 {\it stand alone} mode. It does not need to be operated and is … … 27 27 This computer distributes the alerts from the satellite 28 28 experiments through an internet socket connection. {\it gspot} 29 acts as a server while the client, running at the GSFC, 30 manages the communication of the data concerning the GRBs 31 and concerning the status of the connection. \\ 32 33 The format of the data distributed through the \g differ between the individual satellites 34 and the kind of package. Currently three satellites participate in the GRB survey: 29 acts as a server, while the client, running at the GSFC, 30 manages the communication of the GRB data the status.\\ 31 32 The format of the data distributed via \g depends on the broadcasting satellite 33 and on the kind of package. Currently three satellites participate in the GRB survey: 35 34 HETE-2~\cite{HETE}, INTEGRAL~\cite{INTEGRAL} and SWIFT~\cite{SWIFT}. 36 35 The alerts include the UTC, the GRB coordinates (not always), error on coordinates … … 53 52 shining, the maximal zenith angle is reduced to 65$^\circ$. 54 53 \item {\bf Position of Moon}: The angular 55 distance from the GRB to the Moon has to be at least 30$^\circ$. 54 distance from the GRB to the Moon has to be at least 30$^\circ$. This constant 55 value of 30$^\circ$ will change in the future as soon as the camera experts 56 will provide a plot of the safe distance from the Moon vs. Moon's phase. 57 Therefore such dynamical limit for this value will be used. 56 58 \end{itemize} 57 59 58 60 If one or more of these conditions fail, {\it gspot} enters into a 59 {\color[rgb]{0.9,0.75,0.}\bf Yellow Alarm State} (it means the GRB is not observable at the moment). In this case the program saves the alert in a list and calculates when the GRB will become observable for \ma. In the moment when the criteria listed above will be fulfilled for this burst, and the time intervall after the burst onset is smaller than 5 hours, {\it gspot} enters into \textcolor{red}{\bf Red Alarm State}. 61 {\color[rgb]{0.9,0.75,0.}\bf Yellow Alarm State} (it means the GRB is not observable at the moment). 62 In this case the program saves the alert in a list and calculates when the GRB will become observable for \ma. 63 At the moment when the criteria listed above are fulfilled for this burst, and the time intervall 64 after the burst onset is smaller than 5 hours, {\it gspot} enters into \textcolor{red}{\bf Red Alarm State}. 60 65 If all the mentioned conditions are satisfied from the beginning, {\it gspot} enters into Red Alarm State immediately. 61 If more than one alert is recived and the burst can not be observed immediately, the alert information are saved in a list. The software is weightning the alerts in respect to the time when they will became observable, the delay after the onset and the strenght of the burst. The best candidate will be send to the CC when it will enter the Red Alarm state.\\ 62 63 However, 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). 64 For the communication with CC the format defined in~\cite{CONTROL} is used. At the same time, the shifters and the GRB-MAGIC group are contacted. 66 If more than one alert is recived and the burst can not be observed immediately, the alert information are saved in a list. 67 The software weights the alerts according the total amount of time in which 68 the GRB will be observable, the delay of the onset of GRB's observability, 69 the intensisty of the burst and the mean GRB's zenith angle during its 70 period of observability. 71 The best candidate is sent to the CC as soon as {\it gspot} 72 enters the \textcolor{red}{\bf Red Alarm state}, i.e. as soon as such 73 candidate becomes observable.\\ 74 75 However, in case of \textcolor{red}{\bf RED Alarm State}, 76 if the communication with the CC is available then {\it gspot} sends to it 77 the GRB's equatorial coordinates (RA/DEC J2000). 78 For the communication with CC the format defined in~\cite{CONTROL} is used. 79 At the same time, the shifters and the GRB-MAGIC group are contacted. 65 80 66 81 \subsection{The Interface to the Central Control} … … 69 84 When {\it gspot} is not in alarm state, standard packages are continuously exchanged between CC and {\it gspot}. 70 85 These packages contain the main global status of the two subsystems. 71 In case of alert, {\it gspot} starts to send special alert packages to the CC,72 containing information about the GRB and the ``color'' of the alert.86 In case of \textcolor{red}{\bf RED alert}, {\it gspot} starts to send special alert packages to the CC 87 containing information about the GRB. 73 88 The exchange of the alert packages continues until: 74 89 75 90 \begin{itemize} 76 91 \item {\it gspot} receives from the CC the confirmation 77 that the alert notice has been received. (The CC must send back the alert in order 78 to perform a cross-check of the relevant data.) 79 \item the alarm state expires after {\bf 5 hours} 92 that the alert notice has been received (the CC must send back the alert in order 93 to perform a cross-check of the relevant data); 94 \item the \textcolor{red}{\bf RED Alarm state} expires because of the 95 missing of one ore more of the needed criteria mentioned above; 96 \item the alarm state expires after {\bf 5 hours}. 80 97 \end{itemize} 81 98 82 The CC informs the shift crew about the alert and undertakes83 further steps only in case of a \textcolor{red}{\bf red alerts}.99 The CC informs the shift crew about the alert 100 in case of a \textcolor{red}{\bf RED alert}. 84 101 In this case, a pop-up window 85 appears with all the alert information received by the burst monitor.102 appears with all the alert information received by the Burst Monitor. 86 103 The operator has to confirm the notice by closing the pop-up window. 87 104 He can decide whether to stop the current scheduled observation and to point the GRB. 88 A new button will bedisplayed in the CC allowing to point the telescope to105 A new button is so displayed in the CC allowing to point the telescope to 89 106 the GRB coordinates. 90 107 … … 94 111 information is translated into ``human language'' and stored in ASCII files. 95 112 At the same time, an e-mail is sent to the MAGIC GRB-mailing list 96 {\it grb@mppmu.mpg.de}.113 {\it magic\_grb@mppmu.mpg.de}. 97 114 98 115 \subsection{The GRB Web Page} 99 116 100 The status of the GRB Alert System and relevant informations about the last 101 alert are displayed on a separate web page. The page is hosted at the web server in La Palma and can be accessed under:\\ 117 The status of the GRB Alert System and relevant informations about the 118 current and/or the last alert are displayed on a separate web page. 119 The page is hosted at the web server in La Palma and can be accessed under:\\ 102 120 103 121 \qquad \qquad http://www.magic.iac.es/site/grbm/\\ 104 122 105 123 The web page updates itself automatically every 10 seconds. In this way 106 the status of the Burst Alarm System can be checked by the shifters and from outside .124 the status of the Burst Alarm System can be checked by the shifters and from outside too. 107 125 108 126 \subsection{The Acoustic Alert} … … 122 140 21 contained GRB's coordinates. Time delays to the onset of the burst 123 141 were of the order of several minutes to tens of minutes. The Burst Monitor can be considered stable 124 since November 2004. Since then we have received the following twosignificant alerts:\\142 since November 2004. Since then we have received the following four significant alerts:\\ 125 143 126 144 \begin{tabular}{lllcccl} 127 19th & December & 2004 & 1:44 am & INTEGRAL & Zd $\sim 60^\circ$ & time delay 71 sec.\\ 128 28th & January & 2005 & 5:36 am & HETE-2 & Zd $\sim 65^\circ$ & time delay 73 min. \\ \\ 145 19th & December & 2004 & 1:44 am & INTEGRAL & Zd $\sim 60^\circ$ & time delay 71 sec. \\ 146 28th & January & 2005 & 5:36 am & HETE-2 & Zd $\sim 65^\circ$ & time delay 73 min. \\ 147 5th & March & 2005 & 8:42 pm & SWIFT & Zd $\sim 40^\circ$ & time delay 40 sec. \\ 148 5th & March & 2005 & 10:23 pm & SWIFT & Zd $\sim 70^\circ$ & time delay 80 sec. \\\\ 129 149 \end{tabular} 130 150 131 In both cases the weather conditions at La Palma were bad. 151 In the first two cases the weather conditions at La Palma were bad. In the last two 152 a couple of GRBs were detected within two hours by SWIFT. They were observable since 153 their own onset and for all the following 5 hours. The weather was good, but unfortunately 154 the Telescope was off-service because of the exceptional events occured in La Palma 155 during the previous weeks. 132 156 133 157 \subsection{Experience from SWIFT GRBs until now} 134 158 135 According to the \sw home page~\cite{SWIFT}, the satellite has detected 20 GRBs since mid-December last year. The first bursts were detected by chance during the commissioning phase. Since February 15$^{\mathrm{th}}$ the satellite sends burst allerts to the \g in real time. The current sample contains three bursts which could have been observed by \ma. The coordinates of the last burst from February 15$^{\mathrm{th}}$ were send via an alert within few seconds. Also in this cases the weather conditions did not allow any observation.\\ 159 According to the \sw home page~\cite{SWIFT}, the satellite has detected 20 GRBs since mid-December last year. 160 The bursts were detected by chance during the commissioning phase. Since February 15$^{\mathrm{th}}$ 161 the satellite sends burst allerts to the \g in real time. The current sample contains five bursts which could 162 have been observed by \ma. \\ 136 163 137 164 \begin{tabular}{lllcc} 138 165 19th & December & 2004 & 1:42 am & Zd $\sim 65^\circ$ \\ 139 166 26th & December & 2004 & 8:34 pm & Zd $\sim 52^\circ$ \\ 140 15th & Februar & 2005 & 2:33 am & Zd $\sim 17^\circ$ \\ \\ 167 15th & Februar & 2005 & 2:33 am & Zd $\sim 17^\circ$ \\ 168 5th & March & 2005 & 8:42 pm & Zd $\sim 40^\circ$ \\ 169 5th & March & 2005 & 10:23 pm & Zd $\sim 70^\circ$ \\\\ 141 170 \end{tabular} 142 171
Note:
See TracChangeset
for help on using the changeset viewer.
