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 SASv17.0/84788
Full headers

From: aftabnafisa@gmail.com
Subject: query: epicspeccombine
Compose reply
Download message
Move To:
3 replies: 1 2 3
3 followups: 1 2 3

Private message: yes  no

Notes:

Notification:


Date: Tue, 19 Mar 2019 08:53:03 +0100
From: aftabnafisa@gmail.com
To: xmmhelp@sciops.esa.int
Subject: query: epicspeccombine
Full_Name: Nafisa Aftab
Submission from: (NULL) (193.147.152.102)


Dear sir/madam,

I have some queries related to the task epicspeccombine, kindly find below
----------------
1. Can I use this task to add two EPIC pn spectra which were created from source
region files of different sizes (say, one with 20 arc-sec another with 30
arc-sec) ?

2. Before I use this task in the command line, I gave only following
initialization:
source /usr/local/SAS/xmmsas_20141104_1833/setsas.sh
export SAS_CCFPATH=/ccf

I did not export ODF, .cif, *SUM.SAS files for the two observations. 
Was my approach correct? Or do I need to export something appropriate for this
task? 

3. I copied the command for epicspeccombine from your website and used. I was
getting an error: ** epicspeccombine: error (invalidOption), invalid option '='.
Then I removed the space before and after the '=' sign in three places. Then the
routine executed and produced merged spectrum and response files, it did not
show any warning or error. I am just curious to know: Did I get correct files ?

4. Can I use mathpha, addrmf, addarf to merge multiple EPIC spectra ?
--------------- 
Kindly clarify.

Thank you
Best regards
Nafisa 

Raman Research Institute
Bengaluru
India



Reply 1

