Changeset 6160 for trunk

Timestamp:

01/31/05 20:07:14 (20 years ago)

Author:

garcz

Message:

*** empty log message ***

Location:

trunk/MagicSoft/GRB-Proposal

Files:

• GRB_proposal_2005.tex (modified) (2 diffs)
• Monitor.tex (modified) (2 diffs)
• Strategies.tex (modified) (2 diffs)

trunk/MagicSoft/GRB-Proposal/GRB_proposal_2005.tex

@@ -163 +163 @@
 \bibitem{CONTROL} MAGIC-TDAS 00-07, Cortina J, 2004.
 
+%References used in Strategies
+
+\bibitem{KNEISKE} Kneiske T.M., Bretz T., Mannheim K., Hartmann D.H., A\&A 413, 807, 2004.
+
+%Not used references
 
 \bibitem{PAZCYNSKI} Pazcy\'{n}ski B., Astrophys. J. 308 L43 (1986)
@@ -171 +176 @@
 \bibitem{MESZAROS94} Meszaros P., Rees M., MNRAS 289 L41 (1994)
 
-\bibitem{KNEISKE} Kneiske T.M., Bretz T., Mannheim K., Hartmann D.H., A\&A 413, 807, 2004.
+
 
 \end{thebibliography}

trunk/MagicSoft/GRB-Proposal/Monitor.tex

@@ -148 +148 @@
 \subsection{Comparison between the satellite orbits}
 
-Figure 1 show the difference between the orbits of the \sw, \he and \ig satellite.
+Figure~\ref{fig:orbit} show the difference between the orbits of the \sw, \he and \ig satellite.
 The \sw and \he satellites are situated in a circular orbit with 20.6$^\circ$ respectivly 2$^\circ$ inclination. The revolution period of the \sw and \he satellite add up to 100min. The \ig satellite is situated in an highly eccentric orbit with a revolution period around the Earth of three sidereal days.
 
@@ -159 +159 @@
 \includegraphics[width=0.7\linewidth]{GCNsatellites.eps}
 \caption{Orbits of the \sw, \he and \ig satellites}
-\label{fig:grh}
+\label{fig:orbit}
 \end{figure}
 

trunk/MagicSoft/GRB-Proposal/Strategies.tex

@@ -1 +1 @@
 \section{Proposed Observation Strategies}
 
-First, we make an estimate of how many observations we will perform.\\
+A rough estimate of the needed observation time for GRBs derives
+from the claimed GRB observation frequency of about 150-200 GRBs/year by the \sw
+collaboration~\cite{SWIFT} and the results of the studies on the \ma duty-cycle
+made by Nicola Galante~\cite{NICOLA}.
+Taking into account the calculated duty-cycle of about 10\% and a time intervall of 5 hours
+from the onset of the GRB, we should be able to point about 1--2 GRB/month.
 
-A rough estimate of the needed observation time for GRBs derives 
-from the claimed GRB observation frequency  of about 150-200 GRBs/year by the SWIFT
-collaboration~\cite{SWIFT} and the results of the studies on the MAGIC duty-cycle 
-made by Nicola Galante~\cite{NICOLA}.
-Considering a MAGIC duty-cycle of about 10\% and a tolerance of 5 hours
-to point the GRB, we should be able to point about 1-2 GRB/month. 
+\par
 
+The duty-cycle studies are based on real weather data from the year 2002 taking the following criteria:
 
-Such duty-cycle studies, made before MAGIC started its observations,
-are reliable as long as the considered weather constraints
-(~maximum wind speed of 10m/s, maximum humidity of 80\% and
-darkness at astronomical horizon~) remain similar to the real ones in 2005.
+\begin{itemize}
+\item maximum wind speeds of 10m/s
+\item maximum humidity of 80\%
+\item darkness at astronomical horizon
+\end{itemize}
+
 In these duty-cycle studies also full-moon nights were considered (requiring
-a minimum angular distance of the GRB from the moon of 30$^\circ$~),
-while we propose here to skip the 3-4 full moon nights per month which are not 
-yet under observational control. 
+a minimum angular distance between the GRB and the moon of 30$^\circ$).
 
