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

Last change on this file since 6231 was 6219, checked in by gaug, 20 years ago
*** empty log message ***
File size: 6.5 KB
Line 
1\section{Proposed Observation Strategies}
2
3A rough estimate of the needed observation time for GRBs derives
4from the claimed GRB observation frequency of about 150-200 GRBs/year by the \sw
5collaboration~\cite{SWIFT} and the results of the studies on the \ma duty-cycle
6made by Nicola Galante~\cite{NICOLA}.
7Taking into account the calculated duty-cycle of about 10\% and a time intervall of 5 hours
8from the onset of the GRB, we should be able to point about 1--2 GRB/month.
9
10\par
11
12The duty-cycle studies are based on real weather data from the year 2002 taking the following criteria:
13
14\begin{itemize}
15\item maximum wind speeds of 10m/s
16\item maximum humidity of 80\%
17\item darkness at astronomical horizon
18\end{itemize}
19
20In these duty-cycle studies also full-moon nights were considered (requiring
21a minimum angular distance between the GRB and the moon of 30$^\circ$).
22
23\par
24
25The duty-cycle in~\cite{NICOLA} will be increased by taking into account that \ma should also observe the afterglow emission of an burst that occured up to 5 hours before the start of the shift. Different GRB models predict delayed prompt GeV emission as well as acceleration of photons during the afterglows up to the threshold energy of \ma (for more details see chapter 5).
26
27The afterglow observation is equivalent to an increase of the duty-cycle of about 6 days per month.
28
29\subsection{GRB observations in case of moon shine}
30
31{\it gspot} allows only GRBs with an angular distance of $> 30^\circ$ from the moon.
32The telescope's slewing in case of a GRB alert will be done
33without closing the camera lids, so that the camera could be
34flashed by the moon during such a movement. In principle
35a fast moon-flash shouldn't damage the PMTs, but the behaviour
36of the camera and the Camera Control {\it La Guagua} must
37be tested. On the other hand, if such test conclude that it is not safe
38to get even a short flash from the moon, the possibility
39to implement a new feature into the Steering System must be considered
40which follow a path around the moon while slewing.
41
42\par
43
44There was a shift observing the Crab-Nebula with half-moon at La Palma in December 2004.
45The experience was that the nominal HV could be maintained and gave no
46currents higher than 2\,$\mu$A. This means that moon-periods can be used for GRB-observations
47without fundamental modifications except for full-moon periods. We want to stress that
48these periods increase the chances to catch GRBs by 80\%.
49It is therefore mandatory that the shifters keep the camera in fully operational conditions with high-voltages switched on from the beginning of a half-moon night until the end. This includes periods where no other half-moon observations are scheduled. If no other data can be taken during the this periond, the telescope shuld be pointed in the north direction, close to the zenith. This increase the probability to overlap with the FOV of the satellites.
50
51\par
52
53Because of higher background with moon-light, we suggest to decrease the maximun zenith angle from
54$\theta_{max} = 70^\circ$ to $\theta_{max} = 65^\circ$.
55
56\subsection{Active Mirror Control behaviour}
57
58To reduce the time before starting the observation, the use of the look-up tables (LUTs) is necessary.
59Once generated, the {\it AMC} will use the LUTs and automaticaly focus the panels for a given telescope position. The {\it CC} should send the burst coordinates to the {\it Drive} and the {\it AMC} software in the same time. In this way the panels could be focussed already during the telescope movement.
60
61\subsection{Calibration}
62
63For ordinary source observation, the calibration is currently performed in the following way:
64
65\begin{itemize}
66\item At the beginning of the source observation, a dedicated pedestal run followed by a calibration run is taken.
67\item During the data runs, interlaced calibration events are taken at a rate of 50\,Hz.
68\end{itemize}
69
70We would like to continue taking the interlaced calibration events when a GRB alert is launched, but leave out the pedestal and calibration run in order not to loose valuable time.
71
72\subsection{Determine the maximum zenith angle}
73
74We determine the maximum zenith angle for GRB observations by requiring that the overwhelming majority of possible GRBs will have an in principle observable spectrum. Figure~\ref{fig:grh}
75shows the gamma-ray horizon (GRH) as computed in~\cite{KNEISKE,SALOMON}. The GRH is defined as the
76gamma-ray energy at which a part of $1/e$ of a hypothesied mono-energetic flux gets absorbed after
77travelling a distance of $d$, expressed in redshift $z$ from the earth. One can see that at typical
78GRB distances of $z=1$, all gamma-rays above 100\,GeV get absorbed before they reach the earth.
79
80\par
81
82Even the closest GRB with known redshift ever observed, GRB030329~\cite{GRB030329}, lies at a redshift
83of $z=0.1685$. In this case $\gamma$-rays above 200\,GeV get entirely absorbed.
84
85\begin{figure}[htp]
86\centering
87\includegraphics[width=0.85\linewidth]{f4.eps}
88\caption{Gamma Ray Horizon as derived in~\cite{KNEISKE}}
89\label{fig:grh}
90\end{figure}
91
92\par
93
94We assume now a current energy threshold of 50\,GeV for \ma at a zenith angle of
95$\theta = 0$\footnote{As this proposal is going to be reviewed in a couple of months, improvements of the energy threshold will be taken into account then.}. According to~\cite{ecl}, 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 5.6\,TeV at $\theta = 80^\circ$,
103900\,GeV at $\theta = 70^\circ$ and 500\,GeV at $\theta = 65^\circ$.
104Inserting these results into the GRH (figure~\ref{fig:grh}), one gets a maximal observable GRB distance of $z = 0.1$ at $\theta = 70^\circ$ and $z = 0.2$ at $\theta = 65^\circ$.
105We think that the probability for GRBs to occur at these distances is sufficiently small in order to neglect the very difficult observations beyond these limits.
106
107\subsection{In case of follow-up: Next steps}
108
109We propose to analyse the GRB data at the following day in order to tell whether a follow-up observation during the next night is useful. We think that a limit of 3\,$\sigma$ significance should be enough to start such a follow-up observation of the same place. This follow-up observation can then be used in two ways:
110
111\begin{itemize}
112\item In case of a repeated outbursts for a longer time period of direct observation.
113\item In the other case for having off-data at exactly the same sky location.
114\end{itemize}
115
116%%% Local Variables:
117%%% mode: latex
118%%% TeX-master: "GRB_proposal_2005"
119%%% End:
Note: See TracBrowser for help on using the repository browser.