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

From: piero.ranalli@bo.astro.it
Subject: ESAS in SAS 9: pn_back and cookbook v 3.0
Compose reply
Download message
Move To:
4 replies: 1 2 3 4
3 followups: 1 2 3

Private message: yes  no

Notes:

Notification:


Date: Wed, 22 Jul 2009 16:01:36 GMT
From: piero.ranalli@bo.astro.it
To: xmmhelp@sciops.esa.int
Cc: piero.ranalli@bo.astro.it
Subject: ESAS in SAS 9: pn_back and cookbook v 3.0
Full_Name: Piero Ranalli
Submission from: (NULL) (137.204.66.138)


Dear HelpDesk,

I have 2 questions about the ESAS package recently included in SAS 9.0:

1. Is the pn_back tool included in SAS 9?   It is present in the documentation (
http://xmm.esac.esa.int/sas/current/doc/pn_back/index.html ), but no such task
seems to be present after installing SAS 9  (while mos_back is indeed present).

2. In the SAS 9 online documentation for the 'esas' group of tasks, there is the
following reference (
http://xmm.esac.esa.int/sas/current/doc/esas/node10.html#cook ):
"Snowden, S. L., Kuntz, K. D., Cookbook for Analysis Procedures for XMM-Newton
EPIC MOS Observations of Extended Objects and the Diffuse Background, 2008, Vol
3.0.".

However, by looking at both the ESAC of US/GOF web pages, the only available
version of that document is Ver. 2.0 (2007)   (e.g., the file here:
ftp://xmm.esac.esa.int/pub/xmm-esas/xmm-esas.pdf ).
(Actually, the whole web page about ESAS in the ESAC website seem outdated, as
it still points to an old version of ESAS and also give the advice of using SAS
7.0.0 ...)

Is the ver. 3 (2008) of the ESAS cookbook actually available?


Thanks in advance,

Piero Ranalli
(University of Bologna)


Reply 1

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: piero.ranalli@bo.astro.it
Subject: Re: ESAS in SAS 9: pn_back and cookbook v 3.0 (PR#41486)
Date: Wed Jul 22 20:29:39 2009
Dear Piero Ranalli,

 thank you for these very useful question. I am in the process of investigations
and will let you know as soon as possible.

With best regards,
Jan-Uwe

> Full_Name: Piero Ranalli
> Submission from: (NULL) (137.204.66.138)
> 
> 
> Dear HelpDesk,
> 
> I have 2 questions about the ESAS package recently included in SAS 9.0:
> 
> 1. Is the pn_back tool included in SAS 9?   It is present in the
documentation
(
> http://xmm.esac.esa.int/sas/current/doc/pn_back/index.html ), but no such
task
> seems to be present after installing SAS 9  (while mos_back is indeed
present).
> 
> 2. In the SAS 9 online documentation for the 'esas' group of tasks, there
is
the
> following reference (
> http://xmm.esac.esa.int/sas/current/doc/esas/node10.html#cook ):
> "Snowden, S. L., Kuntz, K. D., Cookbook for Analysis Procedures for
XMM-Newton
> EPIC MOS Observations of Extended Objects and the Diffuse Background, 2008,
Vol
> 3.0.".
> 
> However, by looking at both the ESAC of US/GOF web pages, the only
available
> version of that document is Ver. 2.0 (2007)   (e.g., the file here:
> ftp://xmm.esac.esa.int/pub/xmm-esas/xmm-esas.pdf ).
> (Actually, the whole web page about ESAS in the ESAC website seem outdated,
as
> it still points to an old version of ESAS and also give the advice of using
SAS
> 7.0.0 ...)
> 
> Is the ver. 3 (2008) of the ESAS cookbook actually available?
> 
> 
> Thanks in advance,
> 
> Piero Ranalli
> (University of Bologna)


Reply 2

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: piero.ranalli@bo.astro.it
Subject: Re: ESAS in SAS 9: pn_back and cookbook v 3.0 (PR#41486)
Date: Thu Jul 23 13:38:29 2009
Dear Piero Ranalli,

 the ESAS package integrated in SAS v9.0 is brand new and is still under
development (indicated by the lower than 1 version number "esas-0.9.4").
In light of the usefulness of this package to the users it was decided
to include it in SAS 9.0. Even though some tasks related to epic-pn
analysis, specifically pn-spectra and pn_back, are available, they are
not supported yet and should not be used. These will hopefully be
available with the next patch release of SAS. Also, we hope to release
the next version of the SAS Manual within the next two months, and this
would include a more comprehensive documentation.

 In the meantime, we are happy to provide assistance if you need help
with anything that is not clear from the currently available version of the
documentation. Please also keep in mind that while the manual is out of
date for the installation in SAS, the basic sequence of the processing
is still valid and as specified in version 2 of the stand alone version
of the XMM-ESAS cookbook. The main difference is that cifbuild and odfingest are
no
longer run by mos-filter.

 Hope this is helpful.

With best regards,
Jan-Uwe Ness
XMM-Newton Science Operations Centre

> Full_Name: Piero Ranalli
> Submission from: (NULL) (137.204.66.138)
> 
> 
> Dear HelpDesk,
> 
> I have 2 questions about the ESAS package recently included in SAS 9.0:
> 
> 1. Is the pn_back tool included in SAS 9?   It is present in the
documentation
(
> http://xmm.esac.esa.int/sas/current/doc/pn_back/index.html ), but no such
task
> seems to be present after installing SAS 9  (while mos_back is indeed
present).
> 
> 2. In the SAS 9 online documentation for the 'esas' group of tasks, there
is
the
> following reference (
> http://xmm.esac.esa.int/sas/current/doc/esas/node10.html#cook ):
> "Snowden, S. L., Kuntz, K. D., Cookbook for Analysis Procedures for
XMM-Newton
> EPIC MOS Observations of Extended Objects and the Diffuse Background, 2008,
Vol
> 3.0.".
> 
> However, by looking at both the ESAC of US/GOF web pages, the only
available
> version of that document is Ver. 2.0 (2007)   (e.g., the file here:
> ftp://xmm.esac.esa.int/pub/xmm-esas/xmm-esas.pdf ).
> (Actually, the whole web page about ESAS in the ESAC website seem outdated,
as
> it still points to an old version of ESAS and also give the advice of using
SAS
> 7.0.0 ...)
> 
> Is the ver. 3 (2008) of the ESAS cookbook actually available?
> 
> 
> Thanks in advance,
> 
> Piero Ranalli
> (University of Bologna)


Followup 1

Compose reply
Download message
From: Ranalli Piero <piero.ranalli@gmail.com>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: ESAS in SAS 9: pn_back and cookbook v 3.0 (PR#41486)
Date: Thu, 23 Jul 2009 19:59:38 +0200
Dear Jan-Uwe Ness,

On Thursday 23 July 2009 15:38:28 you wrote:
> to include it in SAS 9.0. Even though some tasks related to epic-pn
> analysis, specifically pn-spectra and pn_back, are available, they are
> not supported yet and should not be used. These will hopefully be
> available with the next patch release of SAS. Also, we hope to release
> the next version of the SAS Manual within the next two months, and this
> would include a more comprehensive documentation.

ok

>  In the meantime, we are happy to provide assistance if you need help
> with anything that is not clear from the currently available version of the
> documentation. Please also keep in mind that while the manual is out of
> date for the installation in SAS, the basic sequence of the processing
> is still valid and as specified in version 2 of the stand alone version
> of the XMM-ESAS cookbook. The main difference is that cifbuild and
> odfingest are no
> longer run by mos-filter.

Fine, thanks.

I have already started with ver 2.0 of the manual, if I need help I will ask.

Also, I have noticed that the ESAS calibration files (e.g., filter wheel 
closed events) seem not to be included in the SAS or in the CCF release. (I 
downloaded them from the background web page, but I think it was worth 
reporting it).

best regards,
Piero



Reply 3

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: piero.ranalli@gmail.com
Subject: Re: ESAS in SAS 9: pn_back and cookbook v 3.0 (PR#41486)
Date: Fri Jul 24 15:56:35 2009
Dear Piero,

 thank you for the additional report, I will forward it to the people in charge.
Meanwhile, the SAS watchout page has been updated in response to your
questions:
http://xmm.esac.esa.int/sas/current/watchout/

Thanks again for the comments.

With best regards,
Jan-Uwe


> Dear Jan-Uwe Ness,
> 
> On Thursday 23 July 2009 15:38:28 you wrote:
>> to include it in SAS 9.0. Even though some tasks related to epic-pn
>> analysis, specifically pn-spectra and pn_back, are available, they are
>> not supported yet and should not be used. These will hopefully be
>> available with the next patch release of SAS. Also, we hope to release
>> the next version of the SAS Manual within the next two months, and
this
>> would include a more comprehensive documentation.
> 
> ok
> 
>>  In the meantime, we are happy to provide assistance if you need help
>> with anything that is not clear from the currently available version of
the
>> documentation. Please also keep in mind that while the manual is out
of
>> date for the installation in SAS, the basic sequence of the processing
>> is still valid and as specified in version 2 of the stand alone
version
>> of the XMM-ESAS cookbook. The main difference is that cifbuild and
>> odfingest are no
>> longer run by mos-filter.
> 
> Fine, thanks.
> 
> I have already started with ver 2.0 of the manual, if I need help I will
ask.
> 
> Also, I have noticed that the ESAS calibration files (e.g., filter wheel 
> closed events) seem not to be included in the SAS or in the CCF release. (I

> downloaded them from the background web page, but I think it was worth 
> reporting it).
> 
> best regards,
> Piero
> 
> 


Followup 2

Compose reply
Download message
From: Ranalli Piero <piero.ranalli@gmail.com>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: ESAS in SAS 9: pn_back and cookbook v 3.0 (PR#41486)
Date: Mon, 27 Jul 2009 16:12:10 +0200
--Boundary-00=_6WbbKisR6ecXI9Z
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Dear Jan-Uwe,

On Friday 24 July 2009 17:56:34 you wrote:
>  thank you for the additional report, I will forward it to the people in
> charge. Meanwhile, the SAS watchout page has been updated in response to

Thanks a lot for reporting my comments.

And... I have a few more :)

The most important one is this:
- mos_back seems not to include any ccd in its processing.
I start the data analysis by running in sequence emchain, mos-filter, and 
mos-spectra. Everything looks fine: I get images and spectra. However, when 
calling mos_back:

$ mos_back -V 5 prefix=1S001 caldb=$ESAS_CALDB elow=4500 ehigh=8000 
ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=1 ccd6=0  ccd7=1 diag=1

(the full output is attached at the end of this mail, while here I only 
include the lines I think are relevant), there is this line in 
the output:

 CCD selection 0 0 0 0 0 0 0

then the final diagnostics look like this:

 Final parameter values and the formal standard errors
 I0                       NaN +/-    0.00000
 I1                  -0.10000 +/-    0.00000
 I2                   0.03000 +/-    0.00000
 I3                  -0.01000 +/-    0.00000
 I4                   0.00300 +/-    0.00000
 I5                  -0.00010 +/-    0.00000

and finally, the file mos1S001-spec.qdp only contain the souce spectrum, while 
the particle background is zero at any energy. (I also include this file in 
this email).
Then, I also checked if the older version of this tool, i.e. xmm_back from 
ESAS 2.0, was working: I found that its output from ver 2.0 is reasonable (no 
NaN's nor zeroes, and a xxx-spec.qdp file looking like the ones in the 
cookbook), provided that do not specify the energy bounds (otherwise, 
xmm_back complains that "Input array size not equal to image" while reading 
the energy-bound image; I'll try redoing all the processing with the old 
version of esas to see if it works).



----------

Other less important things about esas, these are more sort of nuisances:
* mos_back seems very picky about parameters: when called from the command 
line, all parameters have to be specified on the command line, and if any one 
is missing, it exits with a ParamMandatory error.   
* mos-filter deletes (or renames?) the event lists made by emchain.


Best regards,
Piero

--Boundary-00=_6WbbKisR6ecXI9Z
Content-Type: text/plain;
  charset="iso-8859-1";
  name="mos_back.log.1"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="mos_back.log.1"

mos_back:- Executing (routine): mos_back prefix=1S001
caldb=/Users/piero/Public/XMM-CDFS/ESAS_CALDB/caldb/ diag=1 elow=4500 ehigh=8000
ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=1 ccd6=0 ccd7=1  -V 5
mos_back:- mos_back (esas-0.9.4)  [xmmsas_20090615_1803-9.0.0] started: 
2009-07-24T16:19:40.000
 Number of command line arguments:  12
 xmmdir: /Users/piero/Public/XMM-CDFS/ESAS_CALDB/caldb/                         
        
 diag:  1
 prefix: 1S001
 mosnum:  1
 obj_file: mos1S001-obj.pi                                                      
          
 obj_rmf: mos1S001.rmf                                                          
         
 el, eh:  4500 8000
 CCD selection 0 0 0 0 0 0 0
 WARNING: if chip 3, 4 or 6 are missing spurious 
 gold features can arise in the 2.04-2.33, 
 9.38-9.98, 11.03-11.82 keV regions
 Process the observation data
 Backscale and exposure from the observation data
 Process the FWC data from the object region
 Backscale and exposure from the FWC data
 Process the observation data from the corner regions
 Backscale and augmented exposure from the corners of the observation data
 Process the FWC corner data
 Backscale and augmented exposure from the corners of the FWC data
 Backscale for the FWC corner and FWC region data
 Chip  1  backscale=   0.0000000  backscale =   0.0000000
 Chip  2  backscale=   0.0000000  backscale =   0.0000000
 Chip  3  backscale=   0.0000000  backscale =   0.0000000
 Chip  4  backscale=   0.0000000  backscale =   0.0000000
 Chip  5  backscale=   0.0000000  backscale =   0.0000000
 Chip  6  backscale=   0.0000000  backscale =   0.0000000
 Chip  7  backscale=   0.0000000  backscale =   0.0000000
 FC_AREA, REG_AREA, RATIO:    0.0000000   0.0000000 NaN
 test111
 Reading input file
 mos1S001-obj-im-det-4500-8000.fits
 Total observation counts in band    3.0241000E+04
 Total background counts in band    0.0000000
 File exists with output file name
 Clobber the file and continue
 DGAUSJ, singular matrix, pos 2
 MQM ==> Bad return from DGAUSJ
 DGAUSJ, singular matrix, pos 2
 MQM ==> Bad return from DGAUSJ
 DGAUSJ, singular matrix, pos 2
 MQM ==> Bad return from DGAUSJ
 DGAUSJ, singular matrix, pos 2
 MQM ==> Bad return from DGAUSJ
 DGAUSJ, singular matrix, pos 2
 MQM ==> Bad return from DGAUSJ
 DGAUSJ, singular matrix, pos 2
 MQM ==> Bad return from DGAUSJ
 DGAUSJ, singular matrix, pos 2
 MQM ==> 

Message of length 63502 truncated


Reply 4

Resend
From: Ignacio de la Calle <xmmhelp@sciops.esa.int>
To: piero.ranalli@gmail.com
Subject: Re: ESAS in SAS 9: pn_back and cookbook v 3.0 (PR#41486)
Date: Tue Jul 28 14:55:14 2009
Dear Piero,

I have been in contact with the ESAS developer and he has a couple
of suggestions. Also the information you will get out of this will
help us to further find out what is going wrong, because with the
information we have at the moment it is hard to find.

- Start with a fresh window and empty directory
- Set /dirstr/ to the data set's root directory and copy the ODF
  data to /dirstr/odf.
- Create the directory /dirstr/proc for execution
- Set /ccfdir/ to the CCF directory, and check that it
  includes all of the ESAS CCF files 
- Follow these steps:

invoke SAS

setenv DATAPATH /dirstr/
cd $DATAPATH/proc
setenv SAS_CCF $DATAPATH/proc/ccf.cif
setenv SAS_ODF $DATAPATH/odf
setenv SAS_CCFPATH /ccfdir/


cifbuild withccfpath=no analysisdate=now category=XMMCCF calindexset=$SAS_CCF
fullpath=yes verbosity=1

odfingest odfdir=$SAS_ODF outdir=$SAS_ODF verbosity=1

emchain

mos-filter

mos-spectra prefix="1S001" caldb=$ESAS_CALDB reg=reg.txt mask=0 elow=4500
ehigh=8000 ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=1 ccd6=0  ccd7=1

mos_back prefix=1S001 caldb=$ESAS_CALDB elow=4500 ehigh=8000 ccd1=1 ccd2=1
ccd3=1 ccd4=1 ccd5=1 ccd6=0  ccd7=1 diag=1

Please send us the directory listing and screen output from
mos-filter, mos-spectra, and mos_back. It could be that the
failure is probably in mos-filter or mos-spectra, and mos_back
is just not acting properly because of some incorrect input.

Many thanks again for your input,

Ignacio de la Calle
XMM-Newton SOC


> Content-Type: text/plain;
>   charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> Dear Jan-Uwe,
> 
> On Friday 24 July 2009 17:56:34 you wrote:
>>  thank you for the additional report, I will forward it to the people
in
>> charge. Meanwhile, the SAS watchout page has been updated in response
to
> 
> Thanks a lot for reporting my comments.
> 
> And... I have a few more :)
> 
> The most important one is this:
> - mos_back seems not to include any ccd in its processing.
> I start the data analysis by running in sequence emchain, mos-filter, and 
> mos-spectra. Everything looks fine: I get images and spectra. However, when

> calling mos_back:
> 
> $ mos_back -V 5 prefix=1S001 caldb=$ESAS_CALDB elow=4500 ehigh=8000 
> ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=1 ccd6=0  ccd7=1 diag=1
> 
> (the full output is attached at the end of this mail, while here I only 
> include the lines I think are relevant), there is this line in 
> the output:
> 
>  CCD selection 0 0 0 0 0 0 0
> 
> then the final diagnostics look like this:
> 
>  Final parameter values and the formal standard errors
>  I0                       NaN +/-    0.00000
>  I1                  -0.10000 +/-    0.00000
>  I2                   0.03000 +/-    0.00000
>  I3                  -0.01000 +/-    0.00000
>  I4                   0.00300 +/-    0.00000
>  I5                  -0.00010 +/-    0.00000
> 
> and finally, the file mos1S001-spec.qdp only contain the souce spectrum,
while

> the particle background is zero at any energy. (I also include this file in

> this email).
> Then, I also checked if the older version of this tool, i.e. xmm_back from

> ESAS 2.0, was working: I found that its output from ver 2.0 is reasonable
(no

> NaN's nor zeroes, and a xxx-spec.qdp file looking like the ones in the 
> cookbook), provided that do not specify the energy bounds (otherwise, 
> xmm_back complains that "Input array size not equal to image" while reading

> the energy-bound image; I'll try redoing all the processing with the old 
> version of esas to see if it works).
> 
> 
> 
> ----------
> 
> Other less important things about esas, these are more sort of nuisances:
> * mos_back seems very picky about parameters: when called from the command

> line, all parameters have to be specified on the command line, and if any
one

> is missing, it exits with a ParamMandatory error.   
> * mos-filter deletes (or renames?) the event lists made by emchain.
> 
> 
> Best regards,
> Piero
> 
> --Boundary-00=_6WbbKisR6ecXI9Z
> Content-Type: text/plain;
>   charset="iso-8859-1";
>   name="mos_back.log.1"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
> 	filename="mos_back.log.1"
> 
> mos_back:- Executing (routine): mos_back prefix=1S001
> caldb=/Users/piero/Public/XMM-CDFS/ESAS_CALDB/caldb/ diag=1 elow=4500
ehigh=8000
> ccd1=1 ccd2=1 ccd3=1 ccd4=1 ccd5=1 ccd6=0 ccd7=1  -V 5
> mos_back:- mos_back (esas-0.9.4)  [xmmsas_20090615_1803-9.0.0] started: 
> 2009-07-24T16:19:40.000
>  Number of command line arguments:  12
>  xmmdir: /Users/piero/Public/XMM-CDFS/ESAS_CALDB/caldb/                    
  
 
>         
>

Message of length 71925 truncated


Followup 3

Compose reply
Download message
From: Ranalli Piero <piero.ranalli@gmail.com>
To: Ignacio de la Calle <xmmhelp@sciops.esa.int>
Subject: Re: ESAS in SAS 9: pn_back and cookbook v 3.0 (PR#41486)
Date: Thu, 30 Jul 2009 15:29:01 +0200
--Boundary-00=_dAacK5FJvt3ct82
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Tuesday 28 July 2009 16:55:13 you wrote:
> Dear Piero,
>
> I have been in contact with the ESAS developer and he has a couple
> of suggestions. Also the information you will get out of this will
> help us to further find out what is going wrong, because with the
> information we have at the moment it is hard to find.


Dear Ignacio,

Thanks for your reply. I have followed your instructions. Please find attached 
the results (directory listings and tool outputs).


> Please send us the directory listing and screen output from
> mos-filter, mos-spectra, and mos_back. It could be that the
> failure is probably in mos-filter or mos-spectra, and mos_back
> is just not acting properly because of some incorrect input.

Filenames are as follows:
emchain.list   is the directory list after running emchain
mos-filter.log is the output from mos-filter
mos-filter.list is the directory list after running mos-filter
etc.

Best regards,

Piero

--Boundary-00=_dAacK5FJvt3ct82
Content-Type: text/plain;
  charset="iso-8859-1";
  name="emchain.list"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="emchain.list"

P0555782301EMX000FBKGTI0000.FIT
P0555782301EMX000FBKTSR0000.FIT
P0555782301M1S001FBKTSR0000.FIT
P0555782301M1S001MIEVLI0000.FIT
P0555782301M1U002FBKTSR0000.FIT
P0555782301M1U002MIEVLI0000.FIT
P0555782301M1X000HK_GTI0000.FIT
P0555782301M2S002FBKTSR0000.FIT
P0555782301M2S002MIEVLI0000.FIT
P0555782301M2U002FBKTSR0000.FIT
P0555782301M2U002MIEVLI0000.FIT
P0555782301M2X000HK_GTI0000.FIT
P0555782301OBX000ATTGTI0000.FIT
P0555782301OBX000ATTTSR0000.FIT
ccf.cif
emchain.list

--Boundary-00=_dAacK5FJvt3ct82
Content-Type: text/plain;
  charset="iso-8859-1";
  name="mos-filter.list"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="mos-filter.list"

P0555782301EMX000FBKGTI0000.FIT
P0555782301EMX000FBKTSR0000.FIT
P0555782301M1S001-corevlifilt.FIT
P0555782301M1S001-corimgfilt.FIT
P0555782301M1S001-objimg.FIT
P0555782301M1S001-objimgfilt.FIT
P0555782301M1S001FBKTSR0000.FIT
P0555782301M1U002-corevlifilt.FIT
P0555782301M1U002-corimgfilt.FIT
P0555782301M1U002-objimg.FIT
P0555782301M1U002-objimgfilt.FIT
P0555782301M1U002FBKTSR0000.FIT
P0555782301M1X000HK_GTI0000.FIT
P0555782301M2S002-corevlifilt.FIT
P0555782301M2S002-corimgfilt.FIT
P0555782301M2S002-objimg.FIT
P0555782301M2S002-objimgfilt.FIT
P0555782301M2S002FBKTSR0000.FIT
P0555782301M2U002-corevlifilt.FIT
P0555782301M2U002-corimgfilt.FIT
P0555782301M2U002-objimg.FIT
P0555782301M2U002-objimgfilt.FIT
P0555782301M2U002FBKTSR0000.FIT
P0555782301M2X000HK_GTI0000.FIT
P0555782301OBX000ATTGTI0000.FIT
P0555782301OBX000ATTTSR0000.FIT
ccf.cif
emchain.list
mos-filter.list
mos-filter.log
mos1S001-clean.fits
mos1S001-corn-image.fits
mos1S001-corn.fits
mos1S001-gti.fits
mos1S001-gti.txt
mos1S001-hist.qdp
mos1S001-obj-image-det-soft.fits
mos1S001-obj-image-det-unfilt.fits
mos1S001-obj-image-det.fits
mos1S001-obj-image-sky.fits
mos1S001-ori.fits
mos1S001-rate.fits
mos1S001-ratec.fits
mos1U002-clean.fits
mos1U002-corn-image.fits
mos1U002-corn.fits
mos1U002-gti.fits
mos1U002-gti.txt
mos1U002-hist.qdp
mos1U002-obj-image-det-soft.fits
mos1U002-obj-image-det-unfilt.fits
mos1U002-obj-image-det.fits
mos1U002-obj-image-sky.fits
mos1U002-ori.fits
mos1U002-rate.fits
mos1U002-ratec.fits
mos2S002-clean.fits
mos2S002-corn-image.fits
mos2S002-corn.fits
mos2S002-gti.fits
mos2S002-gti.txt
mos2S002-hist.qdp
mos2S002-obj-image-det-soft.fits
mos2S002-obj-image-det-unfilt.fits
mos2S002-obj-image-det.fits
mos2S002-obj-image-sky.fits
mos2S002-ori.fits
mos2S002-rate.fits
mos2S002-ratec.fits
mos2U002-clean.fits
mos2U002-corn-image.fits
mos2U002-corn.fits
mos2U002-gti.fits
mos2U002-gti.txt
mos2U002-hist.qdp
mos2U002-obj-image-det-soft.fits
mos2U002-obj-image-det-unfilt.fits
mos2U002-obj-image-det.fits
mos2U002-obj-image-sky.fits
mos2U002-ori.fits
mos2U002-rate.fits
mos2U002-ratec.fits

--Boundary-00=_dAacK5FJvt3ct82
Content-Type: text/x-log;
  charset="iso-8859-1";
  name="mos-filter.log"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="mos-filter.log"

   
Task: mos-filter
Version: 3.01
Date: 2008-09-16
Author: S. L. Snowden, based on code from K. D. Kuntz
   
Step 1: Do Some Bookkeeping
   
P0555782301M1S001MIEVLI0000.FIT
P0555782301M2S002MIEVLI0000.FIT
P0555782301M1U002MIEVLI0000.FIT
P0555782301M2U002MIEVLI0000.FIT
0 P0555782301M1S001MIEVLI0000.FIT
Filter: 'Thin1'
 
espfilt eventset=mos1S001.fits
   
mv P0555782301M1S001-objevlifilt.FIT mos1S001-clean.fits
mv P0555782301M1S001-objlc.FIT mos1S001-rate.fits
mv P0555782301M1S001-corlc.FIT mos1S001-ratec.fits
mv P0555782301M1S001-gti.FIT mos1S001-gti.fits
mv P0555782301M1S001-gti.txt mos1S001-gti.txt
mv P0555782301M1S001-hist.qdp mos1S001-hist.qdp
Revolution: 1672
 
Observation Date: '2009-01-24T18:34:55'
 
Filter: 'Thin1'
 
Obser

Message of length 98246 truncated

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