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 esas/47855
Full headers

From: Georgiana Ogrean <g.ogrean@jacobs-university.de>
Subject: mos-spectra/pn-spectra region selection
Compose reply
Download message
Move To:
8 replies: 1 2 3 4 5 6 7 8
6 followups: 1 2 3 4 5 6

Private message: yes  no

Notes:

Notification:


Date: Tue, 17 May 2011 14:32:25 +0200
Subject: mos-spectra/pn-spectra region selection
From: Georgiana Ogrean <g.ogrean@jacobs-university.de>
To: xmmhelp@sciops.esa.int
--001517476980eaf0d304a377f612
Content-Type: text/plain; charset=ISO-8859-1

Dear Helpdesk,

In the XMM-ESAS cookbook, it is stated that mos-spectra and pn-spectra only
accept circle and annulus region selections. Is there an easy way to change
the code to be able to use a different region shape? I would need an
ellipse.

Thank you and best wishes,
Georgiana

--001517476980eaf0d304a377f612
Content-Type: text/html; charset=ISO-8859-1

Dear Helpdesk,<br><br>In the XMM-ESAS cookbook, it is stated that
mos-spectra and pn-spectra only accept circle and annulus region selections. Is
there an easy way to change the code to be able to use a different region shape?
I would need an ellipse.<br>
<br>Thank you and best
wishes,<br>Georgiana<br><br><br>

--001517476980eaf0d304a377f612--


Reply 1

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: g.ogrean@jacobs-university.de
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
Date: Tue May 17 14:37:51 2011
Dear Georgiana,

That comment might be outdated, it should accept ellipses. Please try
and let me know if you have any problems.

Thanks,

Ignacio de la Calle
XMM-Newton SOC


> --001517476980eaf0d304a377f612
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Dear Helpdesk,
> 
> In the XMM-ESAS cookbook, it is stated that mos-spectra and pn-spectra
only
> accept circle and annulus region selections. Is there an easy way to
change
> the code to be able to use a different region shape? I would need an
> ellipse.
> 
> Thank you and best wishes,
> Georgiana
> 
> --001517476980eaf0d304a377f612
> Content-Type: text/html; charset=ISO-8859-1
> 
> Dear Helpdesk,<br><br>In the XMM-ESAS cookbook, it is stated
that mos-spectra
> and pn-spectra only accept circle and annulus region selections. Is there
an
> easy way to change the code to be able to use a different region shape? I
would
> need an ellipse.<br>
> <br>Thank you and best
wishes,<br>Georgiana<br><br><br>
> 
> --001517476980eaf0d304a377f612--
> 
> 


Reply 2

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: g.ogrean@jacobs-university.de
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
Date: Wed May 18 08:14:35 2011
Dear Georgiana,

This thread has just gone public now:

http://xmm.esac.esa.int/sas/current/documentation/threads/esasimage_thread.shtml

it might be of use to you. Since it has just now being released,
let me know if anything is unclear or if you see anything wrong.

Many thanks,

Ignacio de la Calle
XMM-Newton SOC 


Followup 1

Compose reply
Download message
Date: Mon, 23 May 2011 17:23:24 +0200
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
From: Georgiana Ogrean <g.ogrean@jacobs-university.de>
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
--20cf3054a55567619304a3f30da9
Content-Type: multipart/alternative; boundary=20cf3054a55567616304a3f30da6

--20cf3054a55567616304a3f30da6
Content-Type: text/plain; charset=ISO-8859-1

Dear Ignacio,

I ran pn-spectra with an elliptical region defined as:

&&((DETX,DETY) in ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))

and it seemed to have worked just fine. However, when I run pn_back I get
the output attached at the end of this email, and no background spectrum is
created. Do you know why this happens? If it matters, I am using a new
pn-spectra file (attached), which was emailed to me by Nora Loiseau a couple
of weeks ago.

The files created by pn-spectra are:

pnS003-im${i}-400-7200-oot.fits ........ with i=1,2,3,4
pnS003-im${i}-400-7200.fits ........ with i=1,2,3,4
pnS003-${i}fc-oot.pi ........ with i=1,2,3,4
pnS003-${i}fc.pi ........ with i=1,2,3,4
pnS003-${i}ff-oot.pi ........ with i=1,2,3,4
pnS003-${i}ff.pi ........ with i=1,2,3,4
pnS003-${i}oc-oot.pi ........ with i=1,2,3,4
pnS003-${i}oc.pi ........ with i=1,2,3,4
pnS003-${i}obj-oot.pi ........ with i=1,2,3,4
pnS003-${i}obj.pi ........ with i=1,2,3,4
pnS003-exp-im-400-7200.fits
pnS003-mask-im-400-7200.fits
pnS003-obj-im-400-7200-oot.fits
pnS003-obj-im-400-7200.fits
pnS003.arf
pnS003.rmf
pnS003-obj-oot.pi
pnS003-obj.pi
pnS003-obj-im-det-400-7200-oot.fits
pnS003-mask-im-det-400-7200.fits
pnS003-exp-im-det-400-7200.fits
pnS003-obj-im-det-400-7200.fits
pnS003-obj-im-sp-det.fits
pnS003-obj-im-oot.fits
pnS003-exp-im.fits
pnS003-mask-im.fits
pnS003-obj-im.fits
pnS003-corn-oot.fits
pnS003-corn.fits

