Up to top level
AO15   AO16   AO17   AO18   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv16.0   SASv16.0_Installation   SASv16.1   SASv16.1_Installation   SASv17.0   SASv17.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing EPICMOS/9420
Full headers

From: dr@star.sr.bham.ac.uk
Subject: OoT correction and epic MOS
Compose reply
Download message
Move To:
1 replies: 1
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Mon, 3 Nov 2003 11:20:12 GMT
From: dr@star.sr.bham.ac.uk
To: xmmhelp@xmm.vilspa.esa.es
CC: dr@star.sr.bham.ac.uk
Subject: OoT correction and epic MOS
Full_Name: Dan Reed
Submission from: (NULL) (147.188.32.208)


Hi there

I have XMM data from epic MOS cameras (full window mode) and not sure as to
whether an Out-of-time (OoT) correction is required for this instrument/mode.
All documentation I have read give examples of its use for the PN camera and
never a mention toward either of the MOS. I know the SAS task epchain (a PN
task) is called to create an OoT event list. Task emchain (a MOS task) doesnt
include an OoT parameter. I would be very grateful for any advice you could give
me.

Cheers

Dan Reed


Reply 1

Resend
From: Maria Santos-Lleo <xmmhelp@xmm.vilspa.esa.es>
To: dr@star.sr.bham.ac.uk
Subject: Re: OoT correction and epic MOS (PR#9420)
Date: Tue Nov  4 17:07:25 2003
Dear Dan, 

The number of Out of Time events in MOS full frame mode is only 0.35 per cent
and therefore a rather low percentage. For other modes you can check the 
XMM-Newton Users Handbook at 

http://xmm.vilspa.esa.es/

under 'XMM-Newton Proposer's Info and Manuals

or go directly to the 'out-of-time-events' section at 

http://xmm.vilspa.esa.es/external/xmm_user_support/documentation/uhb/node39.html

Currently there is no procedure to deal with these OoT within SAS 
in a similar way as it is for pn. However, in most cases there is no
need to correct for such an small effect

I hope this answers your question

With best regards

Maria


Maria Santos-Lleo, 
XMM-Newton SOC 
User Support Group

Up to top level
AO15   AO16   AO17   AO18   Backgrounds   Calibration   Conference   Data   Docs   EPICMOS   EPICpn   Feedback   Gallery   Misc   OM   Pending   PhD_Theses   Publications   RGS   RadMonitor   SAS_Hardware   SAS_WS   SASv16.0   SASv16.0_Installation   SASv16.1   SASv16.1_Installation   SASv17.0   SASv17.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest


Please make your (short) question the subject of your request!


Web interface using JitterBug ... back to the XMM home page