source: trunk/MagicSoft/GRB-Proposal/Strategies.tex@ 6123

Last change on this file since 6123 was 6120, checked in by gaug, 20 years ago
*** empty log message ***
File size: 5.5 KB
Line 
1\section{Proposed Observation Strategies}
2
3First of all let's consider how many observations are we going to do.\\
4
5A rough estimation of the time consume due to GRB observation comes out
6from the claimed GRB observation by SWIFT, of about 150-200 GRBs/year, and
7the results on the studies on the MAGIC duty-cycle made by
8Nicola Galante \cite{GALANTE} and Satoko Mizobuchi \cite{SATOKO}.
9Considering a MAGIC duty-cycle of about 10\% and a tolerance of 5 hours
10to point the GRB, we should be able to point about 1-2 GRB/month.
11Such duty-cycle studies, made before MAGIC started its observations,
12are reliable as long as weather constraints that were considered
13(~maximum wind speed of 10 m/s, maximum humidity of 80\% and
14darkness at astronomical horizon~) revealed similar to the real ones that
15are affecting MAGIC's observation time. In this duty-cycle study
16also full moon night are considered useful (~just requiring
17a minimum angular distance of the GRB from the moon of 30$^\circ$~),
18while 3-4 nights per month are actually skipped because of full moon,
19but this reduction of the real duty-cycle is about compensated
20by the tolerance of 5 hours for considering the alert
21(~5 hours more before the beginning of the night useful
22for getting GRB's alerts are equivalent to an increase
23of the duty-cycle of about 6 days per month~). Actually
24observation's interruptions due to technical tasks are
25not considered here. \\
26
27All this discussion tells us that, excluding from our
28considerations interruptions of the observing time due to
29technical tasks, MAGIC should employ 1-2 nights per month
30in GRB observations. This means that we must do as much
31as possible to observe them EVERY time that a useful
32alert occurs.
33
34\subsection{What to do with the AMC ? }
35
36\ldots {\bf MARKUS G. } \ldots
37
38\subsection{What to do with moon shine ? }
39
40The telescope's slewing in case of a GRB alert will be done
41without closing the camera lids, so that the camera could be
42flashed by the moon during such movement. In principle
43a fast moon-flash shouldn't damage the PMTs, but the behaviour
44of the camera and of the Camera Control {\it guagua} must
45be tested. On the other hand,, if such test concludes that it is not safe
46at all to get even a short flash from the moon, the possibility
47to implement a new feature into the Steering System which
48follow a different path while slewing must be considered.
49\par
50There was a shift observing the Crab-Nebula with half-moon at La Palma in December 2004.
51The experience was that the nominal High-Voltages could be maintained and gave no
52currents higher than 2\,$\mu$A. This means that moon-periods can be used for GRB-observations
53without fundamental modifications except for full-moon periods. We want to stress that
54these periods increase the chances to catch GRBs by 80\%, even if full-moon observations are excluded
55\cite{NICOLA}.
56It is therefore mandatory that the shifters keep the camera in fully operational conditions with high-voltages
57already switched on from the beginning of a half-moon night until the end.
58\par
59Because the background is higher with moon-light, we want to decrease then the maximun zenith angle from
60$\theta^{max} = 70^\circ$ to $\theta^{max} = 65^\circ$.
61
62\subsection{Calibration }
63
64For ordinary source observation, the calibration is currently performed in the following way:
65\begin{itemize}
66\item At the beginning of the source observation, a dedicated pedestal run following by a calibration run is
67taken.
68\item During the data runs, interlaced calibration events are taken with a rate of 50\,Hz.
69\end{itemize}
70
71We would like to continue taking the interlaced calibration events when a GRB
72alert is launched, but leave out the pedestal and calibration run in order not to loose valueable time.
73
74\subsection{Determine the maximum zenith angle}
75
76We determine the maximum zenith angle by requiring that the overwhelming majority of
77possible GRBs will yield an in principle observable spectrum. Figure~\ref{fig:grh}
78shows the gamma-ray horizon (GRH) as computed in~\cite{KNEISKE}. The GRH is defined as the
79gamma-ray energy at which a part of $1/e$ of a hypothiszed mono-energetic flux is absorbed after
80travelling a distance of $d$, expressed in redshift $z$ from the earth. One can see that at typical
81GRB distances of $z=1$, all gamma-rays above 100\,GeV get absorbed before they reach the earth.
82\par
83Even the closest GRB with known redshift ever observed, GRB030329~\cite{GRB030329}, lies at a redshift
84of $z=0.1685$. In this case, gamma-rays above 200\,GeV get absorbed.
85
86\begin{figure}[htp]
87\centering
88\includegraphics[width=0.85\linewidth]{f4.eps}
89\caption{Gamma Ray Horizon, as derived in~\cite{KNEISKE}}
90\label{fig:grh}
91\end{figure}
92
93\par
94We assume now an energy threshold of 50\,GeV for MAGIC at a zenith angle of $\theta = 0$. According
95to~\cite{eckart}, the energy threshold of a Cherenkov telescope scales with zenith angle like:
96
97\begin{equation}
98E^{thr}(\theta) = E^{thr}(0) \cdot \cos(\theta)^{-2.7}
99\label{eq:ethrvszenith}
100\end{equation}
101
102Eq.~\ref{eq:ethrvszenith} leads to an energy threshold of about 900\,GeV at $\theta = 70^\circ$ and
103500\,GeV at $\theta = 65^\circ$. Inserting these results into the GRH (figure~\ref{fig:grh}), one gets
104a maximal observable GRB distance of $z = 0.1$ and $z = 0.2$, respectively. We think that the probability for
105GRBs to occur at these distances is sufficiently small in order to neglect the very difficult observations
106beyond these limits.
107
108\subsection{In case of follow-up: Next steps}
109
110Analysis during day:
111\par
112If some significance is seen, observe the same position next night to get some OFF-data.
113
114
Note: See TracBrowser for help on using the repository browser.