I'm not sure why pn_back says pnS003-4obj.pi is missing, since it's clearly
there. I get similar warnings when running mos_back, but I presume I can
ignore them, right? For MOS, it does create background spectra.

Thanks,
Georgiana

pn_back prefix=S003
caldb=/people/data/astrosoft/xmmsas_11.0.0/ccf/esas_caldb diag=0 elow=400
ehigh=7200 quad1=1 quad2=1 quad3=1 quad4=1

 xmmdir:
/people/data/astrosoft/xmmsas_11.0.0/ccf/esas_caldb

 Quiescent particle background data file:
 /people/data/astrosoft/xmmsas_11.0.0/ccf/esas_caldb/pn-qpb.fits.gz

 diag:  0
 prefix: S003
 el, eh:  400 7200
 Quadrant selection 1 1 1 1

 Create the OOT subtracted spectrum

 Observed spectrum:
pnS003-obj.pi


 PN Mode: PrimeFullWindow
 OOT Scale:   0.0630

 Spectrum RMF:
pnS003.rmf


 OOT spectrum:
pnS003-obj-oot.pi


 Exposure:   39715.7 s

 Process the individual quadrant observation data and create OOT
 subtracted spectra and exposures which are area and exposure normalized.

 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 PN_BACK POSITION 04
 missing file: pnS003-4obj.pi

On Tue, May 17, 2011 at 4:37 PM, Ignacio de la Calle <xmmhelp@sciops.esa.int
> wrote:

> Dear Georgiana,
>
> That comment might be outdated, it should accept ellipses. Please try
> and let me know if you have any problems.
>
> Thanks,
>
> Ignacio de la Calle
> XMM-Newton SOC
>

--20cf3054a55567616304a3f30da6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Ignacio,<br><br>I ran pn-spectra with an elliptical region
defined as:=
<br><br>&amp;&amp;((DETX,DETY) in
ellipse(1959.6,-1803.8,4623.65,1372.90,10=
.0))<br><br>and it seemed to have worked just fine. However, when I
run pn_=
back I get the output attached at the end of this email, and no background =
spectrum is created. Do you know why this happens? If it matters, I am usin=
g a new pn-spectra file (attached), which was emailed to me by Nora Loiseau=
 a couple of weeks ago.<br>

<br>
The files created by pn-spectra are:<br>
<br>pnS003-im${i}-400-7200-oot.fits ........ with
i=3D1,2,3,4<br>pnS003-im$=
{i}-400-7200.fits ........ with i=3D1,2,3,4<br>pnS003-${i}fc-oot.pi
.......=
. with i=3D1,2,3,4<br>pnS003-${i}fc.pi ........ with
i=3D1,2,3,4<br>pnS003-=
${i}ff-oot.pi ........ with i=3D1,2,3,4<br>
pnS003-${i}ff.pi ........ with i=3D1,2,3,4<br>pnS003-${i}oc-oot.pi
........=
 with i=3D1,2,3,4<br>pnS003-${i}oc.pi ........ with
i=3D1,2,3,4<br>pnS003-$=
{i}obj-oot.pi ........ with i=3D1,2,3,4<br>pnS003-${i}obj.pi ........ with
=
i=3D1,2,3,4<br>
pnS003-exp-im-400-7200.fits<br>pnS003-mask-im-400-7200.fits<br>pnS003-obj-i=
m-400-7200-oot.fits<br>pnS003-obj-im-400-7200.fits<br>pnS003.arf<br>pnS003.=
rmf<br>pnS003-obj-oot.pi<br>pnS003-obj.pi<br>pnS003-obj-im-det-400-7200-oot=
.fits<br>
pnS003-mask-im-det-400-7200.fits<br>pnS003-exp-im-det-400-7200.fits<br>pnS0=
03-obj-im-det-400-7200.fits<br>pnS003-obj-im-sp-det.fits<br>pnS003-obj-im-o=
ot.fits<br>pnS003-exp-im.fits<br>pnS003-mask-im.fits<br>pnS003-obj-im.fits<=
br>
pnS003-corn-oot.fits<br>pnS003-corn.fits<br><br>I&#39;m
not sure why pn_bac=
k says

Message of length 60939 truncated


Reply 3

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: g.ogrean@jacobs-university.de
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
Date: Tue May 24 14:18:47 2011
Dear Georgiana,

I cant see anything wrong with this. I need more information.

Can you tell me which obsid you are looking at ?

Also, could you ran the task pn_back using the -V 5 option
and send me the log file then ? Before you run the task, can you
set the variable (c-shell):
   setenv SAS_VERBOSITY 5

Thanks,

Ignacio de la Call
XMM-Newton SOC



Followup 2

Compose reply
Download message
Date: Tue, 24 May 2011 16:47:22 +0200
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
From: Georgiana Ogrean <g.ogrean@jacobs-university.de>
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
--00151744122068bf7604a406aa1f
Content-Type: text/plain; charset=ISO-8859-1

