XMM-Newton SAS Home Page
XMM-Newton Science Analysis System


emchain (emchain-11.20) [xmmsas_20211130_0941-20.0.0]


Main loop

Figure 1: Organisation of the EPIC-MOS chain: merging the event lists. The files in boldly dashed boxes are used (or produced) if they exist. The files in simply dashed boxes are options of the individual tasks not used in the current chain.
\begin{figure}\centerline{\psfig{figure=imaging1.eps,width=\textwidth}}\end{figure}

The main subroutine (processOdf, Fig 1) loops over all exposures and instruments (MOS1/MOS2) present in the input directory (looking for event list files).

If withatthkgen is true or if the tracking history file does not exist already, atthkgen is run first. tabgtigen is run on the output to generate the attitude GTI. The tolerance on attitude variations may be modified via atttol. hkgtigen is run if the HK GTI does not exist already. Those GTI files are not applied by default, they are generated for information. They can be applied by setting filteratt=Y and/or filterhk=Y. They are then merged with the user GTI (if ingtiset is set) into the external GTI used by emframes.

processOdf creates one (or two, if a CCD is operated in TIMING mode) event list for every selected exposure, from all relevant ODF material and (if they exist) the good time intervals generated by tabgtigen and the list of bad pixels (from the CCF or produced internally).

Figure 2: Organisation of the EPIC-MOS chain at CCD/node level with file inputs. Same conventions as in Fig 1
\begin{figure}\centerline{\psfig{figure=imaging0.eps,width=\textwidth}}\end{figure}

In a first step it loops over all CCD/nodes, calling in sequence, as shown in Fig 2:

  1. emframes on the auxiliary file, the events file and the external GTI file (if any), creating a frame file as expected by emevents and a CCD/node specific GTI file which will be reinjected in the final call to evselect.
  2. badpix on the events list, adding the BADPIX extension. If a bad pixels file exists, it is used instead of the CAL calls for the non-uplinked bad pixels, (i.e. badpix is called with getuplnkbadpix=Y getotherbadpix=N getnewbadpix=Y).
  3. emevents on the events list, the offset/variance file and the frame file, creating a new events list which will be propagated through attcalc and emenergy to evlistcomb.
  4. gtialign on the external GTI file and the events file, then gtimerge to merge the resulting aligned GTI and the CCD/node specific GTI.
  5. attcalc on the new events list, filling the X/Y columns.
  6. emenergy on the new events list, filling the FLAG, PHA and PI columns.

By default position, energy and time of each photon are randomised within their respective bins (one CCD pixel for position, one ADU for energy, one frame for time).

Then (Fig 1) all the event list files created (one per CCD/node) are merged by evlistcomb, creating one events list per mode (IMAGING, TIMING). Finally evselect is called on the resulting events list(s), with (CCDNR==$node$ccd) && GTI(merged GTI file,TIME) for all CCD/nodes. emtaglenoise loops over all CCDs (except the central one) to check occurrence of low-energy electronic noise and write the LENOISnn keyword, set to 1 if a CCD is affected. The list of calibration files used to analyse the data is added to the output files as a CALINDEX extension.

XMM-Newton SOC -- 2021-11-30