-This reduction of the real duty-cycle w.r.t. the studies~\cite{NICOLA} 
-gets compensated by the tolerance of 5 hours for considering the alert observable 
-(5 hours more before the beginning of the night 
-are equivalent to an increase of the duty-cycle of about 6 days per month). 
-Observation interruptions due to technical shifts are not considered here. \\
+\par
 
-To conclude, we ask here for about 1-2 nights per month for GRB observations, half-moon nights
-included. 
-Moreover, as the chances go linear with the time that the telescope is able to follow 
-alerts, we ask do an effort as much as possible to maintain the telescope in alarm position 
-EVERY time that a GRB follow-up can be considered possible.
+The 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).
 
+The afterglow observation is equivalent to an increase of the duty-cycle of about 6 days per month.\\
 
-
-\subsection{What to do with the AMC ? }
-
-\ldots {\bf MARKUS G. } \ldots
 
 \subsection{GRB observations in case of moon shine}
@@ -46 +36 @@
 a fast moon-flash shouldn't damage the PMTs, but the behaviour
 of the camera and the Camera Control {\it La Guagua} must
-be tested. On the other hand,, if such test conclude that it is not safe
+be tested. On the other hand, if such test conclude that it is not safe
 to get even a short flash from the moon, the possibility
-to implement a new feature into the Steering System must be considered 
+to implement a new feature into the Steering System must be considered
 which follow a path around the moon while slewing.
+
 \par
-There was a shift observing the Crab-Nebula with half-moon at La Palma in December 2004. 
-The experience was that the nominal High-Voltages could be maintained and gave no 
-currents higher than 2\,$\mu$A. This means that moon-periods can be used for GRB-observations 
-without fundamental modifications except for full-moon periods. We want to stress that 
-these periods increase the chances to catch GRBs by 80\%, even if full-moon observations are excluded~\cite{NICOLA}. 
-It 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.
+
+There was a shift observing the Crab-Nebula with half-moon at La Palma in December 2004.
+The experience was that the nominal HV could be maintained and gave no
+currents higher than 2\,$\mu$A. This means that moon-periods can be used for GRB-observations
+without fundamental modifications except for full-moon periods. We want to stress that
+these periods increase the chances to catch GRBs by 80\%.
+It 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.
+
 \par
-Because the background is higher with moon-light, we want to decrease then the maximun zenith angle from 
-$\theta^{max} = 70^\circ$ to $\theta^{max} = 65^\circ$. 
+
+Because of higher background with moon-light, we suggest to decrease the maximun zenith angle from
+$\theta_{max} = 70^\circ$ to $\theta_{max} = 65^\circ$.
 
 \subsection{Calibration}
 
-For ordinary source observation, the calibration is currently performed in the following way: 
+For ordinary source observation, the calibration is currently performed in the following way:
+
 \begin{itemize}
-\item At the beginning of the source observation, a dedicated pedestal run followed by a calibration run is 
-taken.
+\item At the beginning of the source observation, a dedicated pedestal run followed by a calibration run is taken.
 \item During the data runs, interlaced calibration events are taken at a rate of 50\,Hz.
 \end{itemize}
 
-We 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 valueable time.
+We 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.
 
 \subsection{Determine the maximum zenith angle}
 
-We 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} 
-shows the gamma-ray horizon (GRH) as computed in~\cite{KNEISKE}. The GRH is defined as the 
-gamma-ray energy at which a part of $1/e$ of a hypothiszed mono-energetic flux gets absorbed after 
-travelling a distance of $d$, expressed in redshift $z$ from the earth. One can see that at typical 
+We 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}
+shows the gamma-ray horizon (GRH) as computed in~\cite{KNEISKE}. The GRH is defined as the
+gamma-ray energy at which a part of $1/e$ of a hypothiszed mono-energetic flux gets absorbed after
+travelling a distance of $d$, expressed in redshift $z$ from the earth. One can see that at typical
 GRB distances of $z=1$, all gamma-rays above 100\,GeV get absorbed before they reach the earth. 
 \par