Dear Ignacio,

I'm afraid changing the SAS_VERBOSITY variable and using the -V 5 option
with pn_back doesn't reveal more. Nevertheless, I attached the output at the
end of this email.

The obsid is 0654030101.

Thanks,
Georgiana

pn_back:- Executing (routine): pn_back prefix=S003
caldb=/people/data/astrosoft/xmmsas_11.0.0/ccf/esas_caldb diag=0 elow=400
ehigh=7200 quad1=1 quad2=1 quad3=1 quad4=1  -V 5
pn_back:- pn_back (esas-0.9.15)  [xmmsas_20110223_1801-11.0.0] started:
2011-05-24T14:37:23.000
 xmmdir:
/people/data/astrosoft/xmmsas_11.0.0/ccf/esas_caldb

 Quiescent particle background data file:
 /people/data/astrosoft/xmmsas_11.0.0/ccf/esas_caldb/pn-qpb.fits.gz

 diag:  0
 prefix: S003
 el, eh:  400 7200
 Quadrant selection 1 1 1 1

 Create the OOT subtracted spectrum

 Observed spectrum:
pnS003-obj.pi


 PN Mode: PrimeFullWindow
 OOT Scale:   0.0630

 Spectrum RMF:
pnS003.rmf


 OOT spectrum:
pnS003-obj-oot.pi


 Exposure:   39715.7 s

 Process the individual quadrant observation data and create OOT
 subtracted spectra and exposures which are area and exposure normalized.

 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 READ_PHA POSITION 11
 Missing EXPOSURE keyword
 PN_BACK POSITION 04
 missing file:
pnS003-4obj.pi
in pn-back

--00151744122068bf7604a406aa1f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: base64

RGVhciBJZ25hY2lvLDxicj48YnI+SSYjMzk7bSBhZnJhaWQgY2hhbmdpbmcgdGhlIFNBU19WRVJC
T1NJVFkgdmFyaWFibGUgYW5kIHVzaW5nIHRoZSAtViA1IG9wdGlvbiB3aXRoIHBuX2JhY2sgZG9l
c24mIzM5O3QgcmV2ZWFsIG1vcmUuIE5ldmVydGhlbGVzcywgSSBhdHRhY2hlZCB0aGUgb3V0cHV0
IGF0IHRoZSBlbmQgb2YgdGhpcyBlbWFpbC48YnI+PGJyPlRoZSBvYnNpZCBpcyAwNjU0MDMwMTAx
Ljxicj4KCjxicj5UaGFua3MsPGJyPkdlb3JnaWFuYTxicj48YnI+cG5fYmFjazotIEV4ZWN1dGlu
ZyAocm91dGluZSk6IHBuX2JhY2sgcHJlZml4PVMwMDMgY2FsZGI9L3Blb3BsZS9kYXRhL2FzdHJv
c29mdC94bW1zYXNfMTEuMC4wL2NjZi9lc2FzX2NhbGRiIGRpYWc9MCBlbG93PTQwMCBlaGlnaD03
MjAwIHF1YWQxPTEgcXVhZDI9MSBxdWFkMz0xIHF1YWQ0PTGgIC1WIDU8YnI+cG5fYmFjazotIHBu
X2JhY2sgKGVzYXMtMC45LjE1KaAgW3htbXNhc18yMDExMDIyM18xODAxLTExLjAuMF0gc3RhcnRl
ZDqgIDIwMTEtMDUtMjRUMTQ6Mzc6MjMuMDAwPGJyPgoKoHhtbWRpcjogL3Blb3BsZS9kYXRhL2Fz
dHJvc29mdC94bW1zYXNfMTEuMC4wL2NjZi9lc2FzX2NhbGRioKCgoKCgoKCgoKCgoKCgoKCgoKCg
oKCgoKCgoCA8YnI+oFF1aWVzY2VudCBwYXJ0aWNsZSBiYWNrZ3JvdW5kIGRhdGEgZmlsZTo8YnI+
oC9wZW9wbGUvZGF0YS9hc3Ryb3NvZnQveG1tc2FzXzExLjAuMC9jY2YvZXNhc19jYWxkYi9wbi1x
cGIuZml0cy5neqCgoKCgoKCgoKCgoKAgPGJyPgoKoGRpYWc6oCAwPGJyPqBwcmVmaXg6IFMwMDM8
YnI+oGVsLCBlaDqgIDQwMCA3MjAwPGJyPqBRdWFkcmFudCBzZWxlY3Rpb24gMSAxIDEgMTxicj6g
oCA8YnI+oENyZWF0ZSB0aGUgT09UIHN1YnRyYWN0ZWQgc3BlY3RydW08YnI+oCA8YnI+oE9ic2Vy
dmVkIHNwZWN0cnVtOiBwblMwMDMtb2JqLnBpoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCg
oKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgIDxicj4KCqAgPGJyPqBQTiBNb2Rl
OiBQcmltZUZ1bGxXaW5kb3egoKCgoKCgoKAgPGJyPqBPT1QgU2NhbGU6oKAgMC4wNjMwPGJyPqAg
PGJyPqBTcGVjdHJ1bSBSTUY6IHBuUzAwMy5ybWagoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCg
oKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKAgPGJyPqAgPGJyPqBPT1Qg
c3BlY3RydW06IHBuUzAwMy1vYmotb290LnBpoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCg
oKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKAgPGJyPgoKoCA8YnI+oEV4cG9zdXJlOqCg
IDM5NzE1Ljcgczxicj6gIDxicj6gUHJvY2VzcyB0aGUgaW5kaXZpZHVhbCBxdWFkcmFudCBvYnNl
cnZhdGlvbiBkYXRhIGFuZCBjcmVhdGUgT09UIDxicj6gc3VidHJhY3RlZCBzcGVjdHJhIGFuZCBl
eHBvc3VyZXMgd2hpY2ggYXJlIGFyZWEgYW5kIGV4cG9zdXJlIG5vcm1hbGl6ZWQuPGJyPqAgPGJy
PqBSRUFEX1BIQSBQT1NJVElPTiAxMTxicj6gTWlzc2luZyBFWFBPU1VSRSBrZXl3b3JkPGJyPgoK
oFJFQURfUEhBIFBPU0lUSU9OIDExPGJyPqBNaXNzaW5nIEVYUE9TVVJFIGtleXdvcmQ8YnI+oFBO
X0JBQ0sgUE9TSVRJT04gMDQ8YnI+oG1pc3NpbmcgZmlsZTogcG5TMDAzLTRvYmoucGmgoKCgoKCg
oKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCg
oKAgaW4gcG4tYmFjazxicj48YnI+Cg==
--00151744122068bf7604a406aa1f--



