Changeset 6125 for trunk/MagicSoft/GRB-Proposal
- Timestamp:
- 01/30/05 11:23:12 (20 years ago)
- Location:
- trunk/MagicSoft/GRB-Proposal
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/MagicSoft/GRB-Proposal/GRB_proposal_2005.tex
r6124 r6125 92 92 %------------------------------------------------------------ 93 93 94 95 96 \section{Calibration and Tests} 97 94 \section{Calibrations} 98 95 {\ldots \it \bf Crab data at different axis-offsets to calibrate off-axis sensitivity \ldots \\} 99 96 -
trunk/MagicSoft/GRB-Proposal/Requirements.tex
r6120 r6125 8 8 \par 9 9 10 We strongly push the responsible persons of the drive-, camera-, amc- and central11 control subsystems to fulfill the criteria defined in~\cite{design}. We suggest12 to make a one week shift where the experts meet togetherand test the GRB10 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 and test the GRB 13 13 strategies. In order to avoid good observation time we suggest to make the shift 14 during themoon period. This shift should take place, in arrangement with the14 during a moon period. This shift should take place, in arrangement with the 15 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 , sending16 based on the moment when SWIFT will start to work fully automatically and send 17 17 alerts in real time to the ground stations. 18 18 \par 19 19 20 We present a list of tasks that are verycrucial for the GRB survey:20 We present now a list of tasks which are crucial for the GRB survey: 21 21 22 22 \par … … 25 25 \item {\bf Fast slewing:}\ 26 26 27 One of the most important issues is to implement and test the fast movements28 of the telescope. Specially the communication between CC and Cosy has to be arranged for27 One of the most important issues is to implement and test the fast slewing capability 28 of the telescope. Especially the communication between CC and Cosy has still to be implemented for 29 29 the case of fast movements. 30 30 … … 32 32 33 33 The use of look-up tables to correct the mirror focus during the movement to the GRB 34 coordinates is advantageous. In the alert situation it is a waste of time if we would have to34 coordinates is desirable. 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 In order to use the time during the telescope movement for the focussing of the mirrors to the desired 38 telescope position, the AMC needs the coordinates immediately. In this case it is necessary to change the protocol between the AMC and CC. 37 In case of using lookup-tables during the slewing, it is necessary to change the protocol between the AMC and CC. 39 38 40 39 \item {\bf Behaviour of the camera during moon:}\ 41 40 42 41 It has to be checked what happens when during the pointing to a GRB position the telescope move over the 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. 42 moon. It is excluded by the GRB Alert System that a burst closer than 30$\deg$ to the moon will be pointed. 43 However, it can happen that during the movement of the telescope the moon will pass the FOV. 44 44 In this case the HV of the PMTs will be reduced automatically and will not increase fast enough for the 45 45 GRB observation. … … 47 47 \end{itemize} 48 48 49 \par50 51 All this issues have to be checked during the suggested shift. The aim would be to send fake alerts to52 the GRB Alarm System and proof the behaviour of all subsystems.53 54 -
trunk/MagicSoft/GRB-Proposal/Tests.tex
r6124 r6125 1 \section{ Calibrations andTests}1 \section{Tests} 2 2 3 {\ldots \it \bf Crab data at different axis-offsets to calibrate off-axis sensitivity \ldots \\} 3 We believe that direct, fast GRBs in the MAGIC FOV are too valuable to allow for any technical or personal problems during the alert. 4 Therefore, we would like to make soon a blind test launching a fake GRB alert from outside 5 {\it without telling the shifters beforehand}. These tests are especially important to train the shift crew and make them aware of the 6 importance of being available and reacting fast in such situations. 4 7 8 9
Note:
See TracChangeset
for help on using the changeset viewer.