Документ взят из кэша поисковой машины. Адрес оригинального документа : http://xmm.vilspa.esa.es/sas/5.4.1/doc/emevents.ps.gz Дата изменения: Fri Jan 10 22:52:53 2003 Дата индексирования: Tue Oct 2 04:28:09 2012 Кодировка:

XMM-Newton Science Analysis System Page: 1
emevents
January 10, 2003
Abstract
Dene the nal list of events, correct position and time for one node of one EPIC-
MOS CCD over one exposure.
1 Instruments/Modes
Instrument Mode
EPIC MOS IMAGING, TIMING
2 Use
pipeline processing yes
interactive analysis yes
3 Description
emevents ags unvalid events (following [3]), subtracts bad pixels, merges events split over two nodes,
separates piled up diagonal events into two, adds the time column and monitors the GATTI performance.
It also modies the RAWX and RAWY coordinates to center the events and computes camera coordinates.
emevents modies the number of events. Therefore after it the event le is not consistent with the
NVALID eld of the frame le any more. It may be applied as is to slew data.
As a preliminary step, emevents rejects events with invalid FRAME, RAWX, RAWY and PATTERN. Those are
the result of telemetry errors. They are removed from the list altogether (not only agged).
emevents calls (in order) the following subroutines, all of which can be individually switched o (this
is provided for calibration and debugging activities, the result will not in general be scientically useful
when not used with the default settings):
 EV REC. In EDU Threshold mode (associated to telemetry REDUCED IMAGING mode),
all pixels above the EMDH lower threshold and below the EMDH upper threshold are trans-
mitted individually (no event recognition is performed on board). EV REC performs the
same pattern analysis as on-board, with the dierence that it is performed with the EDU
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 2
threshold set at the EMDH lower threshold (everything below that was lost) and the ener-
gies E 3 and E 4 cannot be recovered.
EV REC generates the ENERGYE1 and ENERGYE2 columns (per event) from the original
ENGYE1E2 column (per pixel). It ags the events outside the EMDH thresholds with OUTSIDE THRESHOLDS.
In Imaging mode this pattern analysis is performed after CUT BAD if analysepatterns is
set to True.
In Timing mode this pattern analysis is used to reject events classied as singles or bipixels
by the 1-D pattern analysis on board, but which are actually part of a large track from a
cosmic-ray in the framestore area. A 2-D pattern analysis, similar to that in Imaging mode,
is run locally around all events with PATTERN 0 or 1 and the event is accepted only if it
would have passed the Imaging pattern analysis, with any PATTERN less than 30. Otherwise
it is agged as COSMIC RAY. No such cosmic-ray rejection is performed if analysepatterns
is set to False. This may not be applied in Compressed Timing mode because most events
do not have a valid RAWX and PATTERN in that mode.
 CUT BAD. On-board all events centered on a bright pixel (declared in the on-board li-
brary) are rejected, but weak bad pixels (with low charge contents) can also be included in
X-ray events next to them. Those events must be corrected for that. To that end all areas
around bright pixels (declared or not in the on-board library), and next to borders, may
be reanalysed, putting the bright pixels and the pixels outside the declared window to 0.
In the process events corresponding to bright pixels not declared on board are agged as
ON BADPIX. If a bright pixel is the main pixel of a split event, it may appear twice in output:
the original event ( agged as ON BADPIX) plus what remains after removing the bright pixel.
Bad pixels are read from the bad pixels extension added by badpix. Dead and intact bad
pixels are ignored.
In TIMING mode there are no bad pixels, only bad columns. The events are not re-
analysed, but simply agged with ON BADPIX. The same happens in Imaging mode when
analysepatterns is set to False. This may not be applied in Compressed Timing mode
because most events do not have a valid RAWX in that mode.
 BINODAL. If the CCD was read through both nodes (mode PRI PART W6 IMAGING
only), X-rays interacting close to the median column of the CCD have their charge cloud
split over both nodes. BINODAL recognizes as only one event those which have been de-
tected on both sides, using the same patterns as on-board. This means also rejecting events
which become larger than the accepted patterns. Only events with their maximum on this
side of the border are kept in the list (i.e. the event list remains formally associated to
one node). If the frame for the other node is agged as bad, then its events should not be
merged. Instead events immediately next to the other half of the CCD should be agged as
CLOSE TO CCD BORDER.
 DIAGO. Diagonal patterns are mostly due to two close-by single events. DIAGO forms two