Reply 4

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: g.ogrean@jacobs-university.de
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
Date: Tue May 24 15:07:15 2011
Dear Georgiana,

I will try and process the observatioon myself and
let you know.

Thanks,

Ignacio de la Calle
XMM-Newton SOC


Reply 5

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: g.ogrean@jacobs-university.de
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
Date: Thu May 26 08:54:52 2011
Dear Georgiana,

I have analysed the obsid and have the same problem. I contacted
the ESAS developer and he is looking into it. This problem does not
arise when analising other obsids, so there must be something particular
to this observation that is causing the problem. Try running pn_back 
with diag=1 or 2 to see if there is any more information and please
send it to me.

Thanks,

Ignacio de la Calle
XMM-Newton SOC


Followup 3

Compose reply
Download message
Date: Thu, 26 May 2011 11:11:10 +0200
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
From: Georgiana Ogrean <g.ogrean@jacobs-university.de>
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
--00151747598cbde03304a42a3320
Content-Type: text/plain; charset=ISO-8859-1

Dear Ignacio,

I have pn-spectra running now, again, for an elliptical region, but I'll try
pn_back with a different diag once it's done.

If it helps to know, I tried pn-spectra with a circular and box region, and
then had no problems with pn_back. So it seems the problem is only for an
elliptical region...

Thanks,
Georgiana


On Thu, May 26, 2011 at 10:54 AM, Ignacio de la Calle <
xmmhelp@sciops.esa.int> wrote:

> Dear Georgiana,
>
> I have analysed the obsid and have the same problem. I contacted
> the ESAS developer and he is looking into it. This problem does not
> arise when analising other obsids, so there must be something particular
> to this observation that is causing the problem. Try running pn_back
> with diag=1 or 2 to see if there is any more information and please
> send it to me.
>
> Thanks,
>
> Ignacio de la Calle
> XMM-Newton SOC
>
>
> ================================================================================================
> This message and any attachments are intended for the use of the addressee
> or addressees only. The unauthorised disclosure,
>
> use, dissemination or copying (either in whole or in part) of its content
> is not permitted. If you received this message in
>
> error, please notify the sender and delete it from your system. Emails can
> be altered and their integrity cannot be guaranteed by
>
> the sender.
>
> Please consider the environment before printing this email.
>
> =================================================================================================
>
>

--00151747598cbde03304a42a3320
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Ignacio,<br><br>I have pn-spectra running now, again, for an
elliptica=
l region, but I&#39;ll try pn_back with a different diag once it&#39;s
done=
.<br><br>If it helps to know, I tried pn-spectra with a circular and
box re=
gion, and then had no problems with pn_back. So it seems the problem is onl=
y for an elliptical region...<br>
<br>Thanks,<br>Georgiana<br><br><br><div
class=3D"gmail_quote">On Thu, May =
26, 2011 at 10:54 AM, Ignacio de la Calle <span dir=3D"ltr">&lt;<a
href=3D"=
mailto:xmmhelp@sciops.esa.int">xmmhelp@sciops.esa.int</a>&gt;</span>
wrote:=
<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Dear
Georgiana,<b=
r>
<br>
I have analysed the obsid and have the same problem. I contacted<br>
the ESAS developer and he is looking into it. This problem does not<br>
arise when analising other obsids, so there must be something particular<br=
>
to this observation that is causing the problem. Try running pn_back<br>
with diag=3D1 or 2 to see if there is any more information and please<br>
send it to me.<br>
<div><div></div><div class=3D"h5"><br>
Thanks,<br>
<br>
Ignacio de la Calle<br>
XMM-Newton SOC<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
This message and any attachments are intended for the use of the addressee =
or addressees only. The unauthorised disclosure,<br>
<br>
use, dissemination or copying (either in whole or in part) of its content i=
s not permitted. If you received this message in<br>
<br>
error, please notify the sender and delete it from your system. Emails can =
be altered and their integrity cannot be guaranteed by<br>
<br>
the sender.<br>
<br>
Please consider the environment before printing this email.<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
</div></div></blockquote></div><br>

