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/85531
Full headers

From: Donato Capozzi <donato.capozzi@gmail.com>
Subject: Use of boolean logic in the task multiespecget
Compose reply
Download message
Move To:
1 replies: 1
0 followups:

Private message: yes  no

Notes:

Notification:


From: Donato Capozzi <donato.capozzi@gmail.com>
Date: Sun, 11 Aug 2019 18:15:20 +0200
Subject: Use of boolean logic in the task multiespecget
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
--000000000000e79835058fd9b8aa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

 Dear Help Desk

I am working on some data of the source 1RXSJ234024.3-532913 (Obs.
0670170401). I choose as extraction region for the MOS data an annulus with
the exclusion of a small circle containing a secondary source that could
contaminate the data (look at the attached picture).

Evselect accepts without problem this region definition, using as
Expression: expression=3D'#XMMEA_EM && (PATTERN<=3D12) &&
((X,Y) IN
annulus(27492.4, 27112.5, 800, 1300)) && .not.((X,Y) IN circle(26310.4,
27306.4, 250))'.

On the other hand I wanted to use multiespecget in order to merge the PN
and MOS data, but unfortunately I wasn=E2=80=99t able to make this task acc=
ept this
region definition. I tried it using boolean logic, like in evselect, but
without success:

multiespecget tables=3D'MOS1_401.fits MOS2_401.fits PN_401.fits'
srcexp=3D'(RA,DEC) in circle(355.0967821,-53.4822167,0.008333)'
backexp=3D'(RA,DEC) in annulus(355.0967821,-53.4822167, 0.011111, 0.0180555=
)
&& .not.(in circle(355.1243697, -53.47956382, 0.0034722)'
calindexsets=3D'ccf.cif ccf.cif ccf.cif' withmultiEPICspec=3Dyes.

Is there some way to run the task multiespecget using an extraction region
that isn=E2=80=99t a simple circle or an annulus?

Thanks for your attention and best regards.

Donato Capozzi

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

<div dir=3D"ltr">
=09
=09


Dear Help Desk<br><br>I am working on some data of the source
1RXSJ234024.3=
-532913 (Obs. 0670170401). I choose as extraction region for the MOS data a=
n annulus with the exclusion of a small circle containing a secondary sourc=
e that could contaminate the data (look at the attached
picture).<br><br>Ev=
select accepts without problem this region definition, using as Expression:=
 expression=3D&#39;#XMMEA_EM &amp;&amp; (PATTERN&lt;=3D12)
&amp;&amp; ((X,Y=
) IN annulus(27492.4, 27112.5, 800, 1300)) &amp;&amp; .not.((X,Y) IN
circle=
(26310.4, 27306.4, 250))&#39;.<br><br>On the other hand I wanted
to use mul=
tiespecget in order to merge the PN and MOS data, but unfortunately I wasn=
=E2=80=99t able to make this task accept this region definition. I tried it=
 using boolean logic, like in evselect, but without
success:<br><br>multies=
pecget tables=3D&#39;MOS1_401.fits MOS2_401.fits PN_401.fits&#39;
srcexp=3D=
&#39;(RA,DEC) in circle(355.0967821,-53.4822167,0.008333)&#39;
backexp=3D&#=
39;(RA,DEC) in annulus(355.0967821,-53.4822167, 0.011111, 0.0180555)
&amp;&=
amp; .not.(in circle(355.1243697, -53.47956382, 0.0034722)&#39; calindexset=
s=3D&#39;ccf.cif ccf.cif ccf.cif&#39;
withmultiEPICspec=3Dyes.<br><br>Is th=
ere some way to run the task multiespecget using an extraction region that =
isn=E2=80=99t a simple circle or an annulus?<br><br>Thanks for your
attenti=
on and best regards.<br><br>Donato Capozzi</div>

--000000000000e79835058fd9b8aa--


Reply 1

Resend
From: Jacobo Ebrero <xmmhelp@sciops.esa.int>
To: donato.capozzi@gmail.com
Subject: Re: Use of boolean logic in the task multiespecget (PR#555%2)
Date: Mon Aug 12 09:47:58 2019
Dear Donato,

I am afraid that the only valid selection expression for the parameters srcexp
and backexp in miltiespecget is a CIRCLE. This is also mentioned in the
description of the parameters here:

https://xmm-tools.cosmos.esa.int/external/sas/current/doc/multiespecget/node7.html

It is hardcoded in the source code of the task, and it was done on purpose due
to the complexity in handling all three EPIC cameras at one time.

So, in your particular case, you may need to find a workaround for your
background extraction (e.g. choosing a circular region in an area devoid of
sources, in the same CCD, and keeping the same Y coordinate as your source of
interest).

Best regards,
Jacobo

----------------------
Dr. Jacobo Ebrero
XMM-Newton SOC
Community Support and Scientific Planning Team

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