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

From: j_aquarian_t@yahoo.co.in
Subject: multixmmselect : EPIC pn
Compose reply
Download message
Move To:
2 replies: 1 2
1 followups: 1

Private message: yes  no

Notes:

Notification:


Date: Fri, 22 Feb 2019 17:52:45 +0100
From: j_aquarian_t@yahoo.co.in
To: xmmhelp@sciops.esa.int
Subject: multixmmselect : EPIC pn
Full_Name: Juhi Tiwari
Submission from: (NULL) (193.147.152.102)


Dear XMM help team,

Could you kindly tell me how to change the default value specchannelmax=11999 to
specchannelmax=20479 in multixmmselect task in SAS for pn spectral analysis?
Since it uses GUI, the window that pops up to call the task 
multiespecget and epicspeccombine as described in
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-multiexposures does not
have a way to do this.

Regards,
Juhi


Reply 1

Resend
From: Pedro Rodriguez <xmmhelp@sciops.esa.int>
To: j_aquarian_t@yahoo.co.in
Subject: Re: multixmmselect : EPIC pn (PR#84674)
Date: Tue Feb 26 11:21:20 2019
Helo Juhi,

one of the main purposes/options of multixmmselect is to combine all the output
spectra one single file with one single response file and one single effective
area file. This is the reason for the parameters to define the output channel
range to be "hardcoded" in the task with no possibility to modify them. 

Sincerely,

Pedro Rodriguez

> Full_Name: Juhi Tiwari
> Submission from: (NULL) (193.147.152.102)
> 
> 
> Dear XMM help team,
> 
> Could you kindly tell me how to change the default value
specchannelmax=11999
to
> specchannelmax=20479 in multixmmselect task in SAS for pn spectral
analysis?
> Since it uses GUI, the window that pops up to call the task 
> multiespecget and epicspeccombine as described in
> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-multiexposures does
not
> have a way to do this.
> 
> Regards,
> Juhi
> 
> 


Followup 1

Compose reply
Download message
Date: Tue, 26 Feb 2019 11:08:41 +0000 (UTC)
From: Juhi Tiwari <j_aquarian_t@yahoo.co.in>
To: "xmmhelp@sciops.esa.int" <xmmhelp@sciops.esa.int>
Subject: Re: multixmmselect : EPIC pn (PR#84674)
------=_Part_5272910_1147201656.1551179321474
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Dear Pedro,
Thanks for your response.=C2=A0
The recommended maximum spec channel value for EPIC pn spectral analysis is=
 20479, so does multixmmselect give the correct response file generation fo=
r pn data? The hardcoded value for specchannelmax is 11999 I guess which is=
 recommended for MOS data analysis.=C2=A0Can multixmmselect at all be used =
for pn data (because of the hardcoded value being 11999)?
I am facing another problem however. If I run multixmmselect for two overla=
pping pn observations and run it, I get an 'especget error'. I came across =
the following helpdesk submission from several months agohttp://xmm.esac.es=
a.int/xmmhelp/SASv16.1?id=3D83237;user=3Dguest
Here a similar problem is mentioned which was thought to be fixed in the ne=
w SAS release, i.e. SAS 17. This is the one I use.=C2=A0
The same especget error shows up when I try to input two mos observations a=
nd run multixmmselect.=C2=A0
Can we please fix this?Solving either of these is very essential for me to =
be able to proceed with my thesis.
Kind regards,Juhi

Sent from Yahoo Mail on Android=20
=20
  On Tue, 26 Feb 2019 at 3:52 PM, Pedro Rodriguez<xmmhelp@sciops.esa.int>
w=
rote:   Helo Juhi,

one of the main purposes/options of multixmmselect is to combine all the ou=
tput
spectra one single file with one single response file and one single effect=
ive
area file. This is the reason for the parameters to define the output chann=
el
range to be "hardcoded" in the task with no possibility to modify them.=20

Sincerely,

Pedro Rodriguez

> Full_Name: Juhi Tiwari
> Submission from: (NULL) (193.147.152.102)
>=20
>=20
> Dear XMM help team,
>=20
> Could you kindly tell me how to change the default value specchannelmax=
=3D11999
to
> specchannelmax=3D20479 in multixmmselect task in SAS for pn spectral anal=
ysis?
> Since it uses GUI, the window that pops up to call the task=20
> multiespecget and epicspeccombine as described in
> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-multiexposures does =
not
> have a way to do this.
>=20
> Regards,
> Juhi
>=20
>=20

This message is intended only for the recipient(s) named above. It may cont=
ain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemina=
tion is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies app=
ropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data=
 Protection Officer (dpo@esa.int).


 =20

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

Dear Pedro,<div id=3D"yMail_cursorElementTracker_1551178295548"><br></div><=
div id=3D"yMail_cursorElementTracker_1551178295722">Thanks for your respons=
e.&nbsp;</div><div
id=3D"yMail_cursorElementTracker_1551178306697"><br></di=
v><div id=3D"yMail_cursorElementTracker_1551178306909">The recommended
maxi=
mum spec channel value for EPIC pn spectral analysis is 20479, so does mult=
ixmmselect give the correct response file generation for pn data? The hardc=
oded value for specchannelmax is 11999 I guess which is recommended for MOS=
 data analysis.&nbsp;<span style=3D"font-family: sans-serif;"
id=3D"yMail_c=
ursorElementTracker_1551179292612">Can multixmmselect at all be used for pn=
 data (because of the hardcoded value being
11999)?</span></div><div id=3D"=
yMail_cursorElementTracker_1551178671788"><br></div><div
id=3D"yMail_cursor=
ElementTracker_1551178672686">I am facing another problem however. If I run=
 multixmmselect for two overlapping pn observations and run it, I get an 'e=
specget error'. I came across the following helpdesk submission from severa=
l months ago</div><div
id=3D"yMail_cursorElementTracker_1551179025413">http=
://xmm.esac.esa.int/xmmhelp/SASv16.1?id=3D83237;user=3Dguest<br></div><div
=
id=3D"yMail_cursorElementTracker_1551179025599">Here a similar problem is m=
entioned which was thought to be fixed in the new SAS release, i.e. SAS 17.=
 This is the one I use.&nbsp;</div><div
id=3D"yMail_cursorElementTracker_15=
51179078678"><br></div><div
id=3D"yMail_cursorElementTracker_1551178786057"=
>The same especget error shows up when I try to input two mos observations =
and run multixmmselect.&nbsp;</div><div
id=3D"yMail_cursorElementTracker_15=
51179094013"><br></div><div
id=3D"yMail_cursorElementTracker_1551179299218"=
>Can we please fix this?</div><div
id=3D"yMail_cursorElementTracker_1551178=
817059">Solving either of these is very essential for me to be able to pr

Message of length 9489 truncated


Reply 2

Resend
From: Pedro Rodriguez <xmmhelp@sciops.esa.int>
To: j_aquarian_t@yahoo.co.in
Subject: Re: multixmmselect : EPIC pn (PR#84674)
Date: Wed Feb 27 13:56:39 2019
Hi,

please note that the main purpose for multixmmselect is to combine EPIC spectra
from different exposures and that is the reason to force all the spectra to be
created with the same range of spectral channels.

With regard to "especget error" it should not be due to the same reason as in
the ticket quoted as it has been fixed in SAS17.

For such an important issue for your thesis, let me recall that multixmmselect,
multiespecget, especget are all shortcuts to the basic procedures to extract
epic spectra describe in our threads:

https://www.cosmos.esa.int/web/xmm-newton/sas-thread-pn-spectrum

https://www.cosmos.esa.int/web/xmm-newton/sas-thread-mos-spectrum

Sincerely,

Pedro

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