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   SASv18.0   SASv18.0_Installation   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing SASv17.0/84260
Full headers

From: enza.magaudda@uni-tuebingen.de
Subject: Problem with epiclccorr pipeline
Compose reply
Download message
Move To:
3 replies: 1 2 3
3 followups: 1 2 3

Private message: yes  no

Notes:

Notification:


Date: Wed, 31 Oct 2018 17:01:07 GMT
From: enza.magaudda@uni-tuebingen.de
To: xmmhelp@sciops.esa.int
CC: enza.magaudda@uni-tuebingen.de
Subject: Problem with epiclccorr pipeline
Full_Name: Enza Magaudda
Submission from: (NULL) (193.147.152.102)


Hello,
I would like to have some information about how epiclccorr works. I read the
handbook but unfortunately I did not have the answers about my problem.
When I subtract the background using 'epiclccorr', I obtain a RATE higher than
the RATE of the source lightcurve before the background subtracting. The problem
seems to be almost resolved if I put applyabsolutecorrection=no. I was not be
able to understand why this happens and how can I totally resolved the problem.

Just to be clear I use the SAS version 1.3 and I'm analysing the observational
data about EPIC201718613. My commands are listed below.

evselect table=pn_evlist_CLEANED.ds energycolumn=PI
expression='#XMMEA_EP&&(PATTERN<=4)&& ((X,Y) IN
circle(26319.715,27943.864,380))
&&(PI in [200:10000])' withrateset=yes rateset="
PN_source_lightcurve_raw.lc"
timebinsize=100 maketimecolumn=yes makeratecolumn=yes

evselect table=pn_evlist_CLEANED.ds energycolumn=PI
expression='#XMMEA_EP&&(PATTERN<=4)&& ((X,Y) IN
circle(27154.671,26272.556,1047.3455))&& (PI in [200:10000])'
withrateset=yes
rateset="PN_background_lightcurve_raw.lc" timebinsize=100 maketimecolumn=yes
makeratecolumn=yes

epiclccorr srctslist=PN_source_lightcurve_raw.lc eventlist=pn_evlist_CLEANED.ds
outset=PN_lccorr.lc bkgtslist=PN_background_lightcurve_raw.lc withbkgset=yes
applyabsolutecorrections=yes

Best Regards,
Enza Magaudda


Reply 1

