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 EPICpn/38320
Full headers

From: miranda@physics.umanitoba.ca
Subject: Re: trouble with a spectrum extracted from multiple point source
Compose reply
Download message
Move To:
2 replies: 1 2
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Tue, 09 Sep 2008 08:41:30 -0500
From: miranda@physics.umanitoba.ca
To: Maria Diaz Trigo <xmmhelp@sciops.esa.int>
Subject: Re: trouble with a spectrum extracted from multiple point source
This message is in MIME format.

--=_3aaxxalqpw5m
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dear Maria

My region file is attached.

Thanks.

Miranda


Quoting Maria Diaz Trigo <xmmhelp@sciops.esa.int>:

> Dear Miranda,
>
> could you please send us the region file that you have used to extract you=
r
> spectrum?
> With this we can tell you already if the region is correct or not.
>
> Best regards,
>
> Maria
>
> Maria Diaz Trigo
> XMM-Newton SOC
>
>> Full_Name: MIranda Jackson
>> Submission from: (NULL) (130.179.72.213)
>>
>>
>> I have extracted a spectrum from a large number of small circles within
a
> larger
>> circle in PN and MOS data, in order to determine the flux contribution
fr=
om
> all
>> of the resolved point sources within the region. The selection
expression
> makes
>> reference to a FITS region file including all of the small circles, =20
>> and I hope
> I
>> have made it so it is a union among all of those circles rather than an
>> intersection, but I'm not sure about that, though it didn't say that
ther=
e
> were
>> zero events in the file when it was produced. When I try to read =20
>> the spectrum
> in
>> with Xspec, after making the other files and setting the =20
>> appropriate keywords
>> (BACKFILE, etc), I get the following errors:
>>
>> ***Warning: Data file obs2pnptsrcspec.grp has invalid BACKSCAL value
=3D =
0.0.
>>     XSPEC will instead use 1.0.
>> Warning: RMF CHANTYPE keyword is not consistent with spectrum
>>
>> ***XSPEC Error: Background file pnbackobs2.pi DETCHANS do not match
data
> file.
>>
>> Please let me know what I can check in the spectrum file to make sure
it =
was
>> extracted properly, and what I have to do with backscale, rmfgen, and
arf=
gen
>> (special command line parameters, etc.) to be able to read this =20
>> spectrum into
>> Xspec.
>>
>> Thanks.
>>
>>
>>
>
> =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
> This message and any attachments are intended for the use of the =20
> addressee or addressees only. The
> unauthorised disclosure, use, dissemination or copying (either in =20
> whole or in part) of its content
> is prohibited. If you received this message in error, please delete =20
> it from your system and notify
> the sender. E-mails can be altered and their integrity cannot be =20
> guaranteed. ESA shall not be liable
> for any e-mail if modified.
> =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
>
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

--=_3aaxxalqpw5m
Content-Type: text/plain;
	charset=UTF-8;
	name="sourcelistincircle_obs1.fits"
Content-Disposition: attachment;
	filename="sourcelistincircle_obs1.fits"
Content-Transfer-Encoding: quoted-printable

SIMPLE  =3D                    T / file does conform to FITS standard       =
      BITPIX  =3D                    8 / number of bits per data pixel      =
            NAXIS   =3D                    0 / number of data axes          =
                  EXTEND  =3D                    T / FITS dataset may contai=
n extensions            XPROC0  =3D 'ds9tocxc outset=3Dsourcelistincircle_ob=
s1.fits xcolumn=3DX ycolumn=3DY # &'CONTINUE  '(imgdisplay-1.47)
[xmmsas_200=
70708_1801-7.1.0]'                      XDAL0   =3D 'sourcelistincircle_obs1=
.fits 2008-07-11T21:20:47.000 Create ds9tocx&'CONTINUE  'c
(imgdisplay-1.47)=
 [xmmsas_20070708_1801-7.1.0] High SAS_MEMORY_MO&'CONTINUE  'DEL=3D
SAS_ROWS=
=3D SAS_ZERO_ROWS=3D SAS_COLUMN_WISE=3D '                     CREATOR =3D 'd=
s9tocxc (imgdisplay-1.47) [xmmsas_20070708_1801-7.1.0]' / name of coDATE    =
=3D '2008-07-11T21:20:47.000' / creation date                             LO=
NGSTRN=3D 'OGIP 1.0'                                                        =
    HISTORY Created by ds9tocxc (imgdisplay-1.47) [xmmsas_20070708_1801-7.1.=
0] at 20HISTORY 08-07-11T21:20:47                                           =
            END                                                             =
                                                                            =
 

