Changeset 6158 for trunk/MagicSoft/GRB-Proposal
- Timestamp:
- 01/31/05 19:10:03 (20 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/MagicSoft/GRB-Proposal/Monitor.tex
r6152 r6158 146 146 \end{tabular} 147 147 148 \subsection{Comparison between the satellite orbits} 148 149 150 Figure 1 show the difference between the orbits of the \sw, \he and \ig satellite. 151 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. 152 153 \par 154 155 It is difficult to make strong conclusions from the individual satellite orbit. The orientation of the satellite FOV is influenced by the scheduled targets. Hovewer, \sw is the satellite with the largest inclination and overlaps mostly with the FOV of \ma. This increases the chance to recive {\bf Red Alarm} from this satellite. 156 157 \begin{figure}[htp] 158 \centering 159 \includegraphics[width=0.7\linewidth]{GCNsatellites.eps} 160 \caption{Orbits of the \sw, \he and \ig satellites} 161 \label{fig:grh} 162 \end{figure} 149 163 150 164 \subsection{Routines to be defined} … … 161 175 calculate if and when the GRB will become observable. 162 176 It would make sense to check if during the period of 5 hours we could point to the burst. 163 Then, the Alarm System would change to the {\bf Red Alarm State}177 Then, the Alarm System should change to the {\bf Red Alarm State} 164 178 at that time and allow the observation. 165 179 … … 170 184 This feature was implemented to avoid any loose of the GRB information. 171 185 Such a situation can occur when for example more than one burst alert is send before 172 the shift crew starts the CC. To solve the problem we will change the {\it gspot} implement a list of the available 173 GRB alerts into in which every item expires after: 186 the shift crew starts the CC. To solve the problem we will change the {\it gspot} routine by implementing a list of the available GRB alerts. 174 187 175 \begin{itemize} 176 \item having been noticed by the CC; 177 \item the canonical 5 hours. 178 \end{itemize} 188 \par 179 189 180 190 If more than one alert is present in the list, the program 181 gives a marker to the prioritary GRB -- a decision based on the 182 total time of observability within the canonical 5 hours, 183 on the intensity of the burst and on the time until the GRB becomes observable. 184 Such a marker should reflect our estimation of the chances to observe the GRB.185 The GRB with the highest marker will be noticed to the Central Control.191 will weight the possible GRBs on the following criteria: 192 (1) the total time of observability within the canonical 5 hours, 193 (2) the intensity of the burst and 194 (3) the time until the GRB becomes observable. 195 The information of the best GRB will be send to the CC. 186 196 187 197 \end{itemize}
Note:
See TracChangeset
for help on using the changeset viewer.