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 EPICMOS/83223
Full headers

From: isabel.lima@inpe.br
Subject: What file is used to extract the background in the timing mode: ImagingEvts or TimingEvts?
Compose reply
Download message
Move To:
2 replies: 1 2
1 followups: 1

Private message: yes  no

Notes:

Notification:


Date: Fri, 13 Apr 2018 21:09:11 GMT
From: isabel.lima@inpe.br
To: xmmhelp@sciops.esa.int
CC: isabel.lima@inpe.br
Subject: What file is used to extract the background in the timing mode: ImagingEvts or TimingEvts? 
Full_Name: Isabel de Jesus Lima
Submission from: (NULL) (150.163.28.101)


I could extract the light curve using the TimingEvts file, but the region with
background is very small. So we would like to compare the results using the bck
from imagingEvts. However, we could not run epiclccor without error. They are: 
 
** epiclccorr: error (attributableNotFound), Could not find attribute with
qualified name Bkg_light_curve.fits:RATE%EXPOSURE in attributable set RATE

or 

** epiclccorr: error (blockNotFound), Could not find block with qualified name
'bkg_testte.fits:RATE' in dataset with name 'bkg_testte.fits'

Cheers,

Isabel Lima


Reply 1

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: isabel.lima@inpe.br
Subject: Re: What file is used to extract the background in the timing mode: ImagingEvts or TimingEvts? (PR#83223)
Date: Mon Apr 16 07:00:56 2018
Dear Isabel de Jesus Lima,

 I hope I understood your question correctly, you want to extract a timing mode
light curve using a background region file created for an image mode events
file?

The Timing Mode events file has only one spatial dimension, and defining a
background region region thus works differently than in image mode.

 An example how to chose regions for source and background in timing mode
observations can be seen in the spectral thread:
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-pn-spectrum-timing

You can therefore not recycle a background extraction region for an image mode
events file for timing mode events file and will have to define the region using
only the RAWX column.

If I understood your question correctly, the problem has already occurred during
the light curve extraction while the lccorr errors are followup errors.

 Best wishes,
Jan-Uwe Ness



> 
> 
> I could extract the light curve using the TimingEvts file, but the region
with
> background is very small. So we would like to compare the results using the
bck
> from imagingEvts. However, we could not run epiclccor without error. They
are:

>  
> ** epiclccorr: error (attributableNotFound), Could not find attribute with
> qualified name Bkg_light_curve.fits:RATE%EXPOSURE in attributable set RATE
> 
> or 
> 
> ** epiclccorr: error (blockNotFound), Could not find block with qualified
name
> 'bkg_testte.fits:RATE' in dataset with name 'bkg_testte.fits'
> 
> Cheers,
> 
> Isabel Lima
> 
> 


Followup 1

Compose reply
Download message
Date: Mon, 16 Apr 2018 11:54:42 -0300
From: isabel.lima@inpe.br
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Cc: <claudia.rodrigues@inpe.br>
Subject: Re: What file is used to extract the background in the timing mode:
--=_86abf26ab9d80c41eee57f47b3575c96
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=UTF-8

 

Dear Jan-Uwe Ness, 

Thanks for your prompt reply. I comment it
below. I also hope to make my doubt clear now. I am using MOS. 

Yes. I
would like to extract a timing mode light curve using the bkg from the
imaging mode events. For spectrum extraction, I have got no problem. The
source + bkg were extracted from timing mode and bkg were extracted from
imaging mode. If I extract src+bkg and bkg from timing events file, also
no problem. I have only got problem, in light curve extraction using bkg
from imaging events file. 

I can run evselect without errors (but see
below). The error occurs when I run epiclccorr. I show below two
attempts of reduction. 

In the attempt 1, we have obtained the bkg
light curve with rates different from zero. But, when I run epiclccorr
occurred the error associated with DETX and DETY. In extracting the bck
for spectrum creation, I used the same region in the detector. 

In the
attempt 2, the bkg light curve created by evselect has rates = zero, but
no error message is displayed when we run evselect. However, something
must be wrong already in evselect. 

== Attempt 1 -_ ImagingEvts - bkg
region is a square_ 

evselect
table=0334_0111180401_EMOS1_S004_ImagingEvts.ds energycolumn=PI
expression='#XMMEA_EM && (PATTERN<=1 || PATTERN==3) && 
(PI in
[200:700]) && ((DETX,DETY) in
BOX(23377.167,12741.611,10611.111,6833.3333,0))' withrateset=yes
rateset="1mosBkg_light_curve.fits" timebinsize=25 xcolumn=DETX
ycolumn=DETY maketimecolumn=yes makeratecolumn=yes (NO Error)


epiclccorr srctslist=mos1_source_lightcurve_raw.lc
eventlist=1mos_barycen.fits outset=mos1_lightcurve_lccorr.lc
bkgtslist=1mosBkg_light_curve.fits withbkgset=yes
applyabsolutecorrections=yes 

** epiclccorr: error (blockNotFound),
Could not find block with qualified name 'tmp.ds:DETX,DETY' in dataset
with name 'tmp.ds' 

_ _ 

_== Attempt 2 - ImagingEvts - bkg is a
circle:_ 

evselect table=0334_0111180401_EMOS1_S004_ImagingEvts.ds
energycolumn=PI expression='#XMMEA_EM&&(PATTERN<=1 || PATTERN==3)
&& (PI
in [200:700]) && ((X,Y) IN circle(24886.7,24187.4,100))' withrateset=yes
rateset="TESTE0_Bkg_light_curve.fits" timebinsize=25 maketimecolumn=yes
makeratecolumn=yes (NO ERROR) 

epiclccorr
srctslist=mos1_source_lightcurve_raw.lc eventlist=1mos_barycen.fits
outset=mos1_lightcurve_lccorr.lc bkgtslist=TESTE0_Bkg_light_curve.fits
withbkgset=yes applyabsolutecorrections=yes 

 ** epiclccorr: error
(attributableNotFound), Could not find attribute with qualified name
TESTE0_Bkg_light_curve.fits:RATE%EXPOSURE in attributable set RATE


Thanks!! 

Isabel 

Em 16-04-2018 04:00, Jan-Uwe Ness escreveu: 

>
Dear Isabel de Jesus Lima,
> 
> I hope I understood your question
correctly, you want to extract a timing mode
> light curve using a
background region file created for an image mode events
> file?
> 
> The
Timing Mode events file has only one spatial dimension, and defining a
>
background region region thus works differently than in image mode.
> 
>
An example how to chose regions for source and background in timing
mode
> observations can be seen in the spectral thread:
>
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-pn-spectrum-timing
>

> [1]You can therefore not recycle a background extraction region for
an image mode
> events file for timing mode events file and will have to
define the region using
> only the RAWX column.
> 
> If I understood
your question correctly, the problem has already occurred during
> the
light curve extraction while the lccorr errors are followup errors.
> 
>
Best wishes,
> Jan-Uwe Ness
> 
>> I could extract the light curve using
the TimingEvts file, but the region
> 
> with
> 
>> background is very
small. So we would like to compare the results using the
> 
> bck
> **
epiclccorr: error (attributableNotFound), Could not find attribute with
qualified name Bkg_light_cur
> 
>> with qualified 
>> 
>> name
>>
'bkg_testte.fits:RATE' in dataset with name 'bkg_testte.fits' Cheers,
I
> lockquote> 
> 
> This message is sent for information and/or
discussion purposes only.
> It shall neither be bi> ve. It may contain
proprietary information and/or protected content. Any unauth
> sure,
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). Thank you.

 

