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 Backgrounds/23573
Full headers

From: Dong-Woo Kim <kim@head.cfa.harvard.edu>
Subject: Can I run 'evigweight' on blank sky event files
Compose reply
Download message
Move To:
1 replies: 1
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Wed, 18 Oct 2006 16:22:29 -0400 (EDT)
From: Dong-Woo Kim <kim@head.cfa.harvard.edu>
Subject: Can I run 'evigweight' on blank sky event files
To: xmmhelp@sciops.esa.int, snowden@milkyway.gsfc.nasa.gov
Cc: kim@head.cfa.harvard.edu

Hi,

I ran 'evigweight' on the blank sky file I downloaded from the XMM
website, but got the following message and not sure whether it worked
or not. 

I ran it on a linux machine w/ SAS 20060628.
My blank sky file is the same as in 
   "M1.T.FF.EVLIRP.FIT" 
taken from 
ftp://xmm.esac.esa.int/pub/ccf/constituents/extras/background/epic/blank_sky/latest

thanks.
- dw

--------------------------------------------------

C> which evigwight 
/soft/XMM/xmmsas_20060628_1801/bin/evigweight

C> evigweight ineventset=mos1_thin_skybkg.fits 
outeventset=mos1_thin_skybkg_vigcor.fits


evigweight:- Executing (routine): evigweight ineventset=mos1_thin_skybkg.fits
outeventset=mos1_thin_skybkg_vigcor.fits newoutput=yes weightcol
name=WEIGHT witheffectivearea=yes withfiltertransmission=yes
withquantumefficiency=yes  -w 3 -V 3
** evigweight: warning (MandatoryAttributeNotFound), In defining the Cal state
from a data set or block (one or more of) the mandatory attribu
te(s) `DATE-OBS/DATE-END' was/were not found - from this/these attribute(s) the
actual exposure start/end date is derived which is now not pos
sible - will assume a default value for the exposure start/end date - please
check the diagnostic output below (requires verbosity >= Verbose)
 for the effective Cal state settings. Please note: In case of a possibly
incorrect exposure start/end date the retrieval of exposure start/en
d date-dependent calibration quantities via the Cal is likely to yield
INADEQUATE data which ultimately might lead to INCORRECT scientific res
ults
** evigweight: warning (MandatoryAttributeNotFound), In defining the Cal state
from a data set or block (one or more of) the mandatory attribu
te(s) `DATE-OBS/DATE-END' was/were not found - from this/these attribute(s) the
actual exposure start/end date is derived which is now not pos
sible - will assume a default value for the exposure start/end date - please
check the diagnostic output below (requires verbosity >= Verbose)
 for the effective Cal state settings. Please note: In case of a possibly
incorrect exposure start/end date the retrieval of exposure start/en
d date-dependent calibration quantities via the Cal is likely to yield
INADEQUATE data which ultimately might lead to INCORRECT scientific res
ults
evigweight:- CCF constituents accessed by the calibration server:
CifEntry{EMOS1, LINCOORD, 17, /data/dw3/XMM2/CCF/EMOS1_LINCOORD_0017.CCF,
1998-01-01T00:00:00.000}
CifEntry{RGS1, LINCOORD, 8, /data/dw3/XMM2/CCF/RGS1_LINCOORD_0008.CCF,
1998-01-01T00:00:00.000}
CifEntry{XMM, MISCDATA, 21, /data/dw3/XMM2/CCF/XMM_MISCDATA_0021.CCF,
1999-01-01T00:00:00.000}
CifEntry{XRT1, XAREAEF, 8, /data/dw3/XMM2/CCF/XRT1_XAREAEF_0008.CCF,
2000-01-13T00:00:00.000}