--00151747598cbde03304a42a3320--



Followup 4

Compose reply
Download message
Date: Mon, 20 Jun 2011 12:09:01 +0200
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
From: Georgiana Ogrean <g.ogrean@jacobs-university.de>
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
--002354187760a38b2904a621ec4f
Content-Type: text/plain; charset=ISO-8859-1

Dear Ignacio,

Do you have any news from the ESAS developer concerning the elliptical
region selection?

Thanks,
Georgiana

--002354187760a38b2904a621ec4f
Content-Type: text/html; charset=ISO-8859-1

Dear Ignacio, <br><br>Do you have any news from the ESAS developer
concerning the elliptical region
selection?<br><br>Thanks,<br>Georgiana<br>

--002354187760a38b2904a621ec4f--



Reply 6

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: g.ogrean@jacobs-university.de
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
Date: Mon Jun 20 14:17:03 2011
Dear Georgina,

You can run the command that produces the file pnS003-clean.fits within 
pn-spectra. Run the command pn-spectra (save the log), and locate the line
I quote bellow. Copy and paste this line in a terminal to see what happens 
when you call eveselect to filter the clean event file to produce a spectrum.
Bellow you can see what I get. You should have a similar output.

evselect table=pnS003-clean.fits:EVENTS withfilteredset=yes 
expression='(PATTERN <= 4)&&(FLAG == 0)&&((DETX,DETY) in
BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY) in
ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY) IN
circle(-2200,-1110,17980))' filtertype=expression keepfilteroutput=no
updateexposure=yes filterexposure=yes withspectrumset=yes
spectrumset=pnS003-4obj.pi energycolumn=PI spectralbinsize=5 withspecranges=yes
specchannelmin=0 specchannelmax=20479
** evselect: warning (NoFilteredEvents), No events have been selected -
filtering of the event list resulted in an empty table
** evselect: warning (NoExpEmpty), Cannot calculate exposure when no events are
selected. Cannot write EXPOSURE keyword for output products.

You can see that in fact the EXPOSURE keyword does not exist in the
spectral file (look for the spectral header in the FITS file). That is
why pn_back complains.

You can open pnS003-clean.fits with the SAS task xmmselect 
(xmmselect table=pnS003-clean.fits), apply the selection expression

(PATTERN <= 4)&&(FLAG == 0)&&((DETX,DETY) in
BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY) in
ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY) IN
circle(-2200,-1110,17980))

and produce an image. You will see that in fact, no events are being selected 
using this selection expression.

Let me know if you can produce this image and if you think this should not
be the case.

Many thanks,

Ignacio de la Calle
XMM-Newton SOC



Followup 5

Compose reply
Download message
Date: Tue, 21 Jun 2011 14:30:06 +0200
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
From: Georgiana Ogrean <g.ogrean@jacobs-university.de>
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
--001517475e621cfc8204a63803c4
Content-Type: multipart/alternative; boundary=001517475e621cfc7b04a63803c2

--001517475e621cfc7b04a63803c2
Content-Type: text/plain; charset=ISO-8859-1

Dear Ignacio,

The output in your email is only for quad4. It's true that my region does
not intersect that quadrant so there are no events to select there, but
events are selected from quadrants 2 and 3. If I don't limit my selection
expression to quadrants 1 and 4, then the image is not empty (I attached the
resulting image in detector coordinates).

There are also some "empty" quadrants for other pn regions I selected, so
I'm not sure that's why pn_back complains in this case, because the other
regions worked fine. Even for this region, if I use a box region instead of
an ellipse (with exactly the same size and position as the ellipse), pn_back
does create background spectra.

Georgiana


On Mon, Jun 20, 2011 at 4:17 PM, Ignacio de la Calle <xmmhelp@sciops.esa.int
> wrote:

