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


emframes (emframes-5.11) [xmmsas_20211130_0941-20.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.

getParamValues01error 
 checkframes=yes and no input events file
 
readEvents01error 
 invalid input events file
 
frames01error 
 checkframes=yes and non-ODF style input frames file
 
frames02error 
 invalid input auxiliary file
 
frames03error 
 no data for CCDID/CCDNODE of events file in auxiliary file
 
frames04error 
 input events file incompatible with auxiliary file
 
frames05error 
 non increasing frame numbers over entire auxiliary file
 
frames06error 
 invalid input counting mode file
 
frames08error 
 a timein value larger than the cycling time has been found
 
readFrames03error 
 invalid input frames file
 
readFrames04error 
 input events file incompatible with frames file
 
getParamValues10warning 
 checkframes=yes and newoutput=no (overwrite). Skip FRAMES
corrective action: restart from auxiliary file if you wish to reapply FRAMES
 
getParamValues15warning 
 odfeventset not set and checknvalid=Y or setdeadtime=Y. Skip VALID and CR_DEAD
corrective action: run emframes with odfeventset set if you wish to aply VALID or CR_DEAD
 
readEvents10warning 
 invalid input events file. Skip VALID and CR_DEAD
corrective action: check input events file
 
flagHk10warning 
 invalid input HK GTI file. Skip FLAG_HK
corrective action: check the HK GTI file
 
frames10warning 
 time interval not constant in data, or input file has fewer than 4 frames. Do not check FRMTIME
corrective action: check FRMTIME manually
 
frames11warning 
 the value of CLOCK_WRAP_AROUND in the summary file is invalid. Use 32767. This is normally all right
corrective action: check FRMTIME manually
 
frames12warning 
 some frames were dropped from the end of the file in analysing the data due to non-increasing frame numbers
corrective action: check FRMTIME manually
 
frames13warning 
 duplicate frame numbers found in the input file, all but one were dropped.
corrective action: check in the input auxiliary file that the proper frames were selected for analysis
 
frames14warning 
 some frame numbers were found out of sequence, so the input data were sorted.
corrective action: none
 
frames15warning 
 frame integration time significantly different from FRMTIME keyword. Update FRMTIME
corrective action: none
 
frames16warning 
 aberrant time in the auxiliary file. Continue, flag such frames and ignore or set their time approximately
corrective action: none
 
frames17warning 
 non-increasing time in the auxiliary file. Continue, flag such frames and ignore or set their time approximately
corrective action: none
 
valid10warning 
 checknvalid=yes and VALID already applied. Option ignored
corrective action: restart from auxiliary file if you wish to reapply VALID
 
valid11warning 
 checknvalid=yes and events have frame number outside frame interval in frames file. Continue
corrective action: none
 
crDead10warning 
 setdeadtime=yes and NPIXEL $-$ NBELOW $-$ NABOVE $<$ sum of pixels in valid events. Flag as bad and continue
corrective action: none
 
makeGti13warning 
 all frames flagged as bad. Empty output GTI file. Continue
corrective action: check the log (with verbosity set to 4 at least) to know why those frames were rejected
 
testDrop12warning 
 more than 50% time lost. Continue
corrective action: check in the log that nothing went wrong
 
putGatti10warning 
 setgatti=yes, but less than 255 frames. set GATTI=ROW
corrective action: if this results in systematic spGatti11 warnings in emevents, you may add the offset manually
 
putGatti11warning 
 setgatti=yes, GATTI on but no GATTIFLG=1. Skip PUT_GATTI. The truncated events cannot be identified
corrective action: none. This is hopeless
 
putGatti12warning 
 setgatti=yes, GATTI on and GATTIFLG not found at expected periodicity. Continue, it may have occurred within a missing frame
corrective action: if this results in systematic spGatti11 warnings in emevents, do not trust the flare screening light curve
 
putGatti14warning 
 setgatti=yes and interval between two successive GATTI flags not equal to 510. Skip PUT_GATTI. The truncated events cannot be identified
corrective action: check the log for frame renumbering messages. If you see where emframes erred, try renumbering the frames manually and run emframes again
 
createOutput10warning 
 incoherence between FRMTIME and GATTIFLG. Continue anyway (FRMTIME is probably wrong, this does not affect the processing)
corrective action: inform SOC (this should not occur in any mode)
 
adjustTimetag10warning 
 reconstructed source position is outside CCD. Flag frame and continue (most likely an attitude error)
corrective action: if this is systematic, the target position RA_OBJ / DEC_OBJ may be wrong. Try providing the source position manually setting srcra/dec
 

XMM-Newton SOC -- 2021-11-30