Message of length 33509 truncated

Reply 1

Resend
From: Maria Diaz Trigo <xmmhelp@sciops.esa.int>
To: miranda@physics.umanitoba.ca
Subject: Re: trouble with a spectrum extracted from multiple point source (PR#38320)
Date: Wed Sep 10 17:03:16 2008
Dear Miranda,

I have forwarded your region to our SAS specialists. I'll come back to you as
soon as I get an answer from them.

Best regards,

Maria

Maria Diaz Trigo
XMM-Newton SOC

> This message is in MIME format.
> 
> --=_3aaxxalqpw5m
> Content-Type: text/plain;
> 	charset=ISO-8859-1;
> 	DelSp="Yes";
> 	format="flowed"
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> Dear Maria
> 
> My region file is attached.
> 
> Thanks.
> 
> Miranda
> 
> 
> Quoting Maria Diaz Trigo <xmmhelp@sciops.esa.int>:
> 
>> Dear Miranda,
>>
>> could you please send us the region file that you have used to extract
you=
> r
>> spectrum?
>> With this we can tell you already if the region is correct or not.
>>
>> Best regards,
>>
>> Maria
>>
>> Maria Diaz Trigo
>> XMM-Newton SOC
>>
>>> Full_Name: MIranda Jackson
>>> Submission from: (NULL) (130.179.72.213)
>>>
>>>
>>> I have extracted a spectrum from a large number of small circles
within a
>> larger
>>> circle in PN and MOS data, in order to determine the flux
contribution fr=
> om
>> all
>>> of the resolved point sources within the region. The selection
expression
>> makes
>>> reference to a FITS region file including all of the small circles,
=20
>>> and I hope
>> I
>>> have made it so it is a union among all of those circles rather
than an
>>> intersection, but I'm not sure about that, though it didn't say
that ther=
> e
>> were
>>> zero events in the file when it was produced. When I try to read
=20
>>> the spectrum
>> in
>>> with Xspec, after making the other files and setting the =20
>>> appropriate keywords
>>> (BACKFILE, etc), I get the following errors:
>>>
>>> ***Warning: Data file obs2pnptsrcspec.grp has invalid BACKSCAL
value =3D =
> 0.0.
>>>     XSPEC will instead use 1.0.
>>> Warning: RMF CHANTYPE keyword is not consistent with spectrum
>>>
>>> ***XSPEC Error: Background file pnbackobs2.pi DETCHANS do not match
data
>> file.
>>>
>>> Please let me know what I can check in the spectrum file to make
sure it =
> was
>>> extracted properly, and what I have to do with backscale, rmfgen,
and arf=
> gen
>>> (special command line parameters, etc.) to be able to read this
=20
>>> spectrum into
>>> Xspec.
>>>
>>> Thanks.
>>>
>>>
>>>
>>
>> =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
>> This message and any attachments are intended for the use of the =20
>> addressee or addressees only. The
>> unauthorised disclosure, use, dissemination or copying (either in =20
>> whole or in part) of its content
>> is prohibited. If you received this message in error, please delete
=20
>> it from your system and notify
>> the sender. E-mails can be altered and their integrity cannot be =20
>> guaranteed. ESA shall not be liable
>> for any e-mail if modified.
>> =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
>>
>>
> 
> 
> 
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> 
> --=_3aaxxalqpw5m
> Content-Type: text/plain;
> 	charset=UTF-8;
> 	name="sourcelistincircle_obs1.fits"
> Content-Disposition: attachment;
> 	filename="sourcelistincircle_obs1.fits"
> Content-Transfer-Encoding: quoted-printable
> 
> SIMPLE  =3D                    T / file does conform to FITS standard      
=
>       BITPIX  =3D                    8 / number of bits per data pixel     
=
>             NAXIS   =3D                    0 / number of data axes         
=
>                   EXTEND  =3D                    T / FITS dataset may
contai=
> n extensions            XPROC0  =3D 'ds9tocxc
outset=3Dsourcelistincircle_ob=
> s1.fits xcolumn=3DX ycolumn=3DY # &'CONTINUE  '(imgdisplay-1.47)
[xmmsas_200=
> 70708_1801-7.1

Message of length 36672 truncated


Reply 2

Resend
From: Maria Diaz Trigo <xmmhelp@sciops.esa.int>
To: miranda@physics.umanitoba.ca
Subject: Re: trouble with a spectrum extracted from multiple point source (PR#38320)
Date: Thu Sep 11 14:51:53 2008
Dear Miranda, 

the region that you have sent us is corrupted. Could you please send it to us
again but gzipping it before you send it? 

Many thanks in advance,

Maria

Maria Diaz Trigo
XMM-Newton SOC

> This message is in MIME format.
> 
> --=_3aaxxalqpw5m
> Content-Type: text/plain;
> 	charset=ISO-8859-1;
> 	DelSp="Yes";
> 	format="flowed"
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> Dear Maria
> 
> My region file is attached.
> 
> Thanks.
> 
> Miranda
> 
> 
> Quoting Maria Diaz Trigo <xmmhelp@sciops.esa.int>:
> 
>> Dear Miranda,
>>
>> could you please send us the region file that you have used to extract
you=
> r
>> spectrum?
>> With this we can tell you already if the region is correct or not.
>>
>> Best regards,
>>
>> Maria
>>
>> Maria Diaz Trigo
>> XMM-Newton SOC
>>
>>> Full_Name: MIranda Jackson
>>> Submission from: (NULL) (130.179.72.213)
>>>
>>>
>>> I have extracted a spectrum from a large number of small circles
within a
>> larger
>>> circle in PN and MOS data, in order to determine the flux
contribution fr=
> om
>> all
>>> of the resolved point sources within the region. The selection
expression
>> makes
>>> reference to a FITS region file including all of the small circles,
=20
>>> and I hope
>> I
>>> have made it so it is a union among all of those circles rather
than an
>>> intersection, but I'm not sure about that, though it didn't say
that ther=
> e
>> were
>>> zero events in the file when it was produced. When I try to read
=20
>>> the spectrum
>> in
>>> with Xspec, after making the other files and setting the =20
>>> appropriate keywords
>>> (BACKFILE, etc), I get the following errors:
>>>
>>> ***Warning: Data file obs2pnptsrcspec.grp has invalid BACKSCAL
value =3D =
> 0.0.
>>>     XSPEC will instead use 1.0.
>>> Warning: RMF CHANTYPE keyword is not consistent with spectrum
>>>
>>> ***XSPEC Error: Background file pnbackobs2.pi DETCHANS do not match
data
>> file.
>>>
>>> Please let me know what I can check in the spectrum file to make
sure it =
> was
>>> extracted properly, and what I have to do with backscale, rmfgen,
and arf=
> gen
>>> (special command line parameters, etc.) to be able to read this
=20
>>> spectrum into
>>> Xspec.
>>>
>>> Thanks.
>>>
>>>
>>>
>>
>> =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
>> This message and any attachments are intended for the use of the =20
>> addressee or addressees only. The
>> unauthorised disclosure, use, dissemination or copying (either in =20
>> whole or in part) of its content
>> is prohibited. If you received this message in error, please delete
=20
>> it from your system and notify
>> the sender. E-mails can be altered and their integrity cannot be =20
>> guaranteed. ESA shall not be liable
>> for any e-mail if modified.
>> =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
>>
>>
> 
> 
> 
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> 
> --=_3aaxxalqpw5m
> Content-Type: text/plain;
> 	charset=UTF-8;
> 	name="sourcelistincircle_obs1.fits"
> Content-Disposition: attachment;
> 	filename="sourcelistincircle_obs1.fits"
> Content-Transfer-Encoding: quoted-printable
> 
> SIMPLE  =3D                    T / file does conform to FITS standard      
=
>       BITPIX  =3D                    8 / number of bits per data pixel     
=
>             NAXIS   =3D                    0 / number of data axes         
=
>                   EXTEND  =3D                    T / FITS dataset may
contai=
> n extensions            XPROC0  =3D 'ds9tocxc
outset=3Dsourcelistincircle_ob=
> s1.fits xcolumn=3DX ycolumn=3DY # &'CONTINUE  '(imgdisplay-1.47)
[xmmsas_200=

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