Changeset 5968 for trunk/MagicSoft

Timestamp:

01/24/05 15:11:31 (20 years ago)

Author:

gaug

Message:

*** empty log message ***

Location:

trunk/MagicSoft

Files:

• GRB-Proposal/GRB_proposal_2005.tex (modified) (4 diffs)
• GRB-Proposal/Introduction.tex (added)
• GRB-Proposal/Monitor.tex (added)
• GRB-Proposal/Requirements.tex (added)
• GRB-Proposal/Strategies.tex (added)
• GRB-Proposal/Timing.tex (added)
• Mars/Changelog (modified) (1 diff)
• Mars/msignal/MExtractTime.cc (modified) (1 diff)
• Mars/msignal/MExtractor.cc (modified) (1 diff)

trunk/MagicSoft/GRB-Proposal/GRB_proposal_2005.tex

@@ -54 +54 @@
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 \title{Proposal for the Observation of Gamma-Ray Bursts with the MAGIC Telescope \\
-     {\it \Large DRAFT 0.0 }}
+     {\it \Large DRAFT 1.0 }}
 \author{  N. Galante\\ \texttt{<nicola.galante@pd.infn.it>}\\
   M. Garczarczyk\\ \texttt{<garcz@mppmu.mpg.de>}\\
@@ -61 +61 @@
 }
   
-\date{December, 2003\\}
-\TDAScode{MAGIC-TDAS 02-??\\ 0312??/NGalante}
+\date{January, 2005\\}
+\TDAScode{MAGIC-TDAS 05-??\\ 0312??/NGalante}
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 %% title %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -70 +70 @@
 \begin{abstract}
 We give a detailed plan for the observation of Gamma Ray Bursts for the year
-2004. All observations will be triggered by alerts of the satellites \he, \ig,  
-\sw or by other circulars by the \g. Based on \he experience from the year 2002, 
-we expect an alert rate of a total of about 50 per year out of which only about 20 will 
-be followed by a position. 
-%FIXME
-{\it \bf THIS HAS STILL TO BE UPDATED FOR 2003 !!}
-The majority of these alerts will be based on ground analysis and 
-arrive with a delay of about an hour or more. 
+2005. All observations will be triggered mainly by alerts of the satellites \he, \ig   
+and above all \sw. we expect an alert rate of a total of about 
+\par
+\ldots HOW MANY??? \ldots
+\par
+per year out of which only about 
+\par
+\ldots HOW MANY??? \ldots
+\par
+will be followed by a position. 
+We give a detailed description of the observation procedures in La Palma and 
+propose to review the situation in half a year from now.
 \end{abstract}
 
 %% contents %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-%\thetableofcontents
+\thetableofcontents
 
 \newpage
 
 %% body %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\include{Introduction}
+\include{Alerts}
+\include{Monitor}
+\include{Strategies}
+\include{Timing}
+\include{Requirements}
+
 
 %------------------------------------------------------------
