Research & Science Home ESA Public Web Site Sci-Tech Portal      XMM-Newton Public Web Site XMM-Newton Sci-Tech Portal
Astrophysics Missions Planetary Exploration Missions Solar Terrestrial Science Missions Fundamental Physics Missions Science Faculty

SAS watchout page


My odfingest run complaints about TimeOutOfRange. Is my ODF healthy?

Your ODF is perfectly healthy. However, your odfingest run might be confused by the presence of pn offset table dumps in the ODF.

Offset tables are used to derive the correct reference scale of the pn energy gain. As of spring 2004, dumps of the pn offset tables, calculated on board after the completion of an observation, are added to the ODF, and used by the SAS to reconstruct the time-dependent gain.

Unfortunately, a bug in odfingest identifies the exposure end time with the pn offset dump end time. As the latter occurs earlier then the former, odfingest complaints that no housekeeping information is available toward the end of the exposure Warnings like the following:

** odfingest: warning (HousekeepingParameterMissing), PN/U003TimeOutOfRange: upper time bound for CMCORR_Q3 in /d/mguainaz/0205370201/odf/0809_0205370201_PNX00000PAH.FIT:PNPAH1 not available. Looking for an entry at or around 2004-05-10T18:10:54.000 but the available time range in PNPAH1 is 2004-05-10T04:35:01.000 - 2004-05-10T17:56:03.000

are consequently generated. Related warning can appear while running subsequent SAS tasks, such as:

** atthkgen: warning (NoAttitude), The attitude was requested for time 200599090.184 which is more than 20 s outside the period for which the attitude is known (closest time is 20.2135487497 s away).

** eexpmap: warning (NullValues), NULL values in the attitude table were ignored

Such warnings are harmless, and can be ignored.

This bug will be fixed in future SAS version


   Copyright 2012© European Space Agency. All rights reserved.
This page was last updated on 3 May, 2010.