events out of one in that case. Both events are agged with DIAGONAL to distinguish them
from true single events. The second event is created only if its charge (i.e. E 2
) is above the
EMDH lower threshold. This operation does not respect the order of increasing RAWY within
a frame. This routine is not applicable in TIMING mode.
When either E 1 or E 2 is within one HWHM of the energy of Si K (1740 eV), the event can
be due to partial absorption associated with Si uorescence, caught in a neighbouring pixel.
This appears as a line at that energy in the spectrum of diagonals. If keepsifluor is set
to True, these events are not split in two but their PATTERN is changed from diagonal to
bipixel (so that it receives the appropriate calibration), and it is agged with DIAGONAL (to
remember it was). As a side eect this creates a hole in the spectrum of diagonals at the
energy of 1740 eV.
 CUT GTI. All events whose frames were agged for rejection by emframes ( ag above
64) are agged for rejection with IN BAD FRAME. Events whose frames were agged below
64 by emframes are agged with IN SPOILED FRAME. \cosmic-ray" events (patterns read
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 3
from CRPATi keywords) are agged with COSMIC RAY. CUT GTI propagates the FRMTIME
and CRPATi keywords.
 PUT XY centers the events (telemetered positions are those of the upper-right corner of
the 5x5 pattern area), subtracts the underscan (not relevant to the user) and adds 1 (for
coherence with the FITS standard on images) so that coordinates run from 1 to 600. It also
subtracts the underscans and adds 1 to the WINDOWX0 and WINDOWY0 keywords for coherence.
Finally, it subtracts the under + overscans (in full frame mode) or 2 (in window mode) to
the WINDOWDX and WINDOWDY keywords.
It then computes the camera coordinates DETX, DETY, in the CAMCOORD2 coordinate
system as described in cal, in units of 0.05 arcseconds. This includes by default randomi-
sation (within a CCD pixel) to avoid Moire eects. Randomisation may be switched o
using randomizeposition=N. In TIMING mode the missing coordinates are replaced by
the SRC RAWX, SRC RAWY keywords (or the center of the CCD if those keywords do not exist)
for computing the camera coordinates. PUT XY ags the (false) events outside the window
with OUT OF CCD WINDOW.
 PUT TI (IMAGING mode) copies for each event of a given frame the same time computed
as the middle between the start and end times of the current frame. Optionally time ran-
domisation (within a frame) may be performed using randomizeposition=Y.
PUT TI (or PUT TT) creates and lls the EXPOSURE extension, with precise time and dura-
tion of each frame and the eective fraction of observing time, corrected for dead-time using
the CRRATIO column of the frame le. The (small) frame transfer time (during which the
sky is actually observed but smeared over a column) is subtracted from the frame duration
TIMEDEL. Following OGIP/93-003, the time is that of the center of each frame (i.e. the same
as that of the events).
 PUT TT (TIMING mode) computes the time for each event as a reference time (the start
time of the current cycle) plus (y i
+ 0.5) times the clocking time. Precise corrections on the
basis of the source position on the CCD are not done at this level. Times are computed as
if the source was at the center of the CCD.
 REJECT ROWS. Some instrumental eects result in several events following one another
in the same row in one frame (particularly at small RAWY), while this is unlikely for normal
X-rays. A simple way to reject this noise is to reject all events (of that frame) found in rows
with many events in a given frame. This is done with ag ON BADROW. The threshold may
be set via maxeventsperrow.
To avoid rejecting true events for bright extended sources or strongly piled-up sources, the
average number of counts in that row plus twice its square root (2  security) is added to
maxeventsperrow.
 REJECT E3 (IMAGING mode, not reduced IMAGING). Some instrumental eects result in
wrong events associated with pathological (usually negative) charge values next to it. This
information is known through the E 3 data. A simple way to reject this noise is to reject all
events whose E 3 is less than a lower threshold (depending on instrument and CCD) set by
e3thresholds. This is done with ag UNDERSHOOT, and has very little eect on true X-rays.
This test is not applied next to rows or column with oset set to 4095 (all events would be
systematically rejected because some of the pixels making E 3 appear at -4095).
 SP GATTI. In order to check the GATTI correction it is possible to compute the energy of
