Up to top level
AO15   AO16   AO17   AO18   AO19   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   SASv18.0   SASv18.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing EPICpn/8562
Full headers

From: cocj@roe.ac.uk
Subject: all EPIC detection?
Compose reply
Download message
Move To:
1 replies: 1
1 followups: 1

Private message: yes  no

Notes:

Notification:


Date: Tue, 20 May 2003 14:40:42 GMT
From: cocj@roe.ac.uk
To: xmmhelp@xmm.vilspa.esa.es
CC: cocj@roe.ac.uk
Subject: all EPIC detection?
Full_Name: Olivia Johnson
Submission from: (NULL) (195.194.120.192)


I have used emosaic to combine my EPIC data into a MOS1+MOS2+pn image, and want
to
combine the corresponding exposure maps as suggested on the MPE Cookbook
'Create
EPIC PN and MOS Exposure Map page (with merge, with farith, or with emosaic?). 
The 
individual exposure maps seem to be in units of seconds.  How are the differing

effective areas of pn and MOS somehow taken into account so that the combined
map 
is appropriate for the merged image?  Can a single image and exposure map then
be 
used for source detection? This seems to have been done with the Lockman Hole
deep 
survey data (Hasinger et al. A&A 365, L45), but I'm uncertain how.

Thanks very much, 
-olivia


Reply 1

Resend
From: Matteo Guainazzi <xmmhelp@xmm.vilspa.esa.es>
To: cocj@roe.ac.uk
Subject: Re: all EPIC detection? (PR#8562)
Date: Wed May 21 12:00:46 2003
Dear Olivia,

 the different effective areas of the detectors are not automatically
taken into account when exposure maps of different instrumentse are
merged, as their units are - as you have noticed - seconds. One needs
to weight the exposure maps for the effective area of each detector
in the energy band, where the exposure maps have been calculated. The
weights need to be calculated manually (i.e., there is no SAS tool for
it). The corresponding numbers can be extracted from the User Handbook,
or from an effective area file.

 Regards,

 Matteo Guainazzi
 XMM-Newton Science Operations Center
 User Support Group


Followup 1

Compose reply
Download message
Date: Wed, 21 May 2003 13:05:41 +0100 (BST)
From: Olivia Johnson <cocj@roe.ac.uk>
To: Matteo Guainazzi <xmmhelp@xmm.vilspa.esa.es>
Subject: Re: all EPIC detection? (PR#8562)
Thanks, I'll do that.  Once corrected, is it then valid to use the single
exposure map and merged MOS1+MOS2+pn image in the standard detection 
algorithms?  

Thanks again,

-olivia



On Wed, 21 May 2003, Matteo Guainazzi wrote:

> Dear Olivia,
> 
>  the different effective areas of the detectors are not automatically
> taken into account when exposure maps of different instrumentse are
> merged, as their units are - as you have noticed - seconds. One needs
> to weight the exposure maps for the effective area of each detector
> in the energy band, where the exposure maps have been calculated. The
> weights need to be calculated manually (i.e., there is no SAS tool for
> it). The corresponding numbers can be extracted from the User Handbook,
> or from an effective area file.
> 
>  Regards,
> 
>  Matteo Guainazzi
>  XMM-Newton Science Operations Center
>  User Support Group
> 
> 



Up to top level
AO15   AO16   AO17   AO18   AO19   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   SASv18.0   SASv18.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