Changeset 6158 for trunk/MagicSoft

Timestamp:

01/31/05 19:10:03 (20 years ago)

Author:

garcz

Message:

*** empty log message ***

File:

• trunk/MagicSoft/GRB-Proposal/Monitor.tex (modified) (3 diffs)

trunk/MagicSoft/GRB-Proposal/Monitor.tex

@@ -146 +146 @@
 \end{tabular}
 
+\subsection{Comparison between the satellite orbits}
 
+Figure 1 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.
+
+\par
+
+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.
+
+\begin{figure}[htp]
+\centering
+\includegraphics[width=0.7\linewidth]{GCNsatellites.eps}
+\caption{Orbits of the \sw, \he and \ig satellites}
+\label{fig:grh}
+\end{figure}
 
 \subsection{Routines to be defined}
@@ -161 +175 @@
 calculate if and when the GRB will become observable.
 It would make sense to check if during the period of 5 hours we could point to the burst.
-Then, the Alarm System would change to the {\bf Red Alarm State}
+Then, the Alarm System should change to the {\bf Red Alarm State}
 at that time and allow the observation.
 
@@ -170 +184 @@
 This feature was implemented to avoid any loose of the GRB information.
 Such a situation can occur when for example more than one burst alert is send before
-the shift crew starts the CC. To solve the problem we will change the {\it gspot} implement a list of the available
-GRB alerts into  in which every item expires after:
+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.
 
-\begin{itemize}
-\item having been noticed by the CC;
-\item the canonical 5 hours.
-\end{itemize}
+\par
 
 If more than one alert is present in the list, the program
-gives a marker to the prioritary GRB -- a decision based on the 
-total time of observability within the canonical 5 hours, 
-on the intensity of the burst and on the time until the GRB becomes observable.
-Such a marker should reflect our estimation of the chances to observe the GRB.
-The GRB with the highest marker will be noticed to the Central Control.
+will weight the possible GRBs on the following criteria:
+(1) the total time of observability within the canonical 5 hours,
+(2) the intensity of the burst and
+(3) the time until the GRB becomes observable.
+The information of the best GRB will be send to the CC.
 
 \end{itemize}