> Dear Georgina,
>
> You can run the command that produces the file pnS003-clean.fits within
> pn-spectra. Run the command pn-spectra (save the log), and locate the line
> I quote bellow. Copy and paste this line in a terminal to see what happens
> when you call eveselect to filter the clean event file to produce a
> spectrum.
> Bellow you can see what I get. You should have a similar output.
>
> evselect table=pnS003-clean.fits:EVENTS withfilteredset=yes
> expression='(PATTERN <= 4)&&(FLAG == 0)&&((DETX,DETY) in
> BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
> BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY) in
> ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY) IN
> circle(-2200,-1110,17980))' filtertype=expression keepfilteroutput=no
> updateexposure=yes filterexposure=yes withspectrumset=yes
> spectrumset=pnS003-4obj.pi energycolumn=PI spectralbinsize=5
> withspecranges=yes
> specchannelmin=0 specchannelmax=20479
> ** evselect: warning (NoFilteredEvents), No events have been selected -
> filtering of the event list resulted in an empty table
> ** evselect: warning (NoExpEmpty), Cannot calculate exposure when no events
> are
> selected. Cannot write EXPOSURE keyword for output products.
>
> You can see that in fact the EXPOSURE keyword does not exist in the
> spectral file (look for the spectral header in the FITS file). That is
> why pn_back complains.
>
> You can open pnS003-clean.fits with the SAS task xmmselect
> (xmmselect table=pnS003-clean.fits), apply the selection expression
>
> (PATTERN <= 4)&&(FLAG == 0)&&((DETX,DETY) in
> BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
> BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY) in
> ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY) IN
> circle(-2200,-1110,17980))
>
> and produce an image. You will see that in fact, no events are being
> selected
> using this selection expression.
>
> Let me know if you can produce this image and if you think this should not
> be the case.
>
> Many thanks,
>
> Ignacio de la Calle
> XMM-Newton SOC
>
>
>
>
> ================================================================================================
> This message and any attachments are intended for the use of the addressee
> or addressees only. The unauthorised disclosure,
>
> use, dissemination or copying (either in whole or in part) of its content
> is not permitted. If you received this message in
>
> error, please notify the sender and delete it from your system. Emails can
> be altered and their integrity cannot be guaranteed by
>
> the sender.
>
> Please consider the environment before printing this email.
>
> =================================================================================================
>
>

--001517475e621cfc7b04a63803c2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Ignacio,<br><br>The output in your email is only for quad4.
It&#39;s t=
rue that my region does not intersect that quadrant so there are no events =
to select there, but events are selected from quadrants 2 and 3. If I don&#=
39;t limit my selection expression to quadrants 1 and 4, then the image is =
not empty (I attached the resulting image in detector coordinates).<br>
<br>There are also some &quot;empty&quot; quadrants for other pn
regions I =
selected, so I&#39;m not sure that&#39;s why pn_back complains in this
case=
, because the other regions worked fine. Even for this region, if I use a b=
ox region instead of an ellipse (with exactly the same size and position as=
 the ellipse), pn_back does create background spectra.<br>
<br>Georgiana<br><br><br><div
class=3

Message of length 3577275 truncated


Reply 7

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: g.ogrean@jacobs-university.de
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
Date: Tue Oct 18 10:51:51 2011
Dear Georgiana,

Sorry for the very long reply. I have been away most of this time with
different things. I only wanted to inquiry about your progress and if 
you still need anything from me.

Apologies again,

Ignacio de la Calle
XMM-Newton SOC

> --001517475e621cfc8204a63803c4
> Content-Type: multipart/alternative; boundary=001517475e621cfc7b04a63803c2
> 
> --001517475e621cfc7b04a63803c2
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Dear Ignacio,
> 
> The output in your email is only for quad4. It's true that my region does
> not intersect that quadrant so there are no events to select there, but
> events are selected from quadrants 2 and 3. If I don't limit my selection
> expression to quadrants 1 and 4, then the image is not empty (I attached
the
> resulting image in detector coordinates).
> 
> There are also some "empty" quadrants for other pn regions I selected, so
> I'm not sure that's why pn_back complains in this case, because the other
> regions worked fine. Even for this region, if I use a box region instead
of
> an ellipse (with exactly the same size and position as the ellipse),
pn_back
> does create background spectra.
> 
> Georgiana
> 
> 
> On Mon, Jun 20, 2011 at 4:17 PM, Ignacio de la Calle
<xmmhelp@sciops.esa.int
>> wrote:
> 
>> Dear Georgina,
>>
>> You can run the command that produces the file pnS003-clean.fits
within
>> pn-spectra. Run the command pn-spectra (save the log), and locate the
line
>> I quote bellow. Copy and paste this line in a terminal to see what
happens
>> when you call eveselect to filter the clean event file to produce a
>> spectrum.
>> Bellow you can see what I get. You should have a similar output.
>>
>> evselect table=pnS003-clean.fits:EVENTS withfilteredset=yes
>> expression='(PATTERN <= 4)&&(FLAG ==
0)&&((DETX,DETY) in
>> BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
>> BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY) in
>> ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY) IN
>> circle(-2200,-1110,17980))' filtertype=expression keepfilteroutput=no
>> updateexposure=yes filterexposure=yes withspectrumset=yes
>> spectrumset=pnS003-4obj.pi energycolumn=PI spectralbinsize=5
>> withspecranges=yes
>> specchannelmin=0 specchannelmax=20479
>> ** evselect: warning (NoFilteredEvents), No events have been selected
-
>> filtering of the event list resulted in an empty table
>> ** evselect: warning (NoExpEmpty), Cannot calculate exposure when no
events
>> are
>> selected. Cannot write EXPOSURE keyword for output products.
>>
>> You can see that in fact the EXPOSURE keyword does not exist in the
>> spectral file (look for the spectral header in the FITS file). That is
>> why pn_back complains.
>>
>> You can open pnS003-clean.fits with the SAS task xmmselect
>> (xmmselect table=pnS003-clean.fits), apply the selection expression
>>
>> (PATTERN <= 4)&&(FLAG == 0)&&((DETX,DETY) in
>> BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
>> BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY) in
>> ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY) IN
>> circle(-2200,-1110,17980))
>>
>> and produce an image. You will see that in fact, no events are being
>> selected
>> using this selection expression.
>>
>> Let me know if you can produce this image and if you think this should
not
>> be the case.
>>
>> Many thanks,
>>
>> Ignacio de la Calle
>> XMM-Newton SOC
>>
>>
>>
>>
>> ================================================================================================
>> This message and any attachments are intended for the use of the
addressee
>> or addressees only. The unauthorised disclosure,
>>
>> use, dissemination or copying (either in whole or in part) of its
content
>> is not permitted. If you received this message in
>>
>> error, please notify the sender and delete it from your system. Emails
can
>> be altered and their integrity cannot be guaranteed by
>>
>> the sender.
>>
>> Please consider the environment before printing this email.
>>
>> =================================================================================================
>>
>>
> 
> --001517475e621cfc7b04a63803c2
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> 
> Dear Ignacio,<br><br>The output in your email is only f