-\section{Introduction}
-The MAGIC telescope has been designed especially light with a special focus on 
-being able to react fastly to GRB alerts from the satellites. 
-In \cite{design} and~\cite{PETRY}, 
-the objective was set to turn the telescope to the burst position in 10-30~s 
-in order to have a fair chance of detecting a burst with the MAGIC telescope. 
-The current possible value is 20 sec. for full turn-around 
-%FIXME
-{\it \bf THIS HAS TO BE CHECKED FROM THOMAS B. !!}
-\par
-Several attempts have been made in the past to observe GRBs at energies 
-from the GeV range upwards each indicating some excess over background but 
-without stringent evidence. The only secured detection was performed by EGRET 
-which detected seven GRBs emitting high energy photons in the 
-100~MeV to 18~GeV range~\cite{EGRET}. There have been 
-results suggesting gamma rays beyond the GeV range from the TIBET array~\cite{TIBET} and 
-from HEGRA-AIROBICC~\cite{HEGRA}. Evidence for TeV emission of one burst was claimed by 
-the MILAGRITO experiment~\cite{MILAGRO}. Recently, the GRAND array has reported some 
-excess of observed muons during seven BATSE bursts~\cite{GRAND}. In this context, note 
-especially a recent publication from the TASC detector on \eg~\cite{TASC}, 
-finding a high-energy spectral 
-component presumably due to ultra-relativistic acceleration of hadrons and 
-producing a spectral index of $-1$ with no cut-off up to the detector limit (200 MeV). 
-\par
-The nowadays most widely accepted model for gamma emission from GRB suggests a bursts 
-environment involving collisions of an ultra-relativistic e$^+$-e$^-$ 
-plasma fireball~\cite{PAZCYNSKI,GOODMAN,SARI}. These fireballs may produce 
-low-energy gamma rays either by ``internal'' collisions of multiple 
-shocks~\cite{XU,REES} or by ``external'' collisions of a single shock 
-with the ambient circum burst medium (CBM)~\cite{MESZAROS94}. 
-\par
-In many publications, 
-the possibility that more energetic gamma-rays come along with the (low-energy) gamma-ray 
-burst, have been explored.
-Proton-synchrotron emission~\cite{TOTANI} have 
-been suggested as well as photo-pion production~\cite{WAXMAN,BAHCALL,BOETTCHER} 
-and inverse-Comption 
-scattering in the burst environment~\cite{MESZAROS93,CHIANG,PILLA,ZHANG}.
-Long-term high-energy gamma emission from accelerated protons in forward-shock 
-has been predicted in~\cite{LI}.
-Even considering pure electron-synchrotron radiation predicts measurable GeV emission for a 
-significant fraction of GRBs~\cite{ZHANG}.
-Implications of the observation of a high-energy gamma-ray component on 
-distance scale, energy production in the GRB and distinction between internal and 
-external shock models have been treated in~\cite{HARTMANN,MANNHEIM,SALOMON,PRIMACK}.
-\par
-In the year 2004, mainly three satellites will produce the bulk of the GRB alerts: The \he 
-satellite, launched in October 2000, the \ig satellite, launched October 2002 and the 
-\sw satellite, scheduled for launch in May, 2004.
-\par
-% HERE
-We will give an overview of the types of alarms, we expect from the three satellites 
-and add then our proposal for observation strategies. Note that while there is already some 
-experience accumulated from the \he and \ig alarms, we do not know yet how \sw will perform
-since it is still not launched. Because the observation of GRBs will differ 
-from conventional observations in several aspects, we also propose a detailed plan to test
- and calibrate the system in order to meet our purposes. 
-\par
-{\ldots \it \bf THIS IS TO BE CHECKED BY NICOLA G. !! \ldots \\}
-\par
-Concerning estimates about the MAGIC observability of GRBs, a very detailed study
-of GRB spectra obtained from the third and fourth \ba catalogue has been made 
-in~\cite{ICRC,NICOLA}. The spectra were extrapolated to \ma energies with a simple continuation 
-of the observed high-energy power law behaviour and the calculated fluxes compared 
-with \ma sensitivities. Setting conservative cuts on observation times and significances, 
-and assuming an energy threshold of 15~GeV, a GRB detection rate of $0.5--2$ per year
-was obtained for an assumed observation delay of 15~sec. and the \sw GRB trigger rate ($\sim 100/year$).
-
-
-\section{\he Alarms}
-
-{\it \bf THIS HAS TO BE UPDATED TO 2003 !!}
-
-The HETE mission has three instruments on board which can generate burst triggers: 
-Fregate, the WXM, and the SXC. 
-Fregate data are examined in two broad energy channels: 
-5-80 keV and 30-400 keV. 
-The WXM data are from 2-30 keV, 
-and the SXC data are from 1.5 to 12 keV. 
-\par
-The Fregate data are searched for counts excesses on four different timescales: 
-20 ms, 160 ms, 1.3 s, and 5.2 s. 
-The threshold for a count excess to be considered significant is generally around 5 sigma. 
-Such an excess must be seen in two of the four Fregate detectors on the same timescale 
-for a burst to be considered real. 
-\par
-The WXM data are examined on multiple timescales between 80 ms and 10 s. 
-The thresholds are all near 5 sigma. This analysis is done on one of the on-board transputers.
-\par
-Fregate data are also analyzed on multiple timescales in a manner identical 
-to that for the WXM data on the same transputer the WXM data are analyzed by.
-\par
-SXC data can be used to create a continuous series of cross-correlation maps using a dedicated DSP, 
-and a burst is registered when the peak of the cross-correlation map exceeds a threshold. 
-Because of the difficulties with the SXC hardware, SXC triggering is currently not operating.
-\par
-When a burst is detected, the real-time spacecraft notification will distribute
-\begin{itemize}
-\item the energy range of the burst (1.5-12 keV, 2-30 keV, 5-80 keV, or 30-400 keV)
-\item the timescale of the trigger (from 20 ms to over 10 s)
-\item the S/N or the peak count rate of the burst
-\end{itemize}
-\par
-
-In the year 2002, about 630 internal \he triggers occurred, out of which about 75 were 
-considered as GRBs or possible GRBs by the ground analysis. About 50 of these bursts 
-were subsequently considered as real\cite{HETE-SUM}. Note that about 40 of 
-another species of bursts called ``X-ray bursts'' (XRB) were detected, mainly while the 
-satellite was looking towards the Galactic center.
-\par
-
-The real-time alerts sent to the \g by \he have the following signature~\cite{HETE}:
-\begin{description}
-\item[ALERT] If the burst is detected using photons in the 5-80 keV or 30-400 keV bands, 
-regardless whether a position has been determined or not. This type of alert has occurred 
-about 170 times in 2002. 
-\item[UPDATE] If a position is determined on board and it is considered significant enough, 
-the RA and declination of the burst will be distributed in this type to the \g.
- Each additional position determined on board 
-(each with higher significance than all determined before) 
-will result in a new Notice of type UPDATE. In 2002, about 10 UPDATE's were sent to 
-the \g, two third of which had a position error of about 1 arcmin, one third with about 
-half an arcmin.
-\item[LAST] Once the on-board processing of data near the time of the trigger is complete, 
-there will be no more immediate results from the spacecraft, 
-a summary Notice this type is distributed. In 2002, about 120 LAST's were sent out to the \g, 
-containing about 20 positions of bursts.
-\end{description}
-The quality of the real-time positions are assured by making a cut on the lightcurve S/N and the 
-image S/N in a way that with $>$90\% the real-time position is correct.
-As a result, HETE positions distributed in real time from the spacecraft are in one of two categories:
-\begin{itemize}
-\item Category I: 
-The image and lightcurve S/N all exceed 3.0, 
-so the position is distributed with a 90\% error radius of 12-14 arcminutes.
-\item Category II: 
-Not all of the image and lightcurve S/N exceeds 3.0, 
-but the quadrature sum of the image S/N from the WXM X and Y detectors is > 3.7, 
-and neither the X nor the Y incident angle exceeds 30 degrees, 
-so the position is distributed with a 90\% error radius of 30 arcminutes.
-\end{itemize}
-
-In order to accommodate those observers who would like to make their own estimate 
-of the quality of a real-time burst localization, also included in the \g message are:
-\begin{itemize}
-\item The image S/N from the X and Y modules of the WXM
-\item The lightcurve S/N from the X and Y modules of the WXM
-\item The longitude of the HETE spacecraft at the time of the trigger.
-\end{itemize}
-The higher the image and lightcurve S/N, 
-the more reliable the localization will be. 
-Low values of image and lightcurve S/N are typically associated with events 
-localized at the edge of the instrument FOV.
-\par
-This method of distribution of \g Notices results in a few common situations:
-\begin{itemize}
-\item If there is no significant position calculated in real time on board, 
-there will be no burst coordinates in any \g Notice. 
-If ground analysis reveals a position, 
-it will be sent out as a type GND\_ANALYSIS Notice.
-\item Because the Burst Alert Station coverage is not always 100\%, 
-there can be gaps in the reception of burst data from the spacecraft. 
-If the flight analysis of a burst is over before a Burst Alert Station is seen, 
-the full analysis of the burst will be sent in two Notices, 
-one of type ALERT and the other of type LAST. 
-This means that a Notice of type ALERT could, in principle, 
-contain the coordinates of the burst.
-\end{itemize}
-Both the WXM and SXC search data from seconds before the burst trigger to minutes after, 
-looking for the image of the burst. The WXM software matches the shadow pattern on the detector 
-with template patterns, looking for a best fit; the SXC looks for peaks in the cross-correlation map.
-In either case, if a significant position is found in either instrument, 
-its location is sent to the ground in real time. 
-Once the positions and their significances are received on the ground, 
-the RA and declination of the image are calculated and, 
-if the significances are high enough, transmitted to the \g. 
-At present, SXC positions are not sent to the \g automatically, 
-but rather only after ground analysis.
-
-\par
-Ground analysis of a burst begins as soon as the full burst data reach MIT after a 
-Primary Ground Station contact (from a few minutes to over an hour after the burst). 
-Automated software performs standard analyses of the downlinked data, 
-and a human is notified to make the final decisions. 
-A followup \g Notice, of type GND\_ANALYSIS, 
-will be distributed under the following circumstances:
-\begin{itemize}
-\item There was no position calculated on board, but ground analyses reveal a significant position.
-\item There was a position calculated on board and ground analyses can improve the coordinates 
-and/or reduce the error box size.
-\item There was a position calculated on board, but there is actually no significant position in the data.
-\end{itemize}
-In general, if there is a position in a real-time \g Notice, 
-it should be considered accurate. 
-If there is no position in a real-time \g Notice, 
-a position may be forthcoming within an hour or so of the original Notice. 
-If a burst position was distributed and it is wrong because of software or operator error, 
-a GND\_ANALYSIS message will be distributed; 
-if no position was distributed, no GND\_ANALYSIS message will be sent.
-In 2002, about 25 ground analyses contained positions of GRB's and 5 further of XRB's.
-\par
-
-From the 30 bursts with position sent to the \g in 2002, \ma would have had 7 in its FOV
-which are  listed in the following table:
-\begin{table}[h]
-\label{tab:heteoverlap}
-\begin{center}
-{\small
-\begin{tabular}{|c|c|c|c|c|c|c|c|c|c|}
-\hline
-\hline
-GRB &    date & UTC & RA & dec. & error     & $\theta$ & $\phi$ & flag  & comments\\
-name & (dd.mm)&     &    &      & arc.      & MA- & MA- & providing & \\
-     &        &     &    &      & min.      & GIC & GIC & position & \\
-\hline
---   & 27.11. & 1:20:39 & 53.78 & -15.84 & 60 & 48 & 198 & UPDATE & probable GRB \\
-     &        &         &       &        &    &    &     &  & moon at:\\
-     &        &         &       &        &    &    &     &  & $\theta= 77^\circ, \phi=77^\circ$\\
-\hline
-GRB021113 & 13.11. & 06:38:57 & 23.47 & 40.4 & 28 & 85 & 314 & GND & no moon \\
-\hline
-GRB021112 & 12.11. & 03:28:16 & 39.22 & 48.8 & 54 & 40 & 313 & GND & no moon \\
-\hline
-GRB020813 & 13.08. & 02:44:19 & 296.66 & -19.6 & 28 & 67 & 229 & ALERT &  no moon \\
-\hline
---   & 28.07. & 21:44:58 & 273.67 & -12.13 & 28 & 45 & 153 & UPDATE & probable GRB\\ 
-     &        &         &       &        &    &    &     &  & no moon \\
-\hline
-GRB020531 & 31.05. & 00:26:18 & 228.69 & -19.36 & 77 & 49 & 191 & GND &  
-moon at: \\
-     &        &         &       &        &    &    &     &  & $\theta= 87^\circ, \phi=118^\circ$ \\
-\hline
-GRB020127 & 27.01. & 20:57:24 & 123.77 & 36.74 & 240 & 51 & 64 & UPDATE & 
-moon at: \\
-     &        &         &       &        &    &    &     &  & $\theta= 47^\circ, \phi=83^\circ$ \\
-\hline
-\hline
-\end{tabular}
-}
-\end{center}
-\caption{\he bursts, which would have been in principle visible from the \ma telescope site at 
-night. No burst durations, alert delays, weather conditions, etc. are displayed. For more 
-detailed information on single bursts, see~\cite{NICOLAGRB}.}
-\end{table}
-
-As one can see from table~\ref{tab:heteoverlap}, more overlap bursts 
-than expected from randomly superimposed fields of view ($\sim$1--2 bursts only), 
-have been found. As expected from the increase of covered solid angle at high 
-zenith angles, all bursts had rather larger zenith angles ($\theta \geq 40^\circ$) 
-culminating and cover the whole range of azimuths. 
-\par
-Additionally, five bursts occurred during the day, but would have moved into the \ma FOV in a 
-delay of less than six hours (see table~\ref{tab:hetelongoverlap}):
-\begin{table}[h]
-\label{tab:hetelongoverlap}
-\begin{center}
-{\small
-\begin{tabular}{|c|c|c|c|c|c|c|c|c|c|}
-\hline
-\hline
-GRB &    date & UTC & RA & dec. & error     & $\theta$ & $\phi$ & flag  & comments\\
-name & (dd.mm)&     &    &      & arc.      & MA- & MA- & providing & \\
-     &        &     &    &      & min.      & GIC & GIC & position & \\
-\hline
---   & 15.07. & 18:45:40 & 273.7 & -12.1 & 2.0 & 51 & 138 & UPDATE & XRB \\
-     &        &         &       &        &    &    &     &  & $\theta$ and $\phi$ at 21:43:00 UTC \\
-     &        &         &       &        &    &    &     &  & moon at:\\
-     &        &         &       &        &    &    &     &  & $\theta= 69^\circ, \phi=252^\circ$\\
-\hline
---   & 09.06. & 20:45:37 & 275.9 & -30.4 & 1.4 & 88 & 126 & LAST & possible GRB \\
-     &        &         &       &        &    &    &     &  & $\theta$ and $\phi$ at 21:43:00 UTC \\
-     &        &         &       &        &    &    &     &  & no moon \\
-\hline
---   & 08.06. & 16:02:39 & 275.9 & -30.4 & 2.2 & 89 & 125 & GND & XRB \\
-     &        &         &       &        &    &    &     &  & $\theta$ and $\phi$ at 21:43:00 UTC \\
-     &        &         &       &        &    &    &     &  & no moon \\
-\hline
-GRB020331 & 31.03. & 16:32:28 & 199.1 & -17.9 & 20 & 86 & 113 & GND & $\theta$ and $\phi$ at 21:49:00 UTC \\
-     &        &         &       &        &    &    &     &  & no moon \\
-\hline
-GRB020317 & 17.03. & 18:15:31 & 155.8 & 12.7 & 36 & 46 & 101 & GND & $\theta$ and $\phi$ at 21:40:00 UTC \\
-     &        &         &       &        &    &    &     &  & moon at:\\
-     &        &         &       &        &    &    &     &  & $\theta= 19^\circ, \phi=271^\circ$\\
-\hline
-\hline
-\end{tabular}
-}
-\end{center}
-\caption{\he bursts, which would have been in principle visible from the \ma telescope site occurring 
-during the day but moving into the \ma FOV in less than six hours.
-No burst durations, alert delays, weather conditions, etc. are displayed. For more 
-detailed information on single bursts, see~\cite{NICOLAGRB,GCNARCHIVE}. Two bursts are marked 
-as XRB (X-ray bursts) a phenomenon seen regularly by the \he WXM while looking into the Galactic Center.} 
-\end{table}
-
-The \he field of view spans roughly 75$^\circ$ in DEC and and 5 hrs in RA. 
-Because \he is anti-solar pointing, its field-of view drifts along the ecliptic 
-at a rate of about one degree per day. Its maximum declination reaches 60$^\circ$ with the lower
- border of its field of view at about -15$^\circ$. Its minimum declination reaches -60$^\circ$ 
-with the upper border at about +15$^\circ$~\cite{HETE}. 
-The best overlap between \ma and \he fields of view 
-is thus in the winter, between October and March. 
-
-\section{\ig Alarms}
-
-{\ldots \it \bf THIS IS TO BE UPDATED TO 2003 !! \ldots \\}
-\par
-The \ig satellite was successfully commissioned in March 2003.
-The use of INTEGRAL is planned for 2 years with a possible extension for up to 5 years.
-
-\par
-The satellite contains four main instruments:
-\begin{description}
-\item[IBIS:\xspace] The imager IBIS (Imager on Board the INTEGRAL Satellite) 
-will achieve an angular resolution of 12 arcmin over an energy range between 15 keV and 10 MeV.
-\item[SPI:\xspace] The spectrometer SPI (SPectrometer on INTEGRAL) 
-will provide spectral analysis of gamma-ray point sources 
-as well as extended sources over an energy range between 20 keV and 8 MeV.
-\item[JEM-X:\xspace]
-Two identical X-ray monitors, JEM-X (Joint European X-ray Monitor) will work 
-simultaneously with the other instruments in the energy range between 3 and 35 keV 
-and with an angular resolution of one arcmin. 
-\item[OMC:\xspace]
-The optical monitoring camera, OMC, covers a field of 17.6 x 17.6 arcsec. 
-The total field of view of the OMC camera will be of 5 x 5 degrees. 
-\end{description}
-
-\par
-Alerts with the coordinates of GRBs will be distributed via internet 
-with a small delay with respect to the GRB occurrence. 
-It is expected that this delay will be smaller than a few minutes. The alerts as 
-such can be delivered to the recipient within 1 second. 
-The expected rate of GRBs that will be localized with an accuracy of a few arcminutes 
-is of the order of 1-2 per month~\cite{GOTZ}.
-\par
-The IBAS alerts are sent via internet, using the UDP transport protocol. The Client Software 
-made available by \ig together with the first real alerts are currently being tested in Barcelona. 
-Five Alert Types have been defined so far~\cite{IBAS}:
-\begin{description}
-\item[POINTDIR] Gives the \ig pointing direction (e.g. to obtain reference images of the pre-GRB sky). No 
-alert is attached with this type.
-\item[SPIACS]
-SPIACS alert packets will be sent after positive triggers detected with the 
-SPI Anti-Coincidence Shield (ACS). No position information will be available, 
-unless the same GRB also triggers some of the imaging instruments 
-and in such a case the position will come through other packet types.
-\item[WAKEUP] 
-WAKEUP packets are generated only once for each GRB 
-and only if the GRB position information is available. 
-They contain the preliminary position derived for the GRB. 
-These are the alerts with the shortest time delay. 
-Any (potential) GRB will generate only one WAKEUP packet.
-\item[REFINED] 
-REFINED packets provide refined information on a GRB event. 
-Zero to several REFINED packets can be generated for a given GRB.
-\item[OFFLINE]
-OFFLINE packets are generated manually after interactive analysis of the data has been performed 
-offline by a Duty Scientist. 
-The time delay might be from one to a few hours (or even longer in some cases). 
-\end{description}
-
-One \ig burst was delivered to the GCN up to now. It would have been visible 
-by \ma with a delay of about 1.5 hours (see table~\ref{tab:integraloverlap}).
-
-\begin{table}[ht]
-\begin{center}
-{\small
-\begin{tabular}{|c|c|c|c|c|c|c|c|c|c|}
-\hline
-\hline
-GRB &    date & UTC & RA & dec. & error     & $\theta$ & $\phi$ & flag  & comments\\
-name & (dd.mm)&     &    &      & arc.      & MA- & MA- & providing & \\
-     &        &     &    &      & min.      & GIC & GIC & position & \\
-\hline
-GRB021125 & 25.11. & 17:58:30 & 19.78 & 28.1 & 30 & 51 & 280 & --- & no moon \\
-     &        &         &       &        &    &    &     &  & $\theta$ and $\phi$ at 19:37:00 UTC \\
-\hline
-\hline
-\end{tabular}
-}
-\end{center}
-\label{tab:integraloverlap}
-\caption{\ig bursts, which would have been in principle visible from the \ma telescope site at 
-night. No burst durations, alert delays, weather conditions, etc. are displayed. For more 
-detailed information on single bursts, see~\cite{NICOLAGRB,GCNARCHIVE}.}
-\end{table}
-
-The period of the INTEGRAL orbit is 3 sideral days, 
-so that the perigee occurs always above the same geographical point on Earth. 
-
-%It is a highly eccentric orbit, 
-%with a perigee height of 10'000 km and 
-%an apogee height of 152'600 km 
-%with an inclination of 51.6 degrees with respect to the equatorial plane. 
-
-
-\section{\sw Alarms}
-
-{\ldots \it \bf THIS IS TO BE UPDATED !! \ldots \\}
-
-The \sw satellite~\cite{SWIFT} is scheduled for launch in May, 2004 for a nominal two-years mission. 
-\par
-It contains three instruments:
-\begin{description}
-\item[BAT:\xspace] The BAT has an large field of view (1.4~sr) in an energy range of 15-150~keV. 
-It has an angular resolution of 22 arcmin. and is itself able to determine GRB source locations (of 
-5$\sigma$ or higher) to a resolution of 4 arcmin. It is predicted to locate more than 100 sources 
-per year. 
-\item[XRT:\xspace] The X-Ray Telescope on \sw provides afterglow positions of 5 arcsec. accuracy within
-100 sec. of the burst alert from BAT in an energy range of 0.2-10~keV.
-\item[UVOT:\xspace]
-The UVOT is designed for optical images of the GRB field 20-60 sec. after the GRB alert and 
-in a wavelength range between 170 and 650~nm. 
-\end{description}
-
-1--4 arcmin. position estimates of the GRB coordinates are predicted to arrive at ground within 
-15 seconds~\cite{SWIFT2}. 
-\par
-\sw autonomously sends preliminary information to the GCN, including a crude optical finding chart 
-populated with postage stamp images around detected stars in UVOT, and BAT and XRT source positions 
-and spectra. Within hours of the next ground pass, the Swift Science Data Center (SDC) 
-initiates autonomous pipeline processing of the telemetry and serves it immediately 
-to the community on its Quick-Look area, available to the community (FITS-files).
-
-\section{Further Possible Alarms}
-
-\subsection{IPN position notices}
-
-These notices are sent out by the GCN itself with GRB positions obtained 
-after triangulation of at least three satellites 
-using the individual arrival times and positions of the spacecrafts \he, \ig, 
-KONUS, NEAR, MARS and ULYSSES. 
-Usually, these messages arrive 
-after previous alerts by the satellites themselves and refine the GRB position determination.
-
-There are two types of messages:
-\begin{description}
-\item[IPN\_SEG:\xspace]
-These Notices use the data from two different spacecrafts.
-Triangulation
-yields an annulus for possible GRB positions. 
-The annulii segments are long (2-10deg) and narrow (2-30armin).
-%yielding an error box area of 4 sq.arcmin to 5 sq.deg.
-%The range of time delays is on average 24 to 48 hours (with the shortest being 11 hours to date).
-These message will not be considered further here 
-because their position uncertainties are too large. 
-\item[IPN\_POS:\xspace]
-For IPN\_POS Notices, the error boxes will be in the several arcmin and above range. 
-For about 55\% of the Notices there will be only a single error box, 
-but because 3 sources yield only 2 unique annuli and these 2 annuli cross in 2 locations, 
-there can be 2 error boxes reports (~25\% of the cases).
-Depending on the relative timing of the GRB and the data dumps through the DSN,
-the wait can be 1-25 hours (more on the weekends). 
-In 2002, 22 such messages were sent out with errors in the range of usually 
-5--30 arcmin. There were no messages before the May 5$^{th}$, however. 
-\end{description}
-
-Only one burst would have been announced by an IPN\_POS in less than 12 hours after the burst 
-(see table~\ref{tab:ipnoverlap}).
-
-\begin{table}[ht]
-\label{tab:ipnoverlap}
-\begin{center}
-{\small
-\begin{tabular}{|c|c|c|c|c|c|c|c|c|c|}
-\hline
-\hline
-GRB &    date & UTC & RA & dec. & error     & $\theta$ & $\phi$ & flag  & comments\\
-name & (dd.mm)&     &    &      & arc.      & MA- & MA- & providing & \\
-     &        &     &    &      & min.      & GIC & GIC & position & \\
-\hline
-GRB021016 & 16.10. & 10:29:00 & 8.43 & 46.8 & 22 & 61 & 43 & IPN\_POS & 
-$\theta$ and $\phi$ at 22:06:48 UTC \\
-     &        &         &       &        &    &    &     &  & moon at: \\
-     &        &         &       &        &    &    &     &  & $\theta= 87^\circ, \phi=118^\circ$ \\
-\hline
-\hline
-\end{tabular}
-}
-\end{center}
-\caption{\ip bursts, which would have been in principle visible from the \ma telescope site at 
-night. Only bursts which have been announced with less than 12 hours are taken into account. 
-No burst durations, weather conditions, etc. are displayed. For more 
-detailed information on single bursts, see~\cite{NICOLAGRB,GCNARCHIVE}.}
-\end{table}
-
-\section{Proposed Observation Strategies}
-
-{\ldots \it \bf THIS IS TO BE UPDATED !! \ldots \\}
-\par
-One can see from tables~\ref{tab:heteoverlap},~\ref{tab:hetelongoverlap},~\ref{tab:integraloverlap}
-and~\ref{tab:ipnoverlap} that observing GRBs 
-at moon periods will significantly increase the chance to observe some. 
-Three out of the seven bursts from table~\ref{tab:heteoverlap} 
-would have occurred in astronomical twilight 
-or very close to the start or end of observation 
-(GRB021113 half an hour after usual closing of the telescope and 
-GRB020127 and the one on 28.7. each three quarters of an hour after usual 
-start). If we want to have a realistic chance to observe bursts, it is therefore 
-important to use all available time {\it including moon periods, periods of astronomical 
-twilight and putting the telescope as soon as possible in GRB-alert position}.
-
-\subsection{What to do at alerts without position (yet)}
-
-{\ldots \it \bf THIS IS TO BE REWRITTEN !! \ldots \\}
-
-\begin{verbatim}
-suggestion email Martin Kestel: \\
-\\
-When you put the telescope in Alt=90 degrees (zenith) and Az=90 degrees east, 
-you have at most 90 degrees to move in either
-axis in order to reach any position on the sky, either in normal tracking mode
-or in reverse tracking mode. The actual speed will most probably be different
-in the two axes and the elevation will probably be slower, as it has only one
-motor attached. Now, the maximum elevation movement from zenith will
-correspond to the maximum zenith angle you want your GRB to have, so, 
-this number will be certainly smaller than 90 degrees.
-\end{verbatim}
-
-\subsection{What to do at alerts with position}
-
-
-\section{Timing considerations}
-
-{\ldots \it \bf HAS TO BE UPDATED AND COMPLETED!! \ldots \\}
-{\it Here, all possible models should go in with reasonning why certain time 
-or flux estimates are proposed.  We have now only estimates on extrapolations 
-of the \eg power-laws. Maybe we should include: IC (in many possible combinations), 
-hadronic emission models (see~\cite{TASC}), Cannonball model. }
-\par
-
-The EGRET~\cite{EGRET} instrument on the CGRO 
-has detected GeV emission of GRB940217 promptly and 90 sec. after 
-the burst onset. 
-\\
-\par
-In~\cite{DERMER}, two peaks in the GeV light curve are calculated. An early maximum coincident 
-with the MeV eak is the high-eneryg extension of the synchrotron component, some seconds 
-after the burst onset. The second maximum peaking at $\approx$ 1.5 hours is due primarily to 
-SSC radiation with significant emission of up to $10^5$ sec. ($\approx 25$ hours) after the burst. 
-\\
-\par
-Li, Dai and Lu~\cite{LI} suggest GeV emission after pion production and some thermalization of the 
-UHE component with radiation maxima of up to one day or even one week (accompanied by long-term
-neutrino emission).
+
+
 
 \subsection{Determine a reasonable upper time delay limit for the onset of an observation}
@@ -670 +138 @@
 
 {\ldots \it \bf STILL TO BE WRITTEN  \ldots \\}
-
-\subsection{Observing neutrino events below the horizon}
-
-{\ldots \it \bf CAN BE MAYBE GO INTO A SEPARATE PROPOSAL  \ldots \\}
 
 \subsection{Observing XRFs}

trunk/MagicSoft/Mars/Changelog

@@ -62 +62 @@
      - added some Getter
 
-
-
  2005/01/24 Markus Gaug
 
-   * msignal/MExtractTimeAndCharge.cc
-     - call Clear() for two results containers at beginning of Process()
+   * msignal/MExtractTime.cc
+   * msignal/MExtractor.cc
+     - removed Clear() for two results containers at beginning of Process()
 
    * msignal/MExtractedSignalPix.cc

trunk/MagicSoft/Mars/msignal/MExtractTime.cc

@@ -159 +159 @@
 
   MRawEvtPixelIter pixel(fRawEvt);
-  fArrTime->Clear();
 
   while (pixel.Next())

trunk/MagicSoft/Mars/msignal/MExtractor.cc

@@ -293 +293 @@
 
   MRawEvtPixelIter pixel(fRawEvt);
-  fSignals->Clear();
 
   while (pixel.Next())