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 Data/8851
Full headers

From: Cara Rakowski <rakowski@head-cfa.cfa.harvard.edu>
Subject: none
Compose reply
Download message
Move To:
2 replies: 1 2
2 followups: 1 2

Private message: yes  no

Notes:

Notification:


To: xmmhelp@xmm.vilspa.esa.es
Subject: 
Date: Fri, 25 Jul 2003 11:49:31 -0400
From: Cara Rakowski <rakowski@head-cfa.cfa.harvard.edu>
Dear User Support,

I am beginning to analyze the data from G337.2-0.7 (obsid
0087940101). The PN data (after reprocessing with epchain(default
parameters)) appear to only contain 26.8 seconds of exposure time. 
From epchain.log:

** epevents: warning (RangeStateVariable::set), The value 26.8913 for
variable `exposure duration' is not in the allowed range: 300 <= value
<= 156819

and indeed the P0087940101PNU002PIEVLI0000.FIT file made appears to be
that length.

The observation browser notes that there are problems with this
exposure. How can I find out what these problems are? Can I access the
rest of the exposure, assuming it was telemetered down?

Thank you,
Cara Rakowski


Reply 1

Resend
From: Matthias Ehle <xmmhelp@xmm.vilspa.esa.es>
To: rakowski@head-cfa.cfa.harvard.edu
Subject: Re: none (PR#8851)
Date: Fri Jul 25 16:31:45 2003
Dear Cara Rakowski,

I checked the data availble in the XMM-Newton Archive (XSA) for the
ObsID 0087940101:

There are in fact two pn exposures in extended full frame mode. These
are two unscheduled exposures U002 having 26s only (therefore no
producst here) but the other one, U003, has 29851s of observing time.

So, please, make sure that you are re-processing U003 with epchain 
or epproc. The fact that they are unscheduled means that they were
not executed from the timeline but had to be started manually. From
our log I see that there was a short problem with one of our ground 
stations.

Cheers,
Matthias.

Matthias Ehle 
XMM-Newton SOC 
User Support Group


Followup 1

Compose reply
Download message
To: Matthias Ehle <xmmhelp@xmm.vilspa.esa.es>
Subject: Re: none (PR#8851) 
Date: Fri, 25 Jul 2003 14:08:30 -0400
From: Cara Rakowski <rakowski@head-cfa.cfa.harvard.edu>
Dear Matthias Ehle,

Thank you! How do you access these exposures?  
I tried:
epchain exposure=U003 withbadpixfind=yes keepintermediate=none > &
epchain.log2 &

which wasn't accepted as a valid exposure, and
epchain exposure=003 withbadpixfind=yes keepintermediate=none > &
epchain.log2 &

that couldn't find the files in the odf,  though
SAS_ODF=/data/rakowski/g337xmm/0087940101/odf
was set and contains:

../0087940101/odf/0219_0087940101_PNU00300AUX.FIT
../0087940101/odf/0219_0087940101_PNU00301IME.FIT
../0087940101/odf/0219_0087940101_PNU00302IME.FIT
../0087940101/odf/0219_0087940101_PNU00303IME.FIT
../0087940101/odf/0219_0087940101_PNU00304IME.FIT
../0087940101/odf/0219_0087940101_PNU00304NOI.FIT
../0087940101/odf/0219_0087940101_PNU00305IME.FIT
../0087940101/odf/0219_0087940101_PNU00306IME.FIT
../0087940101/odf/0219_0087940101_PNU00307IME.FIT
../0087940101/odf/0219_0087940101_PNU00308IME.FIT
../0087940101/odf/0219_0087940101_PNU00309IME.FIT
../0087940101/odf/0219_0087940101_PNU00310IME.FIT
../0087940101/odf/0219_0087940101_PNU00311IME.FIT
../0087940101/odf/0219_0087940101_PNU00312IME.FIT

Suggestions?
Thank you!
Cara


> Dear Cara Rakowski,
> 
> I checked the data availble in the XMM-Newton Archive (XSA) for the
> ObsID 0087940101:
> 
> There are in fact two pn exposures in extended full frame mode. These
> are two unscheduled exposures U002 having 26s only (therefore no
> producst here) but the other one, U003, has 29851s of observing time.
> 
> So, please, make sure that you are re-processing U003 with epchain 
> or epproc. The fact that they are unscheduled means that they were
> not executed from the timeline but had to be started manually. From
> our log I see that there was a short problem with one of our ground 
> stations.
> 
> Cheers,
> Matthias.
> 
> Matthias Ehle 
> XMM-Newton SOC 
> User Support Group





Reply 2

Resend
From: Matthias Ehle <xmmhelp@xmm.vilspa.esa.es>
To: rakowski@head-cfa.cfa.harvard.edu
Subject: Re: none (PR#8851)
Date: Mon Jul 28 07:00:47 2003
Dear Cara,

to select the 2nd unscheduled pn exposure in your ODF, you need to execute

epchain schedule=U exposure=2

(For further details, please, check the epchain SAS task online documentation).

Kind regards,
Matthias.

 


Followup 2

Compose reply
Download message
To: Matthias Ehle <xmmhelp@xmm.vilspa.esa.es>
Subject: Re: none (PR#8851) 
Date: Mon, 28 Jul 2003 14:11:20 -0400
From: Cara Rakowski <rakowski@head-cfa.cfa.harvard.edu>
Thanks Matthias,
I would not have guessed that from the epchain or oal documentation.
Thank you again!
Cara

> Dear Cara,
> 
> to select the 2nd unscheduled pn exposure in your ODF, you need to execute
> 
> epchain schedule=U exposure=2
> 
> (For further details, please, check the epchain SAS task online
documentation
).
> 
> Kind regards,
> Matthias.
> 
>  




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