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

From: "Michael J. Freyberg" <mjf@xray.mpe.mpg.de>
Subject: Re: Observation log browser and SUBMODE keyword discrepancy
Compose reply
Download message
Move To:
0 replies:
0 followups:

Private message: yes  no

Notes:

Notification:


To: Jenny Carter <jac48@star.le.ac.uk>
Cc: xmmhelp@sciops.esa.int
Subject: Re: Observation log browser and SUBMODE keyword discrepancy 
Date: Fri, 02 May 2008 19:43:28 +0200
From: "Michael J. Freyberg" <mjf@xray.mpe.mpg.de>
Hi Jenny,

the OLB is filled manually (at least in the past), while the SUBMODE
keyword is filled by the SAS task "epframes" via the housekeeping
information, especially via the parameter F1294 in the PMH file.

Moreover, this task also checks the time differences between two
frames and "suggests" from this quantity the instrument submode,
as an independent (and the best!) check.
With SAS_VERBOSITY=5 (or higher) you may see for both observations
  epframes:-  MODE, F1294, CHOP suggested to be: 1 3 0
where "MODE" is coded as in the CAL (0=FF,1=eFF,2=LW,3=SW,4=TI,5=BU)
and F1294 is non-zero only for eFF mode.

Also "odfingest" is analysing the HK contents and it writes e.g.
FRAME_TIME_PARAMETER = 3
(i.e. the value of F1294) into the summary file.

So in cases of inconsistency you should prefer the SAS-based values.

Cheers,
Michael


> Hi,
> 
> I have been looking at a couple of observations and have noticed a 
> discrepancy between the 'Mode' as given by the Observation Log Browser and 
> that of the SUBMODE keyword of the relevant event file.
> 
> I have only found this as a problem for PN between extended full-frame and 
> full-frame mode.
> 
> For example:
>  	obsn id. 0112971001 PN Obs log browser mode = Full frame
>  		                          SUBMODE   = PrimeFullWindowExtended
> 
>          obsn id. 0022140101 PN Obs log browser mode = Full frame
>                                            SUBMODE   =
PrimeFullWindowExtended
> 
> 
> Regards,
> Jenny
> 
> 
> -- 
> ---------------------------------------------------------------------
> Jenny Carter		           email :     jac48@star.le.ac.uk
> Dept. of Physics and Astronomy,    Tel   :     +44 (0)116 252 5244
> University of Leicester,           Fax   :     +44 (0)116 252 3311
> Leicester LE1 7RH, U.K.            http://www.star.le.ac.uk/~jac48
> ---------------------------------------------------------------------


------------------------------------------------------------------------
 Michael Freyberg                    | Tel   +49(89)30000-3849 (MPE)
 MPI f. extraterrestrische Physik    | Tel   +49(89)745577-15  (PANTER)
 Giessenbachstr.1                    | Fax   +49(89)30000-3569
 D-85748 Garching                    | Email  mjf@mpe.mpg.de
 Germany                             | Office 1.2.06
------------------------------------------------------------------------

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