Links:
------
[1]
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-pn-spectrum-timing

--=_86abf26ab9d80c41eee57f47b3575c96
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<

Message of length 11944 truncated


Reply 2

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: isabel.lima@inpe.br
Subject: Re: What file is used to extract the background in the timing mode: ImagingEvts or TimingEvts? (PR#83223)
Date: Wed Apr 18 07:14:49 2018
Dear Isabel,

 the fact that the creation of spectra has not crashed does not mean the
resulting products are meaningful. The Imaging and Timing modes are very
different in their nature, and region files for Imaging modes events files
cannot be applied to timing mode events files.

 In imaging mode you have two spatial coordinates, X and Y (in different units),
and you can thus define box, circular, annular, etc regions in two dimensions.
For Timing Mode, there is only one spatial dimension, RAWX. While there is also
a RAWY column in the events file, this corresponds to time and thus has a
completely different meaning than the RAWY column in image modes. Therefore, a
box filter expression on RAWY can formally be performed successfully, but you
effectively filter on time. With a very narrow time interval, I could imagine
that epiclccorr fails while the creation of a spectrum runs successfully also
for a short time interval.

I had sent you the pn spectral extraction thread for timing mode because it is
illustrated how to define the spatial extraction filter. There is also a
corresponding thread for MOS timing mode:
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-mos-spectrum-timing
The filter expression will have to look something like this:
expression='(FLAG==0) && (PATTERN<=0) && (RAWX>=278)
&& (RAWX<=338)'
thus no filtering on RAWY for MOS.

Best wishes,
Jan-Uwe

P.S. All threads can found under
https://www.cosmos.esa.int/web/xmm-newton/sas-threads


> 
> Dear Jan-Uwe Ness, 
> 
> Thanks for your prompt reply. I comment it
> below. I also hope to make my doubt clear now. I am using MOS. 
> 
> Yes. I
> would like to extract a timing mode light curve using the bkg from the
> imaging mode events. For spectrum extraction, I have got no problem. The
> source + bkg were extracted from timing mode and bkg were extracted from
> imaging mode. If I extract src+bkg and bkg from timing events file, also
> no problem. I have only got problem, in light curve extraction using bkg
> from imaging events file. 
> 
> I can run evselect without errors (but see
> below). The error occurs when I run epiclccorr. I show below two
> attempts of reduction. 
> 
> In the attempt 1, we have obtained the bkg
> light curve with rates different from zero. But, when I run epiclccorr
> occurred the error associated with DETX and DETY. In extracting the bck
> for spectrum creation, I used the same region in the detector. 
> 
> In the
> attempt 2, the bkg light curve created by evselect has rates = zero, but
> no error message is displayed when we run evselect. However, something
> must be wrong already in evselect. 
> 
> == Attempt 1 -_ ImagingEvts - bkg
> region is a square_ 
> 
> evselect
> table=0334_0111180401_EMOS1_S004_ImagingEvts.ds energycolumn=PI
> expression='#XMMEA_EM && (PATTERN<=1 || PATTERN==3) && 
> (PI in
> [200:700]) && ((DETX,DETY) in
> BOX(23377.167,12741.611,10611.111,6833.3333,0))' withrateset=yes
> rateset="1mosBkg_light_curve.fits" timebinsize=25 xcolumn=DETX
> ycolumn=DETY maketimecolumn=yes makeratecolumn=yes (NO Error)
> 
> 
> epiclccorr srctslist=mos1_source_lightcurve_raw.lc
> eventlist=1mos_barycen.fits outset=mos1_lightcurve_lccorr.lc
> bkgtslist=1mosBkg_light_curve.fits withbkgset=yes
> applyabsolutecorrections=yes 
> 
> ** epiclccorr: error (blockNotFound),
> Could not find block with qualified name 'tmp.ds:DETX,DETY' in dataset
> with name 'tmp.ds' 
> 
> _ _ 
> 
> _== Attempt 2 - ImagingEvts - bkg is a
> circle:_ 
> 
> evselect table=0334_0111180401_EMOS1_S004_ImagingEvts.ds
> energycolumn=PI expression='#XMMEA_EM&&(PATTERN<=1 ||
PATTERN==3) && (PI
> in [200:700]) && ((X,Y) IN circle(24886.7,24187.4,100))'
withrateset=yes
> rateset="TESTE0_Bkg_light_curve.fits" timebinsize=25 maketimecolumn=yes
> makeratecolumn=yes (NO ERROR) 
> 
> epiclccorr
> srctslist=mos1_source_lightcurve_raw.lc eventlist=1mos_barycen.fits
> outset=mos1_lightcurve_lccorr.lc bkgtslist=TESTE0_Bkg_light_curve.fits
> withbkgset=yes applyabsolutecorrections=yes 
> 
>  ** epiclccorr: error
> (attributableNotFound), Could not find attribute with qualified name
> TESTE0_Bkg_light_curve.fits:RATE%EXPOSURE in attributable set RATE
> 
> 
> Thanks!! 
> 
> Isabel 
> 
> Em 16-04-2018 04:00, Jan-Uwe Ness escreveu: 
> 
>>
> Dear Isabel de Jesus Lima,
>> 
>> I hope I understood your question
> correctly, you want to extract a timing mode
>> light curve using a
> background region file created for an image mode events
>> file?
>> 
>> The
> Timing Mode events file has only one spat

Message of length 6335 truncated

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