events as it was seen by the ADC. This is done by adding the GATTI value and the osets to
all E 1 energies (the other E i
are sums and therefore unsuitable to this purpose) and forming
their spectrum (for events un agged by CUT GTI). All small scale (in energy) structures
in the charge to ADU conversion should reappear in this spectrum. After dividing it by the
direct spectrum of E 1 energies convolved by the histogram of (GATTI + osets) values, this
can be compared with a reference spectrum to look for variations (outside emevents).
In parallel, SP GATTI has an active part, agging for rejection with REJECTED BY GATTI all
events with E 1 + GATTI + osetx(RAWX) + osety(RAWY) = 4095 (range of the ADC),
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 4
which should have been rejected by the EMDH upper threshold but were not due to the
GATTI mechanism.
In TIMING mode this test is restricted to single events, as ENGYE1E2 is the total charge
over all pixels above threshold in the event. This routine is not applicable in Compressed
TIMING mode (no PATTERN).
EV REC, CUT BAD, DIAGO and BINODAL may run only on a fresh ODF event le, not on the result
of a previous run of emevents.
PUT TIME, CUT GTI and SP GATTI require an associated frame le. If withframeset=False then an
empty EXPOSURE extension is created to allow propagating the CCD-specic keywords after evlistcomb.
SP GATTI and REJECT E3 require an associated oset/variance le or extension. It is also advised
to provide it for CUT BAD and BINODAL. As it is not always obvious to know which osets le is
the right one (if several modes were used in an observation, there will also be several osets les with
dierent exposure numbers), emevents will select among a list of osets les those compatible with the
events le in terms of CCD, node, mode and window parameters. Among the compatible les emevents
will select that with DATE-OBS closest to DATE-OBS of the events le, rst within the osets les obtained
before the events le, then within those obtained after the events le if none was obtained before.
The rst and last four column osets (in the window) are patched to 4095 as is done in operations.
If no local oset/variance le is available (because the standard values were used), or if withoffvarsets=False
emevents will read the osets from the cal. If the osets actually used were dierent, this will result in
a large number of spGatti11 warnings and the agging of events with truncated energy will be wrong.
3.1 Patterns
The gure should be interpreted as follows:
 each pattern is included in a 5x5 matrix used for proximity analysis.
 a pattern is centered by denition on the pixel with highest charge.
 this central pixel is colored in red (its charge is E 1 ).
 the other pixels above threshold in the pattern are colored in green (the sum of their charges
is E 2 ).
 all pixels colored in white must be below threshold.
 the crossed pixels are indierent (they can be above threshold).
 the patterns are recognized in increasing order (this is important only for pattern 30, which
comprises patterns 0 and 26-29).
The philosophy for patterns 0-25 is that a good X-ray pattern must be compact, with the highest charge
at the center, and isolated (all pixels around are below threshold).
Patterns 26-29 are the so-called diagonal patterns, not expected from a genuine X-ray, but which can
arise in case of Si uorescence or of pileup of two monopixel events.
The E 3 and E 4 data in the ODF event lists have nothing to do with the "white" and "crossed" pixels.
 E 3 is the sum of charges of pixels below threshold in the 8 pixels of the 3x3 corona (their
number is known from the pattern number).
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 5
Figure 1: List of EPIC-MOS patterns (IMAGING mode)
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 6
 E 4 is the sum of charges of pixels below threshold in the 16 pixels of the 5x5 corona. Their
