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 EPICMOS/17400
Full headers

From: ameer@science.uva.nl
Subject: odf file missing: ????_??????????_M1X00000HTH.FIT.
Compose reply
Download message
Move To:
2 replies: 1 2
0 followups:

Private message: yes  no

Notes:

Notification:


Date: Mon, 21 Mar 2005 19:05:48 GMT
From: ameer@science.uva.nl
To: xmmhelp@xmm.vilspa.esa.es
Subject: odf file missing: ????_??????????_M1X00000HTH.FIT.
Name: Arjen van der Meer

Email_Address: ameer@science.uva.nl

Topic: ODF files

Other_Topic: 

Usage_Mode: command line

SAS_Release: xmmsas_20040318_1831 - aka 6.0.0

Task_Version: odfingest (odfingest-3.23.5) [xmmsas_20041122_1834-6.1.0]

Type: report a showstopper

Title: odf file missing: ????_??????????_M1X00000HTH.FIT.

Description: Dear XMM-Newton Science Operations Centre,

I used SASversion 6.1.0 (was not in the possible options to select) rather than
6.0.0. to start the first steps of reduction of dataset: 0828_0203500201

Running odfingest gives the following error:
** odfingest: warning (HousekeepingParameterMissing), In the directory
/../../0203500201/odf I expected to find one and only one dataset matching the
pattern ????_??????????_M1X00000HTH.FIT. Instead I found 0

I check the ODF directory myself I could find the file
0828_0203500201_M2X00000HTH.FIT, the similar file for MOS2, but not
0828_0203500201_M1X00000HTH.FIT the file for MOS1.
I do have MOS1 in timing mode, but another dataset in timing mode shows the
above mentioned file.

After this "warning" it produces a lot of warnings about missing
housekeepingparameters, which should be in this file above of course. However, a
xxxxx_SUM.SAS file is produced. Can these warnings be ignored? It is not
entirely clear how important this file is.

Thank you in advance,

Arjen van der Meer

Operating_System: other

Other_Operating_System: Fedora Core 3, with Enterprise 3 SAS version

Instrument: emos1

Data_Type: timing

Observation_Identifier: 0828_0203500201

Exposure_Identifier: 

Private: 

Submitted_From: 82.157.7.128 (82.157.7.128)

Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111
Firefox/1.0

Referer: http://xmm.vilspa.esa.es/xmmhelp

Identify: 


Reply 1

Resend
From: Matthias Ehle <xmmhelp@xmm.vilspa.esa.es>
To: ameer@science.uva.nl
Subject: Re: odf file missing: ????_??????????_M1X00000HTH.FIT. (PR#17400)
Date: Tue Mar 22 08:57:22 2005
Dear Arjen van der Meer

you wrote: 
> After this "warning" it produces a lot of warnings about missing
> housekeepingparameters, which should be in this file above of course.
However,
a
> xxxxx_SUM.SAS file is produced. Can these warnings be ignored? It is not
> entirely clear how important this file is.

I have fowarded your question to our ODF and MOS experts and will let you have
their reply as soon as possible (probably after Easter though).

Checking the PP0203500201PPSMSG000_0.ASC delivery note for the pipeline
products
I see no problem reported for MOS1. Also emproc is processing the MOS data
without any warning related to missing housekeeping data. Hence the calibrated
timing mode event list looks good to me.

Cheers,
  Matthias

--
   Dr Matthias Ehle 
   XMM-Newton User Support Group
   European Space Astronomy Centre


Reply 2

Resend
From: Matthias Ehle <xmmhelp@xmm.vilspa.esa.es>
To: ameer@science.uva.nl
Subject: Re: odf file missing: ????_??????????_M1X00000HTH.FIT. (PR#17400)
Date: Mon Jun  6 10:23:55 2005
Dear Arjen van der Meer

sorry for the late reply but after further analysis, please, find below
now some additional comments from our experts:

The HTH file is missing in this ODF for MOS1 for some reason.
It's a housekeeping file reporting about the thresholds and pattern,
- always the same values - which seems rather useless, in the sense
that if it is not present it's not a problem apparently.
emchain can be run afterwards (just tested it)
and calibrated event files are created and further data processing can 
continue.

Cheers,
   Matthias

--
   Dr Matthias Ehle 
   XMM-Newton User Support Group
   European Space Astronomy Centre

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