Ignore:
Timestamp:
01/30/05 11:23:12 (20 years ago)
Author:
gaug
Message:
*** empty log message ***
Location:
trunk/MagicSoft/GRB-Proposal
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • trunk/MagicSoft/GRB-Proposal/GRB_proposal_2005.tex

    r6124 r6125  
    9292%------------------------------------------------------------
    9393
    94 
    95 
    96 \section{Calibration and Tests}
    97 
     94\section{Calibrations}
    9895{\ldots \it \bf Crab data at different axis-offsets to calibrate off-axis sensitivity  \ldots \\}
    9996
  • trunk/MagicSoft/GRB-Proposal/Requirements.tex

    r6120 r6125  
    88\par
    99
    10 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 together and test the GRB
     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 and test the GRB
    1313strategies. In order to avoid good observation time we suggest to make the shift
    14 during the moon period. This shift should take place, in arrangement with the
     14during a moon period. This shift should take place, in arrangement with the
    1515different subsystem managers, before April this year. The time limitation is
    16 based on the moment when SWIFT will start to work fully automatically, sending
     16based on the moment when SWIFT will start to work fully automatically and send
    1717alerts in real time to the ground stations.
    1818\par
    1919
    20 We present a list of tasks that are very crucial for the GRB survey:
     20We present now a list of tasks which are crucial for the GRB survey:
    2121
    2222\par
     
    2525\item {\bf Fast slewing:}\
    2626
    27 One of the most important issues is to implement and test the fast movements
    28 of the telescope. Specially the communication between CC and Cosy has to be arranged for
     27One of the most important issues is to implement and test the fast slewing capability
     28of the telescope. Especially the communication between CC and Cosy has still to be implemented for
    2929the case of fast movements.
    3030
     
    3232
    3333The 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 to
     34coordinates is desirable. In the alert situation it is a waste of time if we would have to
    3535close the camera lids and carry out the full laser adjustment (\~5~min) before starting the observation.
    3636The 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.
     37In case of using lookup-tables during the slewing, it is necessary to change the protocol between the AMC and CC.
    3938
    4039\item {\bf Behaviour of the camera during moon:}\
    4140
    4241It 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.
     42moon. It is excluded by the GRB Alert System that a burst closer than 30$\deg$ to the moon will be pointed.
     43However, it can happen that during the movement of the telescope the moon will pass the FOV.
    4444In this case the HV of the PMTs will be reduced automatically and will not increase fast enough for the
    4545GRB observation.
     
    4747\end{itemize}
    4848
    49 \par
    50 
    51 All this issues have to be checked during the suggested shift. The aim would be to send fake alerts to
    52 the GRB Alarm System and proof the behaviour of all subsystems.
    53 
    54 
  • trunk/MagicSoft/GRB-Proposal/Tests.tex

    r6124 r6125  
    1 \section{Calibrations and Tests}
     1\section{Tests}
    22
    3 {\ldots \it \bf Crab data at different axis-offsets to calibrate off-axis sensitivity  \ldots \\}
     3We believe that direct, fast GRBs in the MAGIC FOV are too valuable to allow for any technical or personal problems during the alert.
     4Therefore, 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
     6importance of being available and reacting fast in such situations.
    47
     8
     9
Note: See TracChangeset for help on using the changeset viewer.