number N4 is known from the PERIPIX column in the event list, which stores the number
of pixels above threshold in the 5x5 corona. Thus N4 = 16 - PERIPIX.
4 Parameters
This section documents the parameters recognized by this task (if any).
Parameter Mand Type Default Constraints
odfeventset yes dataset ' ' none
Input events le
withframeset no boolean no yes/no
Need input frames le
frameset no dataset ' ' none
Input frames le from emframes
newoutput no boolean yes yes/no
Create output events le (no for overwriting input)
eventset no dataset 'events.out' none
Output events le
withovarsets no boolean no yes/no
Need input oset/variance le
ovarsets no list of
datasets
' ' none
List of oset/variance les from ODF
withothernode no boolean no yes/no
Need les for other node (2-node CCD read-out only)
othereventset no dataset ' ' none
Input events le for other node
otherframeset no dataset ' ' none
Input frames le for other node
analysepatterns no boolean yes yes/no
Use EV REC subtask
agbadpixels no boolean yes yes/no
Use CUT BAD subtask
splitdiagonals no boolean yes yes/no
Use DIAGO subtask
keepsi uor no boolean no yes/no
Keep Si uorescence diagonals as one
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 7
agbadtimes no boolean yes yes/no
Use CUT GTI subtask
setcoordinates no boolean yes yes/no
Use PUT XY subtask
randomizeposition no boolean yes yes/no
Randomize DETX/DETY within a pixel
settimes no boolean yes yes/no
Use PUT TI/PUT TT subtask
randomizetime no boolean no yes/no
Randomize TIME within a frame
rejectrows no boolean yes yes/no
Reject rows with too many events
maxeventsperrow no integer 4 > 0
Maximum number of events per row in a frame
rejecte3 no boolean yes yes/no
Reject rows with too negative E3
e3thresholds no list of 14
integers
-29 -68 -40 -45 -34 -41
-51 -36 -57 -30 -23 -27
-36 -29
none
Lower threshold on E3 for all CCDs (M1 and M2)
agtruncatede1 no boolean yes yes/no
Use SP GATTI subtask
writegattispecset no boolean no yes/no
Create output GATTI spectrum le
gattispecset no dataset 'gattispec.out' none
Output GATTI spectrum le
blocksize no integer 10000 > 0
Size of event blocks
5 Errors
This section documents warnings and errors generated by this task (if any). Note that warnings and
errors can also be generated in the SAS infrastructure libraries, in which case they would not be docu-
mented here. Refer to the index of all errors and warnings available in the HTML version of the SAS
documentation.
getParamValues03 (error)
output event le name = input events le name
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 8
openEventsIn01 (error)
newoutput = no (overwrite) and ODF-style events le
openEventsIn02 (error)
Not event list extension name in events le
openEventsIn03 (error)
Not EPIC MOS extension name in events le
copyColumnPart01 (error)
column of unknown type in events le
getNvalid01 (error)
frame number in events le outside those in frames le
readFrames01 (error)
non-regular frame numbers in frames le
initEdusoft02 (error)
unexpected EDUMODE in events le
initEdusoft03 (error)
Imaging mode data and EDUMODE not 3
initEdusoft04 (error)
Timing mode data and EDUMODE not 1
initEdusoft05 (error)
Reduced Imaging mode data and EDUMODE not 2
cutBad01 (error)
more than 2 events created out of one in CUT BAD
getParamValues10 (warning)
missing/invalid bad pixels extension in events le
corrective action: assume none
getParamValues12 (warning)
events le already processed by emevents and CUT BAD activated
corrective action: skip CUT BAD
getParamValues13 (warning)
events le already processed by emevents and DIAGO activated
corrective action: skip DIAGO
getParamValues14 (warning)
events le already processed by emevents and BINODAL activated
corrective action: skip BINODAL
readFrames11 (warning)
CR DEAD not run on frame le
corrective action: continue
readFrames12 (warning)
no GATTIVAL column in input frame le
corrective action: skip SP GATTI
readFrames14 (warning)
frame le not processed by emframes
corrective action: skip CUT GTI, PUT TI/PUT TT and SP GATTI
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 9
readFrames16 (warning)
no FRAME or TIME column in input frame le
corrective action: skip CUT GTI, PUT TI/PUT TT and SP GATTI
readFrames17 (warning)
no FRAMES extension in input frame le
corrective action: skip CUT GTI, PUT TI/PUT TT and SP GATTI
readFrames19 (warning)
input frame le has only one row
corrective action: skip CUT GTI, PUT TI/PUT TT and SP GATTI
readFrames20 (warning)
input frame le is empty
corrective action: skip CUT GTI, PUT TI/PUT TT and SP GATTI
openEventsOut14 (warning)
no valid oset/variance le but SP GATTI activated
corrective action: skip SP GATTI
openEventsOut15 (warning)
no valid oset/variance le but CUT BAD or BINODAL activated
corrective action: assume constant
checkOsets10 (warning)
oset/variance le does not exist
corrective action: look for next one
checkOsets11 (warning)
no valid oset/variance le but CUT BAD, BINODAL or SP GATTI activated
corrective action: assume constant, skip SP GATTI
checkOsets12 (warning)
no compatible oset/variance le older than current exposure
corrective action: consider les obtained after current exposure
checkRejected10 (warning)
more than 90% events rejected
corrective action: continue
reanalyze15 (warning)
blocksize smaller than number of events in a single frame
corrective action: increase blocksize internally and continue
putXY10 (warning)
PUT XY already done before
corrective action: skip EV REC, CUT BAD, BINODAL and PUT XY
spGatti11 (warning)
ENERGYE1 incoherent with GATTI and osets
corrective action: continue
openEvents2In13 (warning)
invalid event le from other node
corrective action: skip BINODAL
read2Frames11 (warning)
frame numbers not parallel for both nodes
corrective action: skip BINODAL
read2Frames13 (warning)
invalid frame le from other node
corrective action: skip BINODAL
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 10
6 Input Files
1. EPIC MOS event list le for one CCD/node (from ODF/SDF, emframes oremevents)
with bad pixels extension (from badpix).
2. frame le for that CCD/node (from emframes). uses columns FRAME, TIME, FLAG, CRRATIO,
GATTIVAL, and keywords TELESCOP, INSTRUME, OBS ID, EXP ID, CCDID, CCDNODE, GATTI ON,
SRC RAWX, SRC RAWY.
3. EPIC MOS oset/variance le for that CCD/node (from ODF/SDF)
4. EPIC MOS event list le for the other node of the same CCD (from ODF/SDF) with bad
pixels extension (from badpix).
5. frame le for the other node (from emframes)
The structure of les in the ODF is described in [1].
7 Output Files
1. new event list le with an EVENTS extension with a dierent number of rows and modi-
ed/additional items:
 modied columns RAWX, RAWY (for PRODUCT: EPIC event list)
 new INTEGER*2 columns DETX, DETY (0.05") (for attcalc and PRODUCT: EPIC
event list)
 new REAL*8 column TIME (s) (for PRODUCT: EPIC event list)
 new INTEGER*2 column FLAG (for emenergy)
 new REAL*4 columns PHA (ADU) and PI (eV) (for emenergy). In TIMING mode
