source: trunk/MagicSoft/GRB-Proposal/Requirements.tex@ 6121

Last change on this file since 6121 was 6120, checked in by gaug, 20 years ago
*** empty log message ***
File size: 2.5 KB
Line 
1\section{Requirements to start full GRB observations}
2
3In the previous sessions we described the status and tasks we still plan to do
4in order to complete the GRB Alarm System.
5Parallel to our system also the different subsystems of the MAGIC telescope have
6to implement and test strategies for the GRB survey.
7
8\par
9
10We strongly push the responsible persons of the drive-, camera-, amc- and central
11control subsystems to fulfill the criteria defined in~\cite{design}. We suggest
12to make a one week shift where the experts meet together and test the GRB
13strategies. In order to avoid good observation time we suggest to make the shift
14during the moon period. This shift should take place, in arrangement with the
15different subsystem managers, before April this year. The time limitation is
16based on the moment when SWIFT will start to work fully automatically, sending
17alerts in real time to the ground stations.
18\par
19
20We present a list of tasks that are very crucial for the GRB survey:
21
22\par
23
24\begin{itemize}
25\item {\bf Fast slewing:}\
26
27One of the most important issues is to implement and test the fast movements
28of the telescope. Specially the communication between CC and Cosy has to be arranged for
29the case of fast movements.
30
31\item {\bf Use of look-up tables:}\
32
33The use of look-up tables to correct the mirror focus during the movement to the GRB
34coordinates is advantageous. In the alert situation it is a waste of time if we would have to
35close the camera lids and carry out the full laser adjustment (\~5~min) before starting the observation.
36The reproducibility of the focus with the use of look-up tables has to be proven.
37In order to use the time during the telescope movement for the focussing of the mirrors to the desired
38telescope position, the AMC needs the coordinates immediately. In this case it is necessary to change the protocol between the AMC and CC.
39
40\item {\bf Behaviour of the camera during moon:}\
41
42It has to be checked what happens when during the pointing to a GRB position the telescope move over the
43moon. 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.
44In this case the HV of the PMTs will be reduced automatically and will not increase fast enough for the
45GRB observation.
46
47\end{itemize}
48
49\par
50
51All this issues have to be checked during the suggested shift. The aim would be to send fake alerts to
52the GRB Alarm System and proof the behaviour of all subsystems.
53
54
Note: See TracBrowser for help on using the repository browser.