Message of length 3856541 truncated


Followup 6

Compose reply
Download message
Date: Wed, 19 Oct 2011 09:00:21 +0200
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
From: Georgiana Ogrean <g.ogrean@jacobs-university.de>
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
--0015174be34eba238504afa164c3
Content-Type: text/plain; charset=ISO-8859-1

Dear Ignacio,

Thanks for getting back to me, I've already figured out a way around that
problem. Instead of using an ellipse, I used a partial annulus (combining
circle and sector selection expressions), and that worked fine for all
detectors.

I also noticed that if one doesn't remove/rename the files created in
previous pn-spectra runs, then pn_back generally fails because pn-spectra
does not overwrite all the old files. I think I've read this suggestion
before on the XMM Helpdesk website, but it would be useful to have a clobber
parameter for mos-spectra and pn-spectra.

Georgiana


On Tue, Oct 18, 2011 at 12:50 PM, Ignacio de la Calle <
xmmhelp@sciops.esa.int> wrote:

> Dear Georgiana,
>
> Sorry for the very long reply. I have been away most of this time with
> different things. I only wanted to inquiry about your progress and if
> you still need anything from me.
>
> Apologies again,
>
> Ignacio de la Calle
> XMM-Newton SOC
>
> > --001517475e621cfc8204a63803c4
> > Content-Type: multipart/alternative;
> boundary=001517475e621cfc7b04a63803c2
> >
> > --001517475e621cfc7b04a63803c2
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Dear Ignacio,
> >
> > The output in your email is only for quad4. It's true that my region
does
> > not intersect that quadrant so there are no events to select there,
but
> > events are selected from quadrants 2 and 3. If I don't limit my
selection
> > expression to quadrants 1 and 4, then the image is not empty (I
attached
> the
> > resulting image in detector coordinates).
> >
> > There are also some "empty" quadrants for other pn regions I selected,
so
> > I'm not sure that's why pn_back complains in this case, because the
other
> > regions worked fine. Even for this region, if I use a box region
instead
> of
> > an ellipse (with exactly the same size and position as the ellipse),
> pn_back
> > does create background spectra.
> >
> > Georgiana
> >
> >
> > On Mon, Jun 20, 2011 at 4:17 PM, Ignacio de la Calle <
> xmmhelp@sciops.esa.int
> >> wrote:
> >
> >> Dear Georgina,
> >>
> >> You can run the command that produces the file pnS003-clean.fits
within
> >> pn-spectra. Run the command pn-spectra (save the log), and locate
the
> line
> >> I quote bellow. Copy and paste this line in a terminal to see what
> happens
> >> when you call eveselect to filter the clean event file to produce
a
> >> spectrum.
> >> Bellow you can see what I get. You should have a similar output.
> >>
> >> evselect table=pnS003-clean.fits:EVENTS withfilteredset=yes
> >> expression='(PATTERN <= 4)&&(FLAG ==
0)&&((DETX,DETY) in
> >> BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
> >> BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY) in
> >> ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY)
IN
> >> circle(-2200,-1110,17980))' filtertype=expression
keepfilteroutput=no
> >> updateexposure=yes filterexposure=yes withspectrumset=yes
> >> spectrumset=pnS003-4obj.pi energycolumn=PI spectralbinsize=5
> >> withspecranges=yes
> >> specchannelmin=0 specchannelmax=20479
> >> ** evselect: warning (NoFilteredEvents), No events have been
selected -
> >> filtering of the event list resulted in an empty table
> >> ** evselect: warning (NoExpEmpty), Cannot calculate exposure when
no
> events
> >> are
> >> selected. Cannot write EXPOSURE keyword for output products.
> >>
> >> You can see that in fact the EXPOSURE keyword does not exist in
the
> >> spectral file (look for the spectral header in the FITS file).
That is
> >> why pn_back complains.
> >>
> >> You can open pnS003-clean.fits with the SAS task xmmselect
> >> (xmmselect table=pnS003-clean.fits), apply the selection
expression
> >>
> >> (PATTERN <= 4)&&(FLAG == 0)&&((DETX,DETY) in
> >> BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
> >> BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY) in
> >> ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY)
IN
> >> circle(-2200,-1110,17980))
> >>
> >> and produce an image. You will see that in fact, no events are
being
> >> selected
> >> using this selection expression.
> >>
> >> Let me know if you can produce this image and if you think this
should
> not
> >> be the case.
> >>
> >> Many thanks,
> >>