the original ENGYE1E2 column is moved to PHA.
 new empty INTEGER*4 columns X, Y (0.05") (for attcalc)
 modied columns ENERGYE1 and ENERGYE2 (E 1 and E 2 in the text) These columns do
not exist in TIMING mode.
 modied WINDOW keywords (for PRODUCT: EPIC event list)
 keyword DET SYST (for attcalc)
 keywords RAND XY and RAND TIM telling which columns were randomised.
 keywords FRMTIME, GATTI ON, COSMICSI, COSMICOU, and CRPATi propagated from the
frame le
 keyword BINODAL warning of 2-node read-out (for emenergy)
 XMMEA nn keywords detailing which ags were set, including XMMEA EM setting the EPIC
MOS rejection mask
 keywords detailing which subroutines were activated, in particular SETCOORD indicates
that RAWX/RAWY were changed.
 comment lines with names of input les
a BADPIX extension propagated from the input le, an OFFSETS extension propagated from
the oset/variance le (if any, for emenergy) and an EXPOSURE extension specic to that
CCD/node (for evlistcomb and eexpmap, arfgen, [2]), with the following items:
 REAL*8 column TIME (s) giving the central time of each frame
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 11
 REAL*4 column TIMEDEL giving the integration time of each frame
 REAL*4 column FRACEXP giving the fraction of eective time
2. a GATTI spectrum le (for calibration purposes) with a SPECTRUM extension with ADU as
index (1-4096) and the following items:
 INTEGER*4 column ORIGINAL giving the histogram of E 1 *GATTI
 REAL*4 column SMOOTHED giving (normalised histogram of E 1 ) convolved with (his-
togram of GATTI)
8 Algorithm
MODULE em_events_module
Read the file names of event files (input and output) and frame file
Open files
Get keyword values
parameters read : choice of sub_tasks to execute
Loop over input task parameters
Read the task parameter / 1 to perform the procedure,
0 not to perform it /
End loop
Get the values of files columns in memory
SUBROUTINE CUT_BAD
if cut_bad requested then
read bad pixels in extension
Loop over frames
Creation of image using inverse pattern definition
Connection with binodal task
in the case of 2 files (prime and redundant) analysis
Set bad pixels to 0
Loop over events
Use of EDUSOFT code for new pattern reconstruction
creation of new rows and destruction of old ones
end loop
end loop
endif
SUBROUTINE DIAGO
if diago requested then
Loop over event rows for diagonal patterns
Check if both E1 and E2 energies are different from Si K energy
In this case :
first correct the existing pattern
pattern is 0, e2 is 0, others the same
second create another pattern
pattern is 0, e1 is old e2, X & Y to be calculated
depending on pattern
e2 is 0, others the same
xmmsas\_20030110\_1802-5.4.1

XMM-Newton Science Analysis System Page: 12
both patterns are flagged
( do not correct the NVALID in the file frame )
end loop
new rows have been created at the end of file
now shift of lines in order to insert new events
Loop over number of new lines
Shift all rows following place of insertion
end loop
endif
Check events with energy value below EMDHLOW or above EMDHHIGH
SUBROUTINE CUT_GTI
if cut_gti requested then
Loop over frame rows
all events whose frames were flagged are flagged for rejection
end loop
endif
SUBROUTINE PUT_XY
if put_xy requested then
Loop over events
center the events, substract the underscan, add 1.
flag the events outside the field of view
end loop
Modify window keywords
Compute camera coordinates
endif
SUBROUTINE PUT_TI ( Imaging mode )
if put_ti requested then
Loop over frame rows
Loop over events rows
calculate the average time for the frame
copy this time in the time column of events file
end loop
end loop
endif
SUBROUTINE PUT_TT ( Timing mode )
if put_tt requested then
Loop over frame rows
Loop over events rows
calculate the new time as reference frame time plus Y offset
copy this time in the time column of events file
end loop
end loop
endif
SUBROUTINE REJECT_ROWS
if reject_rows requested then
Loop over frame rows
Loop over events rows
Build RAWY profile
end loop
xmmsas\_20030110\_1802-5.4.1

XMM-Newton Science Analysis System Page: 13
Loop over events rows
Flag events with RAWY profile larger than maxeventsperrow
end loop
end loop
endif
SUBROUTINE REJECT_E3
if reject_e3 requested then
Read e3threshold parameter for current instrument and CCD
Loop over events rows
Flag events with pattern <= 4 and E3 < e3threshold
end loop
endif
SUBROUTINE SP_GATTI
if sp_gatti requested then
Loop over events rows
calculate the E1 spectrum, the (E1+gatti) spectrum
and the gatti spectrum
end loop
Convolution of E1 and gatti spectra
endif
sequence of instructions for outevent1 creation
closing files
end module
9 Comments
 The reanalysis of events in EV REC, CUT BAD and BINODAL calls a C routine (edusoft)
which interfaces to the C routine (edu simu, written by M. Lortholary of the EPIC/Saclay
team) which simulates the EDU recognition.
 The search for new bad pixels in the data should be performed after emevents so that
known bad pixels are removed and positions are correct.
 Instead of zeroeing bad pixels in CUT BAD, it may be possible to subtract their average
level (usually well dened), leaving only increased noise.
 In 2-node operation, the task must be run twice (once for each node). Thus the projection
of events back to the CCD map in BINODAL is done twice. This is not expected to be a big
overhead. The alternative would be to generate both output event lists in the same task.
10 Future developments
The following points are not considered nal:
 To recompute properly the E 2
energy across nodes (in 2-node operation) the dierential
gain of the nodes should be accounted for.
xmmsas 20030110 1802-5.4.1

XMM-Newton Science Analysis System Page: 14
 It is foreseen to move the parameters of the REJECT E3 routine (e3thresholds) to the
CCF.
References
[1] ESA. XMM Interface Control Document: Observation and Slew Data Files (XSCS to SSC) (SciSIM
to SOCSIM). Technical Report XMM-SOC-ICD-0004-SSD Issue 2.5, ESA/SSD, June 2000. Found
at the URL: ftp://astro.estec.esa.nl/pub/XMM/documents/odf icd.ps.gz.
[2] L.Angelini I.George. Specication of Physical Units within OGIP FITS les. Technical Report
OGIP/93-001, NASA/GSC, May 1995.
[3] Giuseppe Vacanti. Interface specication for the xmm event attributes, April 1999. GV/XMM/1999-
01.
xmmsas 20030110 1802-5.4.1