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

From: Gayoung Chon <gchon@mpe.mpg.de>
Subject: PN data
Compose reply
Download message
Move To:
4 replies: 1 2 3 4
2 followups: 1 2

Private message: yes  no

Notes:

Notification:


Date: Fri, 02 Sep 2011 11:03:55 +0200
From: Gayoung Chon <gchon@mpe.mpg.de>
To: xmmhelp@sciops.esa.int
Subject: PN data
Dear Helpdesk,

I am looking at the observation, 0098010101,
and have a question on the extracted event files.

After the emchain and epchain runs, two types of files
are produced, S for CalClosed and U for the actual
observation in case of MOS. PN event files are produced
only with CalClosed which has S not U in the filename.
In the archived PN image it indicates that it is produced
from U, which I can not extract by epchain.

Could you please check if this is the case ?
I am simply running emchain and epchain to produce
event files.

best wishes, Gayoung


Reply 1

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: gchon@mpe.mpg.de
Subject: Re: PN data (PR#48528)
Date: Fri Sep  2 09:57:31 2011
Dear Gayoung,

 we will be testing whether the science file of pn can be produced with epchain.
In the mean time, for your science analysis, perhaps the pn events file that is
in the PPS could be useful. We will come back to you with the results of further
checks.

 Best regards,
Jan-Uwe

--
Dr. Jan-Uwe Ness
XMM-Newton Science Operations Centre


> Dear Helpdesk,
> 
> I am looking at the observation, 0098010101,
> and have a question on the extracted event files.
> 
> After the emchain and epchain runs, two types of files
> are produced, S for CalClosed and U for the actual
> observation in case of MOS. PN event files are produced
> only with CalClosed which has S not U in the filename.
> In the archived PN image it indicates that it is produced
> from U, which I can not extract by epchain.
> 
> Could you please check if this is the case ?
> I am simply running emchain and epchain to produce
> event files.
> 
> best wishes, Gayoung
> 
> 


Reply 2

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: gchon@mpe.mpg.de
Subject: Re: PN data (PR#48528)
Date: Fri Sep  2 11:54:04 2011
Dear Gayoung,

 as already reported, there is a pn science exposure present in the observation
you are looking at, and the PPS products contain an events file. I have now done
a full extraction of ObsID 0098010101 and was able to extract all products
including the pn events file with U in the file name. If have used the new tool
xmmextractor for testing. It does not only produce events files but also
extracts spectra and light curves. These are all fine for the pn as well.

 Perhaps you are interested in trying xmmextractor, for which you can find some
documentation under
http://xmm.esac.esa.int/sas/current/documentation/threads/xmmextractor.shtml

 If you wish, we can also try and find out what may be missing in your setup,
directory structure, or command line call. For a more detailed analysis, I would
need from you the two log files produced in the following way:
  sasversion >& mysassetup.log
  env >>& mysassetup.log
  epproc -V 5 >& epproc.log
to be called after initializing the SAS following the thread:
http://xmm.esac.esa.int/sas/current/documentation/threads/sas_startup_thread.shtml

 Please let us know if we can help with anything else.
Best regards,
Jan-Uwe


> Dear Helpdesk,
> 
> I am looking at the observation, 0098010101,
> and have a question on the extracted event files.
> 
> After the emchain and epchain runs, two types of files
> are produced, S for CalClosed and U for the actual
> observation in case of MOS. PN event files are produced
> only with CalClosed which has S not U in the filename.
> In the archived PN image it indicates that it is produced
> from U, which I can not extract by epchain.
> 
> Could you please check if this is the case ?
> I am simply running emchain and epchain to produce
> event files.
> 
> best wishes, Gayoung
> 
> 


Followup 1

Compose reply
Download message
Date: Tue, 06 Sep 2011 15:25:38 +0200
From: Gayoung Chon <gchon@mpe.mpg.de>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: PN data (PR#48528)
This is a multi-part message in MIME format.
--------------050301050208000503040304
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear Jan-Uwe,

Thank you for your investigation.

An extraction run with epchain does not produce the desired results
unlike the run with epproc from my side. As far as I can see this is the
first set of data that produces different results from two reduction
schemes. Up to now I have been using epchain and emchain to process
data. I attach both log files for your comparison.

There are a couple of questions remaining, the first being the reason
why epchain fails, and what is special with this dataset especially for
epchain (given emchain does run and produces two set of S and U files).
Given that I will use epproc for this data, if running
     epproc withoutoftime=Y
will produce the same product as
     epchain runbackground=N keepintermediate=raw withoutoftime=Y
since I could not find runbackground option with epproc in the manual.

best wishes, Gayoung


On 09/02/11 13:54, Jan-Uwe Ness wrote:
> Dear Gayoung,
>
>   as already reported, there is a pn science exposure present in the
observation
> you are looking at, and the PPS products contain an events file. I have now
done
> a full extraction of ObsID 0098010101 and was able to extract all products
> including the pn events file with U in the file name. If have used the new
tool
> xmmextractor for testing. It does not only produce events files but also
> extracts spectra and light curves. These are all fine for the pn as well.
>
>   Perhaps you are interested in trying xmmextractor, for which you can find
some
> documentation under
> http://xmm.esac.esa.int/sas/current/documentation/threads/xmmextractor.shtml
>
>   If you wish, we can also try and find out what may be missing in your
setup,
> directory structure, or command line call. For a more detailed analysis, I
would
> need from you the two log files produced in the following way:
>    sasversion>&  mysassetup.log
>    env>>&  mysassetup.log
>    epproc -V 5>&  epproc.log
> to be called after initializing the SAS following the thread:
> http://xmm.esac.esa.int/sas/current/documentation/threads/sas_startup_thread.shtml
>
>   Please let us know if we can help with anything else.
> Best regards,
> Jan-Uwe
>
>
>> Dear Helpdesk,
>>
>> I am looking at the observation, 0098010101,
>> and have a question on the extracted event files.
>>
>> After the emchain and epchain runs, two types of files
>> are produced, S for CalClosed and U for the actual
>> observation in case of MOS. PN event files are produced
>> only with CalClosed which has S not U in the filename.
>> In the archived PN image it indicates that it is produced
>> from U, which I can not extract by epchain.
>>
>> Could you please check if this is the case ?
>> I am simply running emchain and epchain to produce
>> event files.
>>
>> best wishes, Gayoung
>>
>>
> ================================================================================================
> This message and any attachments are intended for the use of the addressee
or addressees only. The unauthorised disclosure,
>
> use, dissemination or copying (either in whole or in part) of its content
is not permitted. If you received this message in
>
> error, please notify the sender and delete it from your system. Emails can
be altered and their integrity cannot be guaranteed by
>
> the sender.
>
> Please consider the environment before printing this email.
> =================================================================================================
>


--------------050301050208000503040304
Content-Type: text/plain;
 name="epchain.log"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="epchain.log"

EXPOSURE =3D 1
/home/gchon/data1/locuss/locuss12/Abell1835/ODF/0101_0098010101_PNS01001I=
ME.FIT
-:- CMD: badpixfind eventset=3Drawevents01.dat badpixset=3DP0098010101PNS=
010BPXFLI0001.FIT hithresh=3D0.0045 hicolthresh=3D0.00105 backgroundrate=3D=
0.00011 loenergythresh=3D0.14 hienergythresh=3D12.0 narrowerthanpsf=3D1.5=
 withsearchbadcolumn=3Dy thresholdlabel=3Drate  -w 10
badpixfind:- Executing (routine): badpixfind eventset=3Drawevents01.dat l=
othresh=3D0 hithresh=3D0.0045 searchbadpix=3Dyes columnsearchlabel=3Dmedi=
an locolthresh=3D0 hicolthresh=3D0.00105 withsearchbadcolumn=3Dyes rawxli=
st=3D'' rawylist=3D'' typelist=3D'' yextentlist=3D'' userflagbadpix=3Dno =
thresholdlabel=3Drate flickertimesteps=3D1 flickerksthresh=3D0.55 flicker=
chisqthresh=3D15 cellsize=3D2 backgroundrate=3D0.00011 narrowerthanpsf=3D=
1.5 badpixset=3DP0098010101PNS010BPXFLI0001.FIT badpixmap=3Dbadpixmap.fit=
s withbadpixmap=3Dno withfovmask=3Dno 

Message of length 2494082 truncated


Reply 3

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: gchon@mpe.mpg.de
Subject: Re: PN data (PR#48528)
Date: Wed Sep  7 07:55:29 2011
Dear Gayoung,

 I have tried the same calls and found that without OoT correction, I get a
clean events file also with epproc. But that is not acceptable, and I have
forwarded your log files and descriptions to the developers to have a closer
look. I will keep you posted of their results.

 Regards,
Jan-Uwe


> Dear Jan-Uwe,
>
> Thank you for your investigation.
>
> An extraction run with epchain does not produce the desired results
> unlike the run with epproc from my side. As far as I can see this is the
> first set of data that produces different results from two reduction
> schemes. Up to now I have been using epchain and emchain to process
> data. I attach both log files for your comparison.
>
> There are a couple of questions remaining, the first being the reason
> why epchain fails, and what is special with this dataset especially for
> epchain (given emchain does run and produces two set of S and U files).
> Given that I will use epproc for this data, if running
>      epproc withoutoftime=Y
> will produce the same product as
>      epchain runbackground=N keepintermediate=raw withoutoftime=Y
> since I could not find runbackground option with epproc in the manual.
>
> best wishes, Gayoung


Reply 4

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: gchon@mpe.mpg.de
Subject: Re: PN data (PR#48528)
Date: Mon Jan 16 09:42:13 2012
Dear Gayoung,

 investigations on the problem with epchain versus epproc for ObsID 0098010101
are still continuing. This observation contains two exposures for each EPIC
instrument, one in CAL CLOSED (exposure S010) and one in thin filter (U002). You
reported that with epchain, only S010 is processed but not U002. We have been
able to reproduce this problem, and the SAS team has been notified to
investigate why not both exposures are handled with epchain. Depending on the
complexity of the problem, it will be fixed in a future SAS version.

 From what has been exchanged, it seems that you have everything you need for
the moment using epproc. In addition, we inform you that you can process
exposure U002 with epchain using the option exposure=2 in the call, thus:
    epchain runbackground=N keepintermediate=raw withoutoftime=Y exposure=2
It is a workaround for this special case and, combined with epproc, hopefully
for the moment sufficient. Please let us know if not.

 The reason the option runbackground=N is not offered in epproc is that epproc
does not produce any background or lightcurve file.

 Unless we hear more from you, I will close the ticket. For new questions,
please raise a new helpticket.

 Best regards,
Jan-Uwe



> Dear Jan-Uwe,
> 
> Thank you for your investigation.
> 
> An extraction run with epchain does not produce the desired results
> unlike the run with epproc from my side. As far as I can see this is the
> first set of data that produces different results from two reduction
> schemes. Up to now I have been using epchain and emchain to process
> data. I attach both log files for your comparison.
> 
> There are a couple of questions remaining, the first being the reason
> why epchain fails, and what is special with this dataset especially for
> epchain (given emchain does run and produces two set of S and U files).
> Given that I will use epproc for this data, if running
>      epproc withoutoftime=Y
> will produce the same product as
>      epchain runbackground=N keepintermediate=raw withoutoftime=Y
> since I could not find runbackground option with epproc in the manual.
> 
> best wishes, Gayoung
> 
> 
> On 09/02/11 13:54, Jan-Uwe Ness wrote:
>> Dear Gayoung,
>>
>>   as already reported, there is a pn science exposure present in the
> observation
>> you are looking at, and the PPS products contain an events file. I have
now
> done
>> a full extraction of ObsID 0098010101 and was able to extract all
products
>> including the pn events file with U in the file name. If have used the
new
> tool
>> xmmextractor for testing. It does not only produce events files but
also
>> extracts spectra and light curves. These are all fine for the pn as
well.
>>
>>   Perhaps you are interested in trying xmmextractor, for which you can
find
> some
>> documentation under
>> http://xmm.esac.esa.int/sas/current/documentation/threads/xmmextractor.shtml
>>
>>   If you wish, we can also try and find out what may be missing in your
setup,
>> directory structure, or command line call. For a more detailed
analysis, I
> would
>> need from you the two log files produced in the following way:
>>    sasversion>&  mysassetup.log
>>    env>>&  mysassetup.log
>>    epproc -V 5>&  epproc.log
>> to be called after initializing the SAS following the thread:
>> http://xmm.esac.esa.int/sas/current/documentation/threads/sas_startup_thread.shtml
>>
>>   Please let us know if we can help with anything else.
>> Best regards,
>> Jan-Uwe
>>
>>
>>> Dear Helpdesk,
>>>
>>> I am looking at the observation, 0098010101,
>>> and have a question on the extracted event files.
>>>
>>> After the emchain and epchain runs, two types of files
>>> are produced, S for CalClosed and U for the actual
>>> observation in case of MOS. PN event files are produced
>>> only with CalClosed which has S not U in the filename.
>>> In the archived PN image it indicates that it is produced
>>> from U, which I can not extract by epchain.
>>>
>>> Could you please check if this is the case ?
>>> I am simply running emchain and epchain to produce
>>> event files.
>>>
>>> best wishes, Gayoung


Followup 2

Compose reply
Download message
Date: Mon, 16 Jan 2012 11:47:24 +0100
From: Gayoung Chon <gchon@mpe.mpg.de>
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
Subject: Re: PN data (PR#48528)
Dear Jan-Uwe,

thank you for the follow-up, and other suggestions.
Please close the ticket.

best wishes, Gayoung


On 01/16/2012 10:42 AM, Jan-Uwe Ness wrote:
> Dear Gayoung,
>
>   investigations on the problem with epchain versus epproc for ObsID
0098010101
> are still continuing. This observation contains two exposures for each EPIC
> instrument, one in CAL CLOSED (exposure S010) and one in thin filter
(U002). You
> reported that with epchain, only S010 is processed but not U002. We have
been
> able to reproduce this problem, and the SAS team has been notified to
> investigate why not both exposures are handled with epchain. Depending on
the
> complexity of the problem, it will be fixed in a future SAS version.
>
>   From what has been exchanged, it seems that you have everything you need
for
> the moment using epproc. In addition, we inform you that you can process
> exposure U002 with epchain using the option exposure=2 in the call, thus:
>      epchain runbackground=N keepintermediate=raw withoutoftime=Y
exposure=2
> It is a workaround for this special case and, combined with epproc,
hopefully
> for the moment sufficient. Please let us know if not.
>
>   The reason the option runbackground=N is not offered in epproc is that
epproc
> does not produce any background or lightcurve file.
>
>   Unless we hear more from you, I will close the ticket. For new questions,
> please raise a new helpticket.
>
>   Best regards,
> Jan-Uwe
>
>
>
>> Dear Jan-Uwe,
>>
>> Thank you for your investigation.
>>
>> An extraction run with epchain does not produce the desired results
>> unlike the run with epproc from my side. As far as I can see this is
the
>> first set of data that produces different results from two reduction
>> schemes. Up to now I have been using epchain and emchain to process
>> data. I attach both log files for your comparison.
>>
>> There are a couple of questions remaining, the first being the reason
>> why epchain fails, and what is special with this dataset especially for
>> epchain (given emchain does run and produces two set of S and U files).
>> Given that I will use epproc for this data, if running
>>       epproc withoutoftime=Y
>> will produce the same product as
>>       epchain runbackground=N keepintermediate=raw withoutoftime=Y
>> since I could not find runbackground option with epproc in the manual.
>>
>> best wishes, Gayoung
>>
>>
>> On 09/02/11 13:54, Jan-Uwe Ness wrote:
>>> Dear Gayoung,
>>>
>>>    as already reported, there is a pn science exposure present in
the
>> observation
>>> you are looking at, and the PPS products contain an events file. I
have now
>> done
>>> a full extraction of ObsID 0098010101 and was able to extract all
products
>>> including the pn events file with U in the file name. If have used
the new
>> tool
>>> xmmextractor for testing. It does not only produce events files but
also
>>> extracts spectra and light curves. These are all fine for the pn as
well.
>>>
>>>    Perhaps you are interested in trying xmmextractor, for which you
can find
>> some
>>> documentation under
>>> http://xmm.esac.esa.int/sas/current/documentation/threads/xmmextractor.shtml
>>>
>>>    If you wish, we can also try and find out what may be missing in
your
> setup,
>>> directory structure, or command line call. For a more detailed
analysis, I
>> would
>>> need from you the two log files produced in the following way:
>>>     sasversion>&   mysassetup.log
>>>     env>>&   mysassetup.log
>>>     epproc -V 5>&   epproc.log
>>> to be called after initializing the SAS following the thread:
>>> http://xmm.esac.esa.int/sas/current/documentation/threads/sas_startup_thread.shtml
>>>
>>>    Please let us know if we can help with anything else.
>>> Best regards,
>>> Jan-Uwe
>>>
>>>
>>>> Dear Helpdesk,
>>>>
>>>> I am looking at the observation, 0098010101,
>>>> and have a question on the extracted event files.
>>>>
>>>> After the emchain and epchain runs, two types of files
>>>> are produced, S for CalClosed and U for the actual
>>>> observation in case of MOS. PN event files are produced
>>>> only with CalClosed which has S not U in the filename.
>>>> In the archived PN image it indicates that it is produced
>>>> from U, which I can not extract by epchain.
>>>>
>>>> Could you please check if this is the case ?
>>>> I am si

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