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


emchain (emchain-12.0.1) [xmmsas_20230412_1735-21.0.0]

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 documented here. Refer to the index of all errors and warnings available in the HTML version of the SAS documentation.

odferror 
 No or non existing or empty input directory
 
odffileserror 
 No ODF-like file in input directory
 
lowGainwarning 
 a CCD was operated in low gain mode. It is scientifically useless and emchain will normally not process it. If processlowgain is set, it will be processed but the flare screening light curve will be wrong unless this is the central CCD
corrective action: set processlowgain=Y if you want that CCD to be processed
 
badexposurewarning 
 the T*EVLI*.FIT files are incompatible with the requested exposure. The merged events list will not be created. This is possible only when clobber=N and T*EVLI*.FIT files exist
corrective action: check the T*EVLI*.FIT files and rerun
 
badinstrumentwarning 
 the T*EVLI*.FIT files are not MOS files. The merged events list will not be created. This is possible only when clobber=N and T*EVLI*.FIT files exist
corrective action: check the T*EVLI*.FIT files and rerun
 
protonflarewarning 
 The GTI fraction after flare screening is less than 10%. It is not applied
corrective action: reassess the flare GTI manually, or change flaremaxrate if you wish
 
noIN_FOVwarning 
 the EXPOSUnn extensions of the merged events file do not contain the IN_FOV keyword. The flare detection cannot proceed
corrective action: rerun emchain on the ODF to regenerate the merged events file
 
badstringwarning 
 a keyword does not have the expected length. It is truncated or padded with _. This should not happen on a regular ODF
corrective action: check whether a file is not corrupted in the ODF (you may know which file contains the offending keyword by looking at the messages), and that the substitution is all right
 

XMM-Newton SOC -- 2023-04-16