** evigweight: warning (MandatoryAttributeNotFound), In defining the Cal state
from a data set or block (one or more of) the mandatory attribu
te(s) `DATE-OBS/DATE-END' was/were not found - from this/these attribute(s) the
actual exposure start/end date is derived which is now not pos
sible - will assume a default value for the exposure start/end date - please
check the diagnostic output below (requires verbosity >= Verbose)
 for the effective Cal state settings. Please note: In case of a possibly
incorrect exposure start/end date the retrieval of exposure start/en
d date-dependent calibration quantities via the Cal is likely to yield
INADEQUATE data which ultimately might lead to INCORRECT scientific res
ults
** evigweight: warning (SummaryOfWarnings), 
   warning MandatoryAttributeNotFound silently occurred 3508310 times

-- 

========
Dong-Woo Kim                              Harvard-Smithsonian Center
kim@cfa.harvard.edu                                 for Astrophysics
Phone:  617-496-7852                      60 Garden Street, MS 6
Fax:    617-495-7356                      Cambridge, MA  02138  USA


Reply 1

Resend
From: Maria Diaz Trigo <xmmhelp@sciops.esa.int>
To: kim@head.cfa.harvard.edu
Subject: Re: Can I run 'evigweight' on blank sky event files (PR#23573)
Date: Thu Oct 19 13:29:48 2006
Dear Dong-Woo,

the warnings you get are related to the lack of the keyword DATE-OBS. 
Our colleagues who created the blank sky event
files explain the following:

The blank sky files are constructed from several different event lists,
spanning
a large range in time over the mission. Date-related keywords, for example
DATE-OBS, have therefore been removed. A few SAS tasks require date and time
stamp keywords. It is recommended that these keywords be added by the user as
required. Missing date and time keywords could be e.g. set to that of the
user's
source spectrum. This can be achieved for example using the FTOOLS
viewer/editor
fv. (see updated blank sky web page).

You could also have a look at the Helpdesk message 22859 in
http://xmm.esac.esa.int/external/xmm_user_support/xmmhelp_frame.shtml, 
where a lot of information is given about the blank sky fields. 

Best regards,

Maria

MAria Diaz Trigo
XMM-Newton Users Support Group


> 
> 
> Hi,
> 
> I ran 'evigweight' on the blank sky file I downloaded from the XMM
> website, but got the following message and not sure whether it worked
> or not. 
> 
> I ran it on a linux machine w/ SAS 20060628.
> My blank sky file is the same as in 
>    "M1.T.FF.EVLIRP.FIT" 
> taken from 
> ftp://xmm.esac.esa.int/pub/ccf/constituents/extras/background/epic/blank_sky/latest
> 
> thanks.
> - dw
> 
> --------------------------------------------------
> 
> C> which evigwight 
> /soft/XMM/xmmsas_20060628_1801/bin/evigweight
> 
> C> evigweight ineventset=mos1_thin_skybkg.fits 
> outeventset=mos1_thin_skybkg_vigcor.fits
> 
> 
> evigweight:- Executing (routine): evigweight
ineventset=mos1_thin_skybkg.fits
> outeventset=mos1_thin_skybkg_vigcor.fits newoutput=yes weightcol
> name=WEIGHT witheffectivearea=yes withfiltertransmission=yes
> withquantumefficiency=yes  -w 3 -V 3
> ** evigweight: warning (MandatoryAttributeNotFound), In defining the Cal
state
> from a data set or block (one or more of) the mandatory attribu
> te(s) `DATE-OBS/DATE-END' was/were not found - from this/these attribute(s)
the
> actual exposure start/end date is derived which is now not pos
> sible - will assume a default value for the exposure start/end date -
please
> check the diagnostic output below (requires verbosity >= Verbose)
>  for the effective Cal state settings. Please note: In case of a possibly
> incorrect exposure start/end date the retrieval of exposure start/en
> d date-dependent calibration quantities via the Cal is likely to yield
> INADEQUATE data which ultimately might lead to INCORRECT scientific res
> ults
> ** evigweight: warning (MandatoryAttributeNotFound), In defining the Cal
state
> from a data set or block (one or more of) the mandatory attribu
> te(s) `DATE-OBS/DATE-END' was/were not found - from this/these attribute(s)
the
> actual exposure start/end date is derived which is now not pos
> sible - will assume a default value for the exposure start/end date -
please
> check the diagnostic output below (requires verbosity >= Verbose)
>  for the effective Cal state settings. Please note: In case of a possibly
> incorrect exposure start/end date the retrieval of exposure start/en
> d date-dependent calibration quantities via the Cal is likely to yield
> INADEQUATE data which ultimately might lead to INCORRECT scientific res
> ults
> evigweight:- CCF constituents accessed by the calibration server:
> CifEntry{EMOS1, LINCOORD, 17, /data/dw3/XMM2/CCF/EMOS1_LINCOORD_0017.CCF,
> 1998-01-01T00:00:00.000}
> CifEntry{RGS1, LINCOORD, 8, /data/dw3/XMM2/CCF/RGS1_LINCOORD_0008.CCF,
> 1998-01-01T00:00:00.000}
> CifEntry{XMM, MISCDATA, 21, /data/dw3/XMM2/CCF/XMM_MISCDATA_0021.CCF,
> 1999-01-01T00:00:00.000}
> CifEntry{XRT1, XAREAEF, 8, /data/dw3/XMM2/CCF/XRT1_XAREAEF_0008.CCF,
> 2000-01-13T00:00:00.000}
> 
> 
> ** evigweight: warning (MandatoryAttributeNotFound), In defining the Cal
state
> from a data set or block (one or more of) the mandatory attribu
> te(s) `DATE-OBS/DATE-END' was/were not found - from this/these attribute(s)
the
> actual exposure start/end date is derived which is now not pos
> sible - will assume a default value for the exposure start/end date -
please
> check the diagnostic output below (requires verbosity >= Verbose)
>  for the effective Cal state settings. Please note: In case of a possibly
> incorrect exposure start/end date the retrieval of exposure start/en
> d date-dependent calibration quantities via the Cal is likely to yield
> INADEQUATE data which ultimately might lead to INCORRECT scientific res
> ults
> ** evigweight: warning (SummaryOfWarnings), 
>    warning MandatoryAttributeNotFound silently occurred 3508310 times
> 
&

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