Message of length 251404 truncated


Reply 8

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: g.ogrean@jacobs-university.de
Subject: Re: mos-spectra/pn-spectra region selection (PR#47855)
Date: Wed Oct 19 09:37:27 2011
Dear Georgiana,

Thanks for letting me know.

Yes, we are aware of the fact you comment regarding pn-spectra not overwriting
files. I am not sure if this will change in future releases or if this is 
something that the ESAS developers want to keep like this (for reasons unknown
to me).

Many thanks and do not hesitate to contact me again if you need anything.

Ignacio de la Calle
XMM-Newton SOC

> Content-Type: text/plain; charset=ISO-8859-1
> 
> Dear Ignacio,
> 
> Thanks for getting back to me, I've already figured out a way around that
> problem. Instead of using an ellipse, I used a partial annulus (combining
> circle and sector selection expressions), and that worked fine for all
> detectors.
> 
> I also noticed that if one doesn't remove/rename the files created in
> previous pn-spectra runs, then pn_back generally fails because pn-spectra
> does not overwrite all the old files. I think I've read this suggestion
> before on the XMM Helpdesk website, but it would be useful to have a
clobber
> parameter for mos-spectra and pn-spectra.
> 
> Georgiana
> 
> 
> On Tue, Oct 18, 2011 at 12:50 PM, Ignacio de la Calle <
> xmmhelp@sciops.esa.int> wrote:
> 
>> Dear Georgiana,
>>
>> Sorry for the very long reply. I have been away most of this time with
>> different things. I only wanted to inquiry about your progress and if
>> you still need anything from me.
>>
>> Apologies again,
>>
>> Ignacio de la Calle
>> XMM-Newton SOC
>>
>> > --001517475e621cfc8204a63803c4
>> > Content-Type: multipart/alternative;
>> boundary=001517475e621cfc7b04a63803c2
>> >
>> > --001517475e621cfc7b04a63803c2
>> > Content-Type: text/plain; charset=ISO-8859-1
>> >
>> > Dear Ignacio,
>> >
>> > The output in your email is only for quad4. It's true that my
region does
>> > not intersect that quadrant so there are no events to select
there, but
>> > events are selected from quadrants 2 and 3. If I don't limit my
selection
>> > expression to quadrants 1 and 4, then the image is not empty (I
attached
>> the
>> > resulting image in detector coordinates).
>> >
>> > There are also some "empty" quadrants for other pn regions I
selected, so
>> > I'm not sure that's why pn_back complains in this case, because
the other
>> > regions worked fine. Even for this region, if I use a box region
instead
>> of
>> > an ellipse (with exactly the same size and position as the
ellipse),
>> pn_back
>> > does create background spectra.
>> >
>> > Georgiana
>> >
>> >
>> > On Mon, Jun 20, 2011 at 4:17 PM, Ignacio de la Calle <
>> xmmhelp@sciops.esa.int
>> >> wrote:
>> >
>> >> Dear Georgina,
>> >>
>> >> You can run the command that produces the file
pnS003-clean.fits within
>> >> pn-spectra. Run the command pn-spectra (save the log), and
locate the
>> line
>> >> I quote bellow. Copy and paste this line in a terminal to see
what
>> happens
>> >> when you call eveselect to filter the clean event file to
produce a
>> >> spectrum.
>> >> Bellow you can see what I get. You should have a similar
output.
>> >>
>> >> evselect table=pnS003-clean.fits:EVENTS withfilteredset=yes
>> >> expression='(PATTERN <= 4)&&(FLAG ==
0)&&((DETX,DETY) in
>> >> BOX(-2196,-1110,16060,15510,0))&&((DETX,DETY) in
>> >> BOX(-10241.5,-9311.0,8041.5,8216.0,0))&&((DETX,DETY)
in
>> >> ellipse(1959.6,-1803.8,4623.65,1372.90,10.0))&&((DETX,DETY)
IN
>> >> circle(-2200,-1110,17980))' filtertype=expression
keepfilteroutput=no
>> >> updateexposure=yes filterexposure=yes withspectrumset=yes
>> >> spectrumset=pnS003-4obj.pi energycolumn=PI spectralbinsize=5
>> >> withspecranges=yes
>> >> specchannelmin=0 specchannelmax=20479
>> >> ** evselect: warning (NoFilteredEvents), No events have been
selected -
>> >> filtering of the event list resulted in an empty table
>> >> ** evselect: warning (NoExpEmpty), Cannot calculate exposure
when no
>> events
>> >> are
>> >> selected. Cannot write EXPOSURE keyword for output products.
>> >>
>> >> You can see that in fact the EXPOSURE keyword does not exist
in the
>> >> spectral file (look for the spectral header in the FITS file).
That is
>> >> why pn_back complains.
>> >>

Message of length 273890 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