- Timestamp:
- 01/29/05 17:38:13 (20 years ago)
- Location:
- trunk/MagicSoft/GRB-Proposal
- Files:
-
- 5 edited
-
Introduction.tex (modified) (4 diffs)
-
Monitor.tex (modified) (9 diffs)
-
Requirements.tex (modified) (4 diffs)
-
Strategies.tex (modified) (4 diffs)
-
Timing.tex (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/MagicSoft/GRB-Proposal/Introduction.tex
r6109 r6120 7 7 the objective to turn the telescope to the burst position within 10-30\,sec. 8 8 in order to have a fair chance to detect a burst when the emission is still ongoing. 9 During the com issioning phase it could be proven that that goal was reached.9 During the commissioning phase it could be proven that that goal was reached. 10 10 The telescope is able to turn 180 degrees in azimuth within 20\,sec. and 80 degrees in zenith within 10\,sec.\\ 11 11 12 12 13 13 Very high energy (VHE) GRB observations have the potential to constrain the current GRB models 14 on both the prompt and extende nd phases of GRB emission~\cite{HARTMANN,MANNHEIM,SALOMON}.15 Models based on both internal and external shocks predicts VHE fluence comp erable to,14 on both the prompt and extended phases of GRB emission~\cite{HARTMANN,MANNHEIM,SALOMON}. 15 Models based on both internal and external shocks predicts VHE fluence comparable to, 16 16 or in certain situations stronger than, the keV-MeV radiation, 17 17 with duration ranging from shorter than the keV-MeV burst to extended TeV afterglows~\cite{DERMER, PILLA, ZHANG1}. … … 24 24 in the burst environment~\cite{MESZAROS93,CHIANG,PILLA,ZHANG2}. 25 25 Long-term HE $\gamma$ emission from accelerated protons in the forward-shock has been predicted in~\cite{LI}. 26 This model predicts GeV inverse compton emission even one day after the burst.26 This model predicts GeV inverse Compton emission even one day after the burst. 27 27 Even considering pure electron-synchrotron radiation predicts measurable GeV emission for a significant fraction of GRBs~\cite{ZHANG2}.\\ 28 28 29 GeV emission in GRBs is particular y sensitive to the Lorentz factor and the photon density of the emitting material -29 GeV emission in GRBs is particularly sensitive to the Lorentz factor and the photon density of the emitting material - 30 30 and thus to the distance of the radiating shock from the source - due to the $\gamma~\gamma \rightarrow$ 31 31 \textit{e$^+$~e$^-$} absorption in the emission region. Direct comparison of the prompt GRB flux at $\sim$ 10\,GeV and $\sim$ 100\,keV … … 37 37 each indicating some excess over background but without stringent evidence. 38 38 The only significant detection was performed by EGRET which detected seven GRBs emitting high energy (HE) 39 photons in the 100\,MeV to 18\,dGeV range~\cite{EGRET}. The data shows no evidence of a HE roll over39 photons in the 100\,MeV to 18\,dGeV range~\cite{EGRET}. The data shows no evidence of a HE roll-over 40 40 in the GRB spectrum~\cite{DINGUS}. Recent results indicate that the spectrum of some GRBs contains a very hard, 41 41 luminous, long-duration component~\cite{GONZALES}. 42 42 There have been results suggesting gamma rays beyond the GeV range from the TIBET air shower array 43 43 in coincidence with BATSE bursts~\cite{AMENOMORI}, rapid follow-up observations by the 44 Whipple Air C erenkov Telescope~\cite{CONNAUGHTON1}, and coincident and monitoring studies by HEGRA-AIROBICC~\cite{PADILLA},44 Whipple Air Cherenkov Telescope~\cite{CONNAUGHTON1}, and coincident and monitoring studies by HEGRA-AIROBICC~\cite{PADILLA}, 45 45 Whipple~\cite{CONNAUGHTON2} and the Milagro prototype Milagrito~\cite{MILAGRO}. 46 46 The GRAND array has reported some excess of observed muons during seven BATSE bursts~\cite{GRAND}. … … 65 65 by peak energies below 50~keV and a dominant X-ray fluence. Because of similar properties a connection between XRFs and GRBs is 66 66 suggested. The most popular theories say that XRFs are produced from GRBs observed ''off-axis''. 67 Alternativ ly, an increase of the baryon load within the fireball itself or low efficiency shocks can produce XRFs.67 Alternatively, an increase of the baryon load within the fireball itself or low efficiency shocks can produce XRFs. 68 68 If there is a connection between the XRFs and GRBs, they should originate at rather low redshifts (z $<$ 0.6).\\ 69 69 -
trunk/MagicSoft/GRB-Proposal/Monitor.tex
r6119 r6120 18 18 three communication channels to notice the shifters 19 19 about an alert situation. The program is called {\it gspot} (Gamma 20 Sources P Ointing Trigger). It is a C based daemon running 2420 Sources Pointing Trigger). It is a C based daemon running 24 21 21 hours a day on the {\it www} machine, our external server, in a 22 22 {\it stand alone} mode. It does not need to be operated and is 23 fully automatic. It manages network di connections23 fully automatic. It manages network disconnections 24 24 within the external net and/or the internal one. 25 25 … … 29 29 The connection to {\it GRB Coordinates Network} (GCN)~\cite{GCN} is performed by {\it gspot} through a 30 30 TCP/IP connection to a computer at the Goddard Space Flight Center (GSFC). 31 This computer distributes the information it rec ieves from the satellite31 This computer distributes the information it receives from the satellite 32 32 experiments through the normal internet socket connection. The {\it gspot} on our 33 33 side acts as a server while the client, running at the GSFC, 34 34 manages the communication of the data concerning the GRBs 35 and concerning the status of the conn nection. \\35 and concerning the status of the connection. \\ 36 36 37 37 The format of the data distributed through the GCN differ between the individual satellites … … 74 74 An interface to {\it gspot} sends all the relevant information to {\it arehucas}. 75 75 In the case of {\bf NO Alarm State} the standard packages, containing the main global status 76 of the two subsystems, are continuo sly excanged between CC and {\it gspot}.76 of the two subsystems, are continuously exchanged between CC and {\it gspot}. 77 77 In the alert case {\it gspot} starts to send to CC special alert packages, 78 contain g information about of the GRB and the ''colour'' of the alert.78 containing information about of the GRB and the ''colour'' of the alert. 79 79 The exchange of the alert packages continues until the following steps occur: 80 80 … … 82 82 \item {\it gspot} receives from {\it arehucas} the confirmation 83 83 that it has received the alert notice; {\it arehucas} must send the alert back in order 84 to perform a cross check of the relevant data;84 to perform a cross-check of the relevant data; 85 85 \item the alarm state expire after {\bf 5 hours}. 86 86 \end{itemize} 87 87 88 At the moment {\it arehucas} informs the shift crew about the aler nand undergo88 At the moment {\it arehucas} informs the shift crew about the alert and undergo 89 89 further steps only in case of red alerts. In this case a pop-up window 90 appears with all the alert information rec ived by the burst monitor.90 appears with all the alert information received by the burst monitor. 91 91 The operator has to confirm the notice by closing the pop-up window. 92 92 He can decide to stop the current scheduled observation and to point the GRB. … … 103 103 104 104 The status of the GRB Alert System and relevant informations from the last 105 alert are displayed on a sep erate web page. The page is hosted on the web server in La Palma.105 alert are displayed on a separate web page. The page is hosted on the web server in La Palma. 106 106 The address is the following:\\ 107 107 … … 109 109 110 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 everyw ere.111 the status of the Burst Alarm System can be checked from everywhere. 112 112 113 113 \subsection{The acoustic alert} 114 114 115 A further CC-ind ipendent acoustic alarm called {\it phava}115 A further CC-independent acoustic alarm called {\it phava} 116 116 (~PHonetic Alarm for Valued Alerts~) will be installed 117 117 in La Palma very soon. It will provide a loud acoustic signal … … 122 122 of the system and of the alert. 123 123 124 \subsection{Alerts rec ived until now}124 \subsection{Alerts received until now} 125 125 126 126 Since July, 15th 2004 {\it gspot} has been working stable. 127 It rec ived from HETE-2 and INTEGRAL about 100 alerts, most of them without coordinates.127 It received from HETE-2 and INTEGRAL about 100 alerts, most of them without coordinates. 128 128 More precisely only 20 of them contained GRB's coordinates. Time delays 129 129 were in most cases very large - in the order of of several minutes or even … … 131 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 on December 19th at 1:44 am and the GRB zenith angle was $\sim 60^\circ$. Pitty that the weather134 conditions were very bad dur nig this night.133 on December 19th at 1:44 am and the GRB zenith angle was $\sim 60^\circ$. It is a pity that the weather 134 conditions were very bad during this night. 135 135 136 136 … … 161 161 loose GRB informations due to nasty events. 162 162 Such situation can appear ONLY when the CC is switched off so 163 that it cannot rec ive the alert. Indeed such situation can164 occ our when more than one alert happens in the late afternoon or163 that it cannot receive the alert. Indeed such situation can 164 occur when more than one alert happens in the late afternoon or 165 165 in the 5 hours before the beginning of the night-shift. 166 166 In such a case we propose -
trunk/MagicSoft/GRB-Proposal/Requirements.tex
r6098 r6120 4 4 in order to complete the GRB Alarm System. 5 5 Parallel to our system also the different subsystems of the MAGIC telescope have 6 to implement and test strategies for the GRB surv ay.6 to implement and test strategies for the GRB survey. 7 7 8 8 \par 9 9 10 We strongly push the responsible s of the drive-, camera-, amc- and central11 control subsystems to fullfill the criteria defined in~\cite{design}. We suggest12 to make a one week shift where the experts meet together and test the GRB13 st ategies. In order to avoid good observation timewe suggest to make the shift14 during the moon period. This shift should take place, in arrangement with the15 different subsystem responsibles, before april this year. The time limitation is16 based on the moment when SWIFT will start to work fully automaticly, sending17 al lerts in real time to the groundstations.10 We strongly push the responsible persons of the drive-, camera-, amc- and central 11 control subsystems to fulfill the criteria defined in~\cite{design}. We suggest 12 to make a one week shift where the experts meet together and test the GRB 13 strategies. In order to avoid good observation time we suggest to make the shift 14 during the moon period. This shift should take place, in arrangement with the 15 different subsystem managers, before April this year. The time limitation is 16 based on the moment when SWIFT will start to work fully automatically, sending 17 alerts in real time to the ground stations. 18 18 \par 19 19 20 We present a list of tasks that are very crucial for the GRB surv ay:20 We present a list of tasks that are very crucial for the GRB survey: 21 21 22 22 \par … … 32 32 33 33 The use of look-up tables to correct the mirror focus during the movement to the GRB 34 coordinates is advant egous. In the alert situation it is a vaste of time if we would have to34 coordinates is advantageous. In the alert situation it is a waste of time if we would have to 35 35 close the camera lids and carry out the full laser adjustment (\~5~min) before starting the observation. 36 36 The reproducibility of the focus with the use of look-up tables has to be proven. 37 37 In order to use the time during the telescope movement for the focussing of the mirrors to the desired 38 telescope posit on, the AMC needs the coordinates immediately. In this case it is necessary to change the protocol between the AMC and CC.38 telescope position, the AMC needs the coordinates immediately. In this case it is necessary to change the protocol between the AMC and CC. 39 39 40 40 \item {\bf Behaviour of the camera during moon:}\ … … 42 42 It has to be checked what happens when during the pointing to a GRB position the telescope move over the 43 43 moon. It is excluded by the GRB Alert System that a burst closer than 30$\deg$ to the moon will be pointed. However it is not prevented that during the movement of the telescope the moon will pass the FOV. 44 In this case the HV of the PMTs will be reduced automatically and will not increase fast enough tfor the44 In this case the HV of the PMTs will be reduced automatically and will not increase fast enough for the 45 45 GRB observation. 46 46 … … 49 49 \par 50 50 51 All this issues have to be checked during the suggested shift. The aim would be to send fake al lerts to52 the GRB Alarm System and proo vethe behaviour of all subsystems.51 All this issues have to be checked during the suggested shift. The aim would be to send fake alerts to 52 the GRB Alarm System and proof the behaviour of all subsystems. 53 53 54 54 -
trunk/MagicSoft/GRB-Proposal/Strategies.tex
r6105 r6120 7 7 the results on the studies on the MAGIC duty-cycle made by 8 8 Nicola Galante \cite{GALANTE} and Satoko Mizobuchi \cite{SATOKO}. 9 Considering a MAGIC duty-cycle of about 10\% and a tol lerance of 5 hours9 Considering a MAGIC duty-cycle of about 10\% and a tolerance of 5 hours 10 10 to point the GRB, we should be able to point about 1-2 GRB/month. 11 11 Such duty-cycle studies, made before MAGIC started its observations, 12 12 are reliable as long as weather constraints that were considered 13 (~maximum wind 'sspeed of 10 m/s, maximum humidity of 80\% and13 (~maximum wind speed of 10 m/s, maximum humidity of 80\% and 14 14 darkness at astronomical horizon~) revealed similar to the real ones that 15 15 are affecting MAGIC's observation time. In this duty-cycle study 16 also full moon night are considered useful l(~just requiring16 also full moon night are considered useful (~just requiring 17 17 a minimum angular distance of the GRB from the moon of 30$^\circ$~), 18 18 while 3-4 nights per month are actually skipped because of full moon, 19 19 but this reduction of the real duty-cycle is about compensated 20 by the tol lerance of 5 hours for considering the alert21 (~5 hours more before the beginning of the night useful l20 by the tolerance of 5 hours for considering the alert 21 (~5 hours more before the beginning of the night useful 22 22 for getting GRB's alerts are equivalent to an increase 23 23 of the duty-cycle of about 6 days per month~). Actually … … 29 29 technical tasks, MAGIC should employ 1-2 nights per month 30 30 in GRB observations. This means that we must do as much 31 as possible to observe them EVERY time that a useful l32 alert occ ours.31 as possible to observe them EVERY time that a useful 32 alert occurs. 33 33 34 34 \subsection{What to do with the AMC ? } … … 43 43 a fast moon-flash shouldn't damage the PMTs, but the behaviour 44 44 of the camera and of the Camera Control {\it guagua} must 45 be tested. O therway, if such test concludes that it is not safe45 be tested. On the other hand,, if such test concludes that it is not safe 46 46 at all to get even a short flash from the moon, the possibility 47 to implement a new feature into the Steering System w ich48 follow a different path while s elwing must be considered.47 to implement a new feature into the Steering System which 48 follow a different path while slewing must be considered. 49 49 \par 50 50 There was a shift observing the Crab-Nebula with half-moon at La Palma in December 2004. … … 103 103 500\,GeV at $\theta = 65^\circ$. Inserting these results into the GRH (figure~\ref{fig:grh}), one gets 104 104 a maximal observable GRB distance of $z = 0.1$ and $z = 0.2$, respectively. We think that the probability for 105 GRBs to occur at these distances is suffi ently small in order to neglect the very difficult observations105 GRBs to occur at these distances is sufficiently small in order to neglect the very difficult observations 106 106 beyond these limits. 107 107 -
trunk/MagicSoft/GRB-Proposal/Timing.tex
r6001 r6120 14 14 \par 15 15 In~\cite{DERMER}, two peaks in the GeV light curve are calculated. An early maximum coincident 16 with the MeV eak is the high-enerygextension of the synchrotron component, some seconds16 with the MeV peak is the high-energy extension of the synchrotron component, some seconds 17 17 after the burst onset. The second maximum peaking at $\approx$ 1.5 hours is due primarily to 18 18 SSC radiation with significant emission of up to $10^5$ sec. ($\approx 25$ hours) after the burst.
Note:
See TracChangeset
for help on using the changeset viewer.