Resend
From: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
To: enza.magaudda@uni-tuebingen.de
Subject: Re: Problem with epiclccorr pipeline (PR#84260)
Date: Fri Nov  2 08:39:55 2018
Dear Enza Magaudda,

In order to reproduce, and eventually, solve you problem we need morr
information:

You say

Just to be clear I use the SAS version 1.3 and I'm analysing the observational
data about EPIC201718613. My commands are listed below.


Please confirm the SAS verstion you are using (the current one is SAS 17.0) 

Also, please send the obsid you are working with (EPIC201718613 is not an
obsid).

Thanks in advance,


Rosario Gonzalez-Riestra
XMM-SOC User Support Group


Followup 1

Compose reply
Download message
Date: Sun, 04 Nov 2018 12:35:55 +0100
From: Enza Magaudda <enza.magaudda@uni-tuebingen.de>
To: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
Subject: Re: Problem with epiclccorr pipeline (PR#84260)
Dear Rosario Gonzalez,
thank you so much for your reply.
Sorry I was not so clear. I use SAS 17.0 and the obsID of my target is  
0820460101.
The same thing happens also with the followed obsID 0820460201 so I  
don't think it depends on this.

Best Regards,
Enza Magaudda

Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int> ha scritto:

> Dear Enza Magaudda,
>
> In order to reproduce, and eventually, solve you problem we need morr
> information:
>
> You say
>
> Just to be clear I use the SAS version 1.3 and I'm analysing the  
> observational
> data about EPIC201718613. My commands are listed below.
>
>
> Please confirm the SAS verstion you are using (the current one is SAS 17.0)
>
> Also, please send the obsid you are working with (EPIC201718613 is not an
> obsid).
>
> Thanks in advance,
>
>
> Rosario Gonzalez-Riestra
> XMM-SOC User Support Group
>
>
> This message is intended only for the recipient(s) named above. It  
> may contain proprietary information and/or
> protected content. Any unauthorised disclosure, use, retention or  
> dissemination is prohibited. If you have received
> this e-mail in error, please notify the sender immediately. ESA  
> applies appropriate organisational measures to protect
> personal data, in case of data privacy queries, please contact the  
> ESA Data Protection Officer (dpo@esa.int).




Reply 2

Resend
From: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
To: enza.magaudda@uni-tuebingen.de
Subject: Re: Problem with epiclccorr pipeline (PR#84260)
Date: Mon Nov  5 11:25:01 2018
Dear  Enza Magaudda,

The fact that the RATE in the output light curve produced by 'epiclccorr' is
higher than the one produced by 'evselect' is normal.

evselect just 'counts' the number of events received in a given period of time
(that is, it makes an histogram), whil 
epiclccorr applies a number of corrections, the most important one in the
'useful' time within each time bin (what are called "Relative Corrections": Dead
time, GTIs, exposure...) . Since not 100% of the time in each bin is useful, the
final RATE is higher tham the value given by evselect.

Regards

Rosario


Followup 2

Compose reply
Download message
Date: Tue, 06 Nov 2018 17:18:02 +0100
From: Enza Magaudda <enza.magaudda@uni-tuebingen.de>
To: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
Subject: Re: Problem with epiclccorr pipeline (PR#84260)
Dear Raosario Gonzalez,
thank you so much for your reply. You made clear what I have supposed  
about the pipeline. One more thing what do you mean exactly with DEAD  
TIME?

Best Regards,
Enza Magaudda
Quoting Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>:

> Dear  Enza Magaudda,
>
> The fact that the RATE in the output light curve produced by 'epiclccorr'
is
> higher than the one produced by 'evselect' is normal.
>
> evselect just 'counts' the number of events received in a given  
> period of time
> (that is, it makes an histogram), whil
> epiclccorr applies a number of corrections, the most important one in the
> 'useful' time within each time bin (what are called "Relative  
> Corrections": Dead
> time, GTIs, exposure...) . Since not 100% of the time in each bin is  
> useful, the
> final RATE is higher tham the value given by evselect.
>
> Regards
>
> Rosario
>
> This message is intended only for the recipient(s) named above. It  
> may contain proprietary information and/or
> protected content. Any unauthorised disclosure, use, retention or  
> dissemination is prohibited. If you have received
> this e-mail in error, please notify the sender immediately. ESA  
> applies appropriate organisational measures to protect
> personal data, in case of data privacy queries, please contact the  
> ESA Data Protection Officer (dpo@esa.int).





Reply 3

Resend
From: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
To: enza.magaudda@uni-tuebingen.de
Subject: Re: Problem with epiclccorr pipeline (PR#84260)
Date: Tue Nov  6 16:40:53 2018
Dear Enza Magaudda,

In few words, the deadtime is the time that it takes to read the detector (the
detector does not collect data while it is being read). It is different for the
different instrument modes.


Rosario


Followup 3

Compose reply
Download message
Date: Tue, 06 Nov 2018 17:50:40 +0100
From: Enza Magaudda <enza.magaudda@uni-tuebingen.de>
To: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
Subject: Re: Problem with epiclccorr pipeline (PR#84260)
Ok, Thank you so much again.

Have a nice evening.
Enza
Quoting Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>:

> Dear Enza Magaudda,
>
> In few words, the deadtime is the time that it takes to read the  
> detector (the
> detector does not collect data while it is being read). It is  
> different for the
> different instrument modes.
>
>
> Rosario
>
>
> This message is intended only for the recipient(s) named above. It  
> may contain proprietary information and/or
> protected content. Any unauthorised disclosure, use, retention or  
> dissemination is prohibited. If you have received
> this e-mail in error, please notify the sender immediately. ESA  
> applies appropriate organisational measures to protect
> personal data, in case of data privacy queries, please contact the  
> ESA Data Protection Officer (dpo@esa.int).




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   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