Resend
From: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
To: aftabnafisa@gmail.com
Subject: Re: query: epicspeccombine (PR#84788)
Date: Tue Mar 19 10:55:59 2019
Dear Bafia Aftab,


> 1. Can I use this task to add two EPIC pn spectra which were created from
source
> region files of different sizes (say, one with 20 arc-sec another with 30
> arc-sec) ?
> 

No, 'epicspeccombine'  assumes that the spectral extraction regions are 
identical for all the EPIC input files. 


> 2. Before I use this task in the command line, I gave only following
> initialization:
> source /usr/local/SAS/xmmsas_20141104_1833/setsas.sh
> export SAS_CCFPATH=/ccf
> 
> I did not export ODF, .cif, *SUM.SAS files for the two observations. 
> Was my approach correct? Or do I need to export something appropriate for
this
> task? 
> 

This is correct. You need to set these environment variables when you process
the 
individual datasets to generate the spectra and the response matrices.
But they are not needed to run epicspeccombine.


> 3. I copied the command for epicspeccombine from your website and used. I
was
> getting an error: ** epicspeccombine: error (invalidOption), invalid option
'='.
> Then I removed the space before and after the '=' sign in three places.
Then
the
> routine executed and produced merged spectrum and response files, it did
not
> show any warning or error. I am just curious to know: Did I get correct
files
?
> 

Yes, what you did is correct. This is a mistake in the thread. Thanks for
letting us know.


> 4. Can I use mathpha, addrmf, addarf to merge multiple EPIC spectra ?

These are 'ftools' tasks. As they are not part of SAS, we cannot guarantee that

their output is correct or compatible with other SAS tasks (e.g. there may be
keywords
missing or incorrect in the headers of the output files).


I see in your message that you are using an old version of SAS (SASv14): 

/usr/local/SAS/xmmsas_20141104_1833/setsas.sh

I would suggest that you installthe current version SASv17
(xmmsas_20180620_1732).
 	


Regards,

Rosario Gonzalez-Riestra
XMM-SOC User SUpport Group




Followup 1

Compose reply
Download message
From: Nafisa Aftab <aftabnafisa@gmail.com>
Date: Tue, 19 Mar 2019 21:55:21 +0530
Subject: Re: query: epicspeccombine (PR#84788)
To: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
--0000000000004c5fa7058474f4ca
Content-Type: text/plain; charset="UTF-8"

Dear Dr. Gonzalez-Riestra,

Many thanks for your kind reply, this clarified all my queries.
Now I am facing the issue related to source region of different sizes. Is
there any tool which can scale the extraction area ? Because I need to
combine several EPIC-pn spectrum which were extracted from source regions
of different sizes. For example I have a set of 7 spectra which were
created from circular source regions of radius between 20-30 arc-sec.
(Since source intensity had variations, so I had chosen radius of the
source regions accordingly).

Kindly suggest.

Thank you
Best regards
Nafisa

On Tue, Mar 19, 2019 at 3:26 PM Rosario Gonzalez Riestra <
xmmhelp@sciops.esa.int> wrote:

>
> Dear Bafia Aftab,
>
>
> > 1. Can I use this task to add two EPIC pn spectra which were created
from
> source
> > region files of different sizes (say, one with 20 arc-sec another with
30
> > arc-sec) ?
> >
>
> No, 'epicspeccombine'  assumes that the spectral extraction regions are
> identical for all the EPIC input files.
>
>
> > 2. Before I use this task in the command line, I gave only following
> > initialization:
> > source /usr/local/SAS/xmmsas_20141104_1833/setsas.sh
> > export SAS_CCFPATH=/ccf
> >
> > I did not export ODF, .cif, *SUM.SAS files for the two observations.
> > Was my approach correct? Or do I need to export something appropriate
for
> this
> > task?
> >
>
> This is correct. You need to set these environment variables when you
> process
> the
> individual datasets to generate the spectra and the response matrices.
> But they are not needed to run epicspeccombine.
>
>
> > 3. I copied the command for epicspeccombine from your website and
used.
> I was
> > getting an error: ** epicspeccombine: error (invalidOption), invalid
> option
> '='.
> > Then I removed the space before and after the '=' sign in three
places.
> Then
> the
> > routine executed and produced merged spectrum and response files, it
did
> not
> > show any warning or error. I am just curious to know: Did I get
correct
> files
> ?
> >
>
> Yes, what you did is correct. This is a mistake in the thread. Thanks for
> letting us know.
>
>
> > 4. Can I use mathpha, addrmf, addarf to merge multiple EPIC spectra ?
>
> These are 'ftools' tasks. As they are not part of SAS, we cannot guarantee
> that
>
> their output is correct or compatible with other SAS tasks (e.g. there may
> be
> keywords
> missing or incorrect in the headers of the output files).
>
>
> I see in your message that you are using an old version of SAS (SASv14):
>
> /usr/local/SAS/xmmsas_20141104_1833/setsas.sh
>
> I would suggest that you installthe current version SASv17
> (xmmsas_20180620_1732).
>
>
>
> Regards,
>
> 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).
>
>
>

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

<div dir=3D"ltr"><div>Dear Dr.
Gonzalez-Riestra,</div><div><br></div><div>M=
any thanks for your kind reply, this clarified all my
queries.</div><div>No=
w I am facing the issue related to source region of different sizes. Is the=
re any tool which can scale the extraction area ? Because I need to combine=
 several EPIC-pn spectrum which were extracted from source regions of diffe=
rent sizes. For example I have a set of 7 spectra which were created from c=
ircular source regions of radius between 20-30 arc-sec. (Since source inten=
sity had variations, so I had chosen radius of the source regions according=
ly).</div><div><br></div><div>Kindly
suggest.</div><div><br></div><div>Than=
k you</div><div>Best
regards</div><div>Nafisa<br></div></div><br><div
class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Mar 19,
2019=
 at 3:26 PM Rosario Gonzalez Riestra &lt;<a
href=3D"mailto:xmmhelp@sciops.e=
sa.int">xmmhelp@sciops.esa.int</a>&gt;
wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.

Message of length 8608 truncated


Reply 2

Resend
From: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
To: aftabnafisa@gmail.com
Subject: Re: query: epicspeccombine (PR#84788)
Date: Wed Mar 20 10:12:25 2019
Dear Nafisa,


> Now I am facing the issue related to source region of different sizes. Is
> there any tool which can scale the extraction area ? Because I need to
> combine several EPIC-pn spectrum which were extracted from source regions
> of different sizes. For example I have a set of 7 spectra which were
> created from circular source regions of radius between 20-30 arc-sec.
> (Since source intensity had variations, so I had chosen radius of the
> source regions accordingly).

I am afraid that there is no solution or workaround for this, as it is clearly
stated in the description of the task, see

http://xmm-tools.cosmos.esa.int/external/sas/current/doc/epicspeccombine/node3.html


But also note that the size of the extraction region does not need to change
with  the source intensity, so there would be no problem in extracting all the
spectra with 
regions of the same size.


Regards,

Rosario

 


 


Followup 2

Compose reply
Download message
From: Nafisa Aftab <aftabnafisa@gmail.com>
Date: Wed, 20 Mar 2019 16:40:54 +0530
Subject: Re: query: epicspeccombine (PR#84788)
To: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
--00000000000079cbd3058484aeb4
Content-Type: text/plain; charset="UTF-8"

Dear Dr. Gonzalez Riestra,

Many thanks for clarifying.

> But also note that the size of the extraction region does not need to
change
> with  the source intensity, so there would be no problem in extracting
all the
> spectra with regions of the same size.

Yeah. Thank you.
When the source was faint, I extracted spectra from 20 arc-sec region. If I
make it 30 arc-sec, then more background will
be added, I am worried of increase in signal to noise ratio in that
spectrum. In this situation, If you have any suggestion
kindly let me know.

Thank you
Best regards
Nafisa



On Wed, Mar 20, 2019 at 2:42 PM Rosario Gonzalez Riestra <
xmmhelp@sciops.esa.int> wrote:

>
> Dear Nafisa,
>
>
> > > Now I am facing the issue related to source region of different
sizes.
> Is
> > there any tool which can scale the extraction area ? Because I need to
> > combine several EPIC-pn spectrum which were extracted from source
regions
> > of different sizes. For example I have a set of 7 spectra which were
> > created from circular source regions of radius between 20-30 arc-sec.
> > (Since source intensity had variations, so I had chosen radius of the
> > source regions accordingly).
>
> I am afraid that there is no solution or workaround for this, as it is
> clearly
> stated in the description of the task, see
>
>
> http://xmm-tools.cosmos.esa.int/external/sas/current/doc/epicspeccombine/node3.html
>
>
> But also note that the size of the extraction region does not need to
> change
> with  the source intensity, so there would be no problem in extracting all
> the
> spectra with
> regions of the same size.
>
>
> 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).
>
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div><span
style=3D"color:rgb(153,0,255)"=
>Dear Dr.<span class=3D"gmail-qu" tabindex=3D"-1"><span
name=3D"Rosario Gon=
zalez Riestra" class=3D"gmail-gD"> Gonzalez
Riestra,</span></span></span></=
div><div><span style=3D"color:rgb(153,0,255)"><span
class=3D"gmail-qu" tabi=
ndex=3D"-1"><span name=3D"Rosario Gonzalez Riestra"
class=3D"gmail-gD"><br>=
</span></span></span></div><div><span
class=3D"gmail-qu" tabindex=3D"-1"><s=
pan name=3D"Rosario Gonzalez Riestra" class=3D"gmail-gD"><span
style=3D"col=
or:rgb(153,0,255)">Many thanks for clarifying.
</span><br></span></span></d=
iv><div><span class=3D"gmail-qu" tabindex=3D"-1"><span
name=3D"Rosario Gonz=
alez Riestra" class=3D"gmail-gD"><br></span></span></div><div><span
class=
=3D"gmail-qu" tabindex=3D"-1"><span name=3D"Rosario Gonzalez Riestra"
class=
=3D"gmail-gD">&gt; But also note that the size of the extraction region
doe=
s not need to change<br>
&gt; with=C2=A0 the source intensity, so there would be no problem in extra=
cting all the<br>
&gt; spectra with=20
regions of the same size.</span></span></div><div><span
class=3D"gmail-qu" =
tabindex=3D"-1"><span name=3D"Rosario Gonzalez Riestra"
class=3D"gmail-gD">=
<br></span></span></div><div><span
class=3D"gmail-qu" tabindex=3D"-1"><span=
 name=3D"Rosario Gonzalez Riestra" class=3D"gmail-gD"><span
style=3D"color:=
rgb(153,0,255)">Yeah. Thank
you.<br></span></span></span></div><div><span
s=
tyle=3D"color:rgb(153,0,255)"><span class=3D"gmail-qu"
tabindex=3D"-1"><spa=
n name=3D"Rosario Gonzalez Riestra" class=3D"gmail-gD">When the source was =
faint, I extracted spectra from 20 arc-sec region. If I make it 30 arc-sec,=
 then more background
will</span></span></span></div><div><span
style=3D"co=
lor:rgb(153,0,255)"><span class=3D"gmail-qu" tabindex=3D"-1"><span
name=3D"=
Rosario Gonzalez Riestra" class=3D"gmail-gD">be added, I am worried of incr=
ease in signal to noise ratio in that spectrum. In this situation, If you h=
ave any suggestion</span></span></span></div><

Message of length 9106 truncated


Reply 3

Resend
From: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
To: aftabnafisa@gmail.com
Subject: Re: query: epicspeccombine (PR#84788)
Date: Wed Mar 20 13:36:08 2019
Dear Nafisa,

May then suggest that you do the other way round, i.e. extract all spectra with
a circle of 20 arcsec? This will work both for the faint and for the bright
sources.


Rosario



Followup 3

Compose reply
Download message
From: Nafisa Aftab <aftabnafisa@gmail.com>
Date: Wed, 20 Mar 2019 22:19:03 +0530
Subject: Re: query: epicspeccombine (PR#84788)
To: Rosario Gonzalez Riestra <xmmhelp@sciops.esa.int>
--000000000000e0daca0584896618
Content-Type: text/plain; charset="UTF-8"

Dear Dr.  Riestra,

Many thanks for the kind suggestion. This is indeed very helpful.

Thank you
Best regards
Nafisa

On Wed, 20 Mar 2019, 18:06 Rosario Gonzalez Riestra,
<xmmhelp@sciops.esa.int>
wrote:

>
> Dear Nafisa,
>
> May then suggest that you do the other way round, i.e. extract all spectra
> with
> a circle of 20 arcsec? This will work both for the faint and for the bright
> sources.
>
>
> 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).
>
>
>

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

<div dir=3D"auto">Dear Dr.=C2=A0 Riestra,=C2=A0<div
dir=3D"auto"><br></div>=
<div dir=3D"auto">Many thanks for the kind suggestion. This is indeed very
=
helpful.=C2=A0</div><div dir=3D"auto"><br></div><div
dir=3D"auto">Thank you=
=C2=A0</div><div dir=3D"auto">Best regards=C2=A0</div><div
dir=3D"auto">Naf=
isa</div></div><br><div class=3D"gmail_quote"><div
dir=3D"ltr" class=3D"gma=
il_attr">On Wed, 20 Mar 2019, 18:06 Rosario Gonzalez Riestra, &lt;<a
href=
=3D"mailto:xmmhelp@sciops.esa.int" target=3D"_blank" rel=3D"noreferrer">xmm=
help@sciops.esa.int</a>&gt; wrote:<br></div><blockquote
class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<br>
Dear Nafisa,<br>
<br>
May then suggest that you do the other way round, i.e. extract all spectra =
with<br>
a circle of 20 arcsec? This will work both for the faint and for the bright=
<br>
sources.<br>
<br>
<br>
Rosario<br>
<br>
<br>
This message is intended only for the recipient(s) named above. It may cont=
ain proprietary information and/or<br>
protected content. Any unauthorised disclosure, use, retention or dissemina=
tion is prohibited. If you have received<br>
this e-mail in error, please notify the sender immediately. ESA applies app=
ropriate organisational measures to protect<br>
personal data, in case of data privacy queries, please contact the ESA Data=
 Protection Officer (<a href=3D"mailto:dpo@esa.int" rel=3D"noreferrer noref=
errer" target=3D"_blank">dpo@esa.int</a>).<br>
<br>
<br>
</blockquote></div>

--000000000000e0daca0584896618--


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