Up to top level
AO15   AO16   AO17   AO18   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   SciSim   Simulators_other   Suggestions   Trash   Visibility   XMM-bouncing   XMM-news   XRPS   XSA   esas   incoming  

Logged in as guest

Viewing SASv17.0/83919
Full headers

From: nrodd@berkeley.edu
Subject: Error running epchain on obsID=0690580101
Compose reply
Download message
Move To:
4 replies: 1 2 3 4
4 followups: 1 2 3 4

Private message: yes  no

Notes:

Notification:


Date: Thu, 6 Sep 2018 01:00:13 GMT
From: nrodd@berkeley.edu
To: xmmhelp@sciops.esa.int
CC: nrodd@berkeley.edu
Subject: Error running epchain on obsID=0690580101
Full_Name: Nick Rodd
Submission from: (NULL) (193.147.152.102)


Hello,

In order to process obsID=0690580101 I have been following the tutorial here:
https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html

When I got to the step "epchain withoutoftime=true" I received the following
error message:

*** Error in `epframes': corrupted size vs. prev_size: 0x000000000875a8f0 ***

with a lot of follow on, which I can provide if helpful. I've tried a few other
obsIDs but haven't experienced the same error.

Would you be able to explain to me what's going on here?

Thanks for your help,
Nick


Reply 1

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: nrodd@berkeley.edu
Subject: Re: Error running epchain on obsID=0690580101 (PR#83919)
Date: Thu Sep  6 12:55:49 2018
Dear Nick,

You probably used epchain without parameters, then it takes the first 
exposure available which in this case is 005. The exposure 005 failed and
was re-started with number 006. This can be seen in the observation 
log browser, and also in the XSA interface "Details" (magnifying 
glass besides the obsID):

..............

Anomalies derived from the science validation of PPS products:
==============================================================

XMM SSC data-product screening log
Version: 15-Mar-13
 
Revolution  2420
Obs Seq.    0690580101
Target      ESO 138-G1
Seq_id      075517
 
PCMS operator comment:
Ignored EPN exposure U005 due to failure in module pnEvents
Ignored dead MOS1 CCD#3 explicitly as SAS erroneously tries to analyse it
  SSC data-product screening log
Version: 15-Mar-13
 
Revolution  2420
Obs Seq.    0690580101
Target      ESO 138-G1
Seq_id      075517
 
PCMS operator comment:
Ignored EPN exposure U005 due to failure in module pnEvents
Ignored dead MOS1 CCD#3 explicitly as SAS erroneously tries to analyse it
 
....
etc

So please use:
                                                                                

epchain schedule=U odfaccess=odf exposure=6


Best regards,

Nora



> 
> In order to process obsID=0690580101 I have been following the tutorial
here:
> https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html
> 
> When I got to the step "epchain withoutoftime=true" I received the
following
> error message:
> 
> *** Error in `epframes': corrupted size vs. prev_size: 0x000000000875a8f0
***
> 
> with a lot of follow on, which I can provide if helpful. I've tried a few
other
> obsIDs but haven't experienced the same error.
> 
> Would you be able to explain to me what's going on here?
> 
> Thanks for your help,
> Nick
> 
> ----
Dr. Nora Loiseau
XMM-Newton User Support Group


Followup 1

Compose reply
Download message
From: Nicholas Rodd <nrodd@berkeley.edu>
Date: Thu, 6 Sep 2018 07:36:04 -0700
Subject: Re: Error running epchain on obsID=0690580101 (PR#83919)
To: xmmhelp@sciops.esa.int
--000000000000359cd3057534d0c3
Content-Type: text/plain; charset="UTF-8"

Hi Nora,

Thank you so much for this feedback. I have been trying to write a script
that can automatically go through as many of the details as possible here:
https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html

Given this, do you know of a way to test for this using the tools at the
command line?

Also given this issue wasn't mentioned in the cookbook, I was wondering it
you know of any alternative resources that describe the process of setting
up the data? I've also had a colleague tell me some additional tips that
are missing in that cookbook, e.g. he said I should be running "export
SAS_ODF=$(readlink -f *SUM.SAS)" after odfingest. This is my first foray
into XMM data, and I just want to safeguard as best as possible against
making an error in setting up the data.

Thanks again for your help,
Nick

On Thu, Sep 6, 2018 at 5:55 AM Nora Loiseau <xmmhelp@sciops.esa.int>
wrote:

> Dear Nick,
>
> You probably used epchain without parameters, then it takes the first
> exposure available which in this case is 005. The exposure 005 failed and
> was re-started with number 006. This can be seen in the observation
> log browser, and also in the XSA interface "Details" (magnifying
> glass besides the obsID):
>
> ..............
>
> Anomalies derived from the science validation of PPS products:
> ==============================================================
>
> XMM SSC data-product screening log
> Version: 15-Mar-13
>
> Revolution  2420
> Obs Seq.    0690580101
> Target      ESO 138-G1
> Seq_id      075517
>
> PCMS operator comment:
> Ignored EPN exposure U005 due to failure in module pnEvents
> Ignored dead MOS1 CCD#3 explicitly as SAS erroneously tries to analyse it
>   SSC data-product screening log
> Version: 15-Mar-13
>
> Revolution  2420
> Obs Seq.    0690580101
> Target      ESO 138-G1
> Seq_id      075517
>
> PCMS operator comment:
> Ignored EPN exposure U005 due to failure in module pnEvents
> Ignored dead MOS1 CCD#3 explicitly as SAS erroneously tries to analyse it
>
> ....
> etc
>
> So please use:
>
>
> epchain schedule=U odfaccess=odf exposure=6
>
>
> Best regards,
>
> Nora
>
>
>
> >
> > In order to process obsID=0690580101 I have been following the
tutorial
> here:
> > https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html
> >
> > When I got to the step "epchain withoutoftime=true" I received the
> following
> > error message:
> >
> > *** Error in `epframes': corrupted size vs. prev_size:
> 0x000000000875a8f0 ***
> >
> > with a lot of follow on, which I can provide if helpful. I've tried a
few
> other
> > obsIDs but haven't experienced the same error.
> >
> > Would you be able to explain to me what's going on here?
> >
> > Thanks for your help,
> > Nick
> >
> > ----
> Dr. Nora Loiseau
> XMM-Newton User Support Group
>
> This message is intended only for the recipient(s) named above. It may
> contain proprietary information and/or
> protected content. Any unauthorised disclosure, use, retention or
> dissemination is prohibited. If you have received
> this e-mail in error, please notify the sender immediately. ESA applies
> appropriate organisational measures to protect
> personal data, in case of data privacy queries, please contact the ESA
> Data Protection Officer (dpo@esa.int).
>
>
>

--000000000000359cd3057534d0c3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div
dir=3D"ltr">Hi Nora=
,<div><br></div><div>Thank you so much for this
feedback. I have been tryin=
g to write a script that can automatically go through as many of the detail=
s as possible here:=C2=A0<a href=3D"https://heasarc.gsfc.nasa.gov/docs/xmm/=
esas/cookbook/xmm-esas.html">https://heasarc.gsfc.nasa.gov/docs/xmm/esas/co=
okbook/xmm-esas.html</a><br><br>Given this, do you know of a
way to test fo=
r this using the tools at the command
line?</div><div><br></div><div>Also g=
iven this issue wasn&#39;t mentioned in the cookbook, I was wondering it yo=
u know of any alternative resources that describe the process of setting up=
 the data? I&#39;ve also had a colleague tell me some additional tips that =
are missing in that cookbook, e.g. he said I should be running &quot;export=
 SAS_ODF=3D$(readlink -f *SUM.SAS)&quot; after odfingest. This is my first =
foray into XMM data, and I just want to safeguard as best as possible again=
st making an error in setting up the
data.</div><div><br></div><di

Message of length 9213 truncated


Reply 2

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: nrodd@berkeley.edu
Subject: Re: Error running epchain on obsID=0690580101 (PR#83919)
Date: Thu Sep  6 16:11:12 2018
Hi Nick

With the task epproc, almost equal to epchain, you do not need to specify which

scheduled or unscheduled exposure you want to reduce, it does it for all of
them.

For general information on the tasks, parameters, etc., please check 
https://www.cosmos.esa.int/web/xmm-newton/sas
in particular:
https://www.cosmos.esa.int/web/xmm-newton/sas-threads
giving instructions since the SAS set-up up to the ESAS analysis.

Best regards,

Nora


> 
> Thank you so much for this feedback. I have been trying to write a script
> that can automatically go through as many of the details as possible here:
> https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html
> 
> Given this, do you know of a way to test for this using the tools at the
> command line?
> 
> Also given this issue wasn't mentioned in the cookbook, I was wondering it
> you know of any alternative resources that describe the process of setting
> up the data? I've also had a colleague tell me some additional tips that
> are missing in that cookbook, e.g. he said I should be running "export
> SAS_ODF=$(readlink -f *SUM.SAS)" after odfingest. This is my first foray
> into XMM data, and I just want to safeguard as best as possible against
> making an error in setting up the data.
> 
> Thanks again for your help,
> Nick
> 
> On Thu, Sep 6, 2018 at 5:55 AM Nora Loiseau <xmmhelp@sciops.esa.int>
wrote:
> 
>> Dear Nick,
>>
>> You probably used epchain without parameters, then it takes the first
>> exposure available which in this case is 005. The exposure 005 failed
and
>> was re-started with number 006. This can be seen in the observation
>> log browser, and also in the XSA interface "Details" (magnifying
>> glass besides the obsID):
>>
>> ..............
>>
>> Anomalies derived from the science validation of PPS products:
>> ==============================================================
>>
>> XMM SSC data-product screening log
>> Version: 15-Mar-13
>>
>> Revolution  2420
>> Obs Seq.    0690580101
>> Target      ESO 138-G1
>> Seq_id      075517
>>
>> PCMS operator comment:
>> Ignored EPN exposure U005 due to failure in module pnEvents
>> Ignored dead MOS1 CCD#3 explicitly as SAS erroneously tries to analyse
it
>>   SSC data-product screening log
>> Version: 15-Mar-13
>>
>> Revolution  2420
>> Obs Seq.    0690580101
>> Target      ESO 138-G1
>> Seq_id      075517
>>
>> PCMS operator comment:
>> Ignored EPN exposure U005 due to failure in module pnEvents
>> Ignored dead MOS1 CCD#3 explicitly as SAS erroneously tries to analyse
it
>>
>> ....
>> etc
>>
>> So please use:
>>
>>
>> epchain schedule=U odfaccess=odf exposure=6
>>
>>
>> Best regards,
>>
>> Nora
>>
>>
>>
>> >
>> > In order to process obsID=0690580101 I have been following the
tutorial
>> here:
>> > https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html
>> >
>> > When I got to the step "epchain withoutoftime=true" I received
the
>> following
>> > error message:
>> >
>> > *** Error in `epframes': corrupted size vs. prev_size:
>> 0x000000000875a8f0 ***
>> >
>> > with a lot of follow on, which I can provide if helpful. I've
tried a few
>> other
>> > obsIDs but haven't experienced the same error.
>> >
>> > Would you be able to explain to me what's going on here?
>> >
>> > Thanks for your help,
>> > Nick
>> >
>> > ----
>> Dr. Nora Loiseau
>> XMM-Newton User Support Group
>>
>> This message is intended only for the recipient(s) named above. It may
>> contain proprietary information and/or
>> protected content. Any unauthorised disclosure, use, retention or
>> dissemination is prohibited. If you have received
>> this e-mail in error, please notify the sender immediately. ESA
applies
>> appropriate organisational measures to protect
>> personal data, in case of data privacy queries, please contact the ESA
>> Data Protection Officer (dpo@esa.int).
>>
>>
>>
> 
> --000000000000359cd3057534d0c3
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
> 
> <div dir=3D"ltr"><div dir=3D"ltr"><div
dir=3D"ltr"><div dir=3D"ltr">Hi Nora=
> ,<div><br></div><div>Thank you so much for this
feedback. I have been tryin=
> g to write a script th

Message of length 10768 truncated


Followup 2

Compose reply
Download message
From: Nicholas Rodd <nrodd@berkeley.edu>
Date: Thu, 6 Sep 2018 09:38:59 -0700
Subject: Re: Error running epchain on obsID=0690580101 (PR#83919)
To: xmmhelp@sciops.esa.int
--000000000000c6c8620575368754
Content-Type: text/plain; charset="UTF-8"

Hi Nora,

That's fantastic, thanks so much.

To clarify one other issue I had in looking into the data for this
observation. The PN U005 exposure is missing, which makes perfect sense
given what you said. However, it looks like the MOS1S001 and MOS2S002
exposures are also missing, but the MOS analysis steps seem to run without
ever complaining! I am able to run through the commands: emchain >
mos-filter > cheese > mos-spectra > mos_back, without an error despite
these missing files. Do you know what the reason for this is?

Thanks again,
Nick

On Thu, Sep 6, 2018 at 9:11 AM Nora Loiseau <xmmhelp@sciops.esa.int>
wrote:

> Hi Nick
>
> With the task epproc, almost equal to epchain, you do not need to specify
> which
>
> scheduled or unscheduled exposure you want to reduce, it does it for all of
> them.
>
> For general information on the tasks, parameters, etc., please check
> https://www.cosmos.esa.int/web/xmm-newton/sas
> in particular:
> https://www.cosmos.esa.int/web/xmm-newton/sas-threads
> giving instructions since the SAS set-up up to the ESAS analysis.
>
> Best regards,
>
> Nora
>
>
> >
> > Thank you so much for this feedback. I have been trying to write a
script
> > that can automatically go through as many of the details as possible
> here:
> > https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html
> >
> > Given this, do you know of a way to test for this using the tools at
the
> > command line?
> >
> > Also given this issue wasn't mentioned in the cookbook, I was
wondering
> it
> > you know of any alternative resources that describe the process of
> setting
> > up the data? I've also had a colleague tell me some additional tips
that
> > are missing in that cookbook, e.g. he said I should be running "export
> > SAS_ODF=$(readlink -f *SUM.SAS)" after odfingest. This is my first
foray
> > into XMM data, and I just want to safeguard as best as possible
against
> > making an error in setting up the data.
> >
> > Thanks again for your help,
> > Nick
> >
> > On Thu, Sep 6, 2018 at 5:55 AM Nora Loiseau
<xmmhelp@sciops.esa.int>
> wrote:
> >
> >> Dear Nick,
> >>
> >> You probably used epchain without parameters, then it takes the
first
> >> exposure available which in this case is 005. The exposure 005
failed
> and
> >> was re-started with number 006. This can be seen in the
observation
> >> log browser, and also in the XSA interface "Details" (magnifying
> >> glass besides the obsID):
> >>
> >> ..............
> >>
> >> Anomalies derived from the science validation of PPS products:
> >> ==============================================================
> >>
> >> XMM SSC data-product screening log
> >> Version: 15-Mar-13
> >>
> >> Revolution  2420
> >> Obs Seq.    0690580101
> >> Target      ESO 138-G1
> >> Seq_id      075517
> >>
> >> PCMS operator comment:
> >> Ignored EPN exposure U005 due to failure in module pnEvents
> >> Ignored dead MOS1 CCD#3 explicitly as SAS erroneously tries to
analyse
> it
> >>   SSC data-product screening log
> >> Version: 15-Mar-13
> >>
> >> Revolution  2420
> >> Obs Seq.    0690580101
> >> Target      ESO 138-G1
> >> Seq_id      075517
> >>
> >> PCMS operator comment:
> >> Ignored EPN exposure U005 due to failure in module pnEvents
> >> Ignored dead MOS1 CCD#3 explicitly as SAS erroneously tries to
analyse
> it
> >>
> >> ....
> >> etc
> >>
> >> So please use:
> >>
> >>
> >> epchain schedule=U odfaccess=odf exposure=6
> >>
> >>
> >> Best regards,
> >>
> >> Nora
> >>
> >>
> >>
> >> >
> >> > In order to process obsID=0690580101 I have been following
the
> tutorial
> >> here:
> >> > https://heasarc.gsfc.nasa.gov/docs/xmm/esas/cookbook/xmm-esas.html
> >> >
> >> > When I got to the step "epchain withoutoftime=true" I
received the
> >> following
> >> > error message:
> >> >
> >> > *** Error in `epframes': corrupted size vs. prev_size:
> >> 0x000000000875a8f0 ***
> >> >
> >> > with a lot of follow on, which I can provide if helpful. I've
tried a
> few
> >> other
> >> > obsIDs but haven't experienced the same error.
> >> >
> >> > Would you 

Message of length 33372 truncated


Reply 3

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: nrodd@berkeley.edu
Subject: Re: Error running epchain on obsID=0690580101 (PR#83919)
Date: Thu Sep  6 18:08:37 2018
Hi Nick,
> 
> To clarify one other issue I had in looking into the data for this
> observation. The PN U005 exposure is missing, which makes perfect sense
> given what you said. However, it looks like the MOS1S001 and MOS2S002
> exposures are also missing, but the MOS analysis steps seem to run without
> ever complaining! I am able to run through the commands: emchain >
> mos-filter > cheese > mos-spectra > mos_back, without an error
despite
> these missing files. Do you know what the reason for this is?

The tasks are slightly different. Anyway we will try to include a comment in 
the description and threads.

Best,

Nora
----
Dr. Nora Loiseau
XMM-Newton User Support Group


Followup 3

Compose reply
Download message
From: Nicholas Rodd <nrodd@berkeley.edu>
Date: Thu, 6 Sep 2018 11:31:43 -0700
Subject: Re: Error running epchain on obsID=0690580101 (PR#83919)
To: xmmhelp@sciops.esa.int
--000000000000f5faa70575381a4d
Content-Type: text/plain; charset="UTF-8"

Hi Nora,

To clarify, is there an issue on the MOS side here that I should worry
about given the missing files?

Best,
Nick

On Thu, Sep 6, 2018 at 11:08 AM Nora Loiseau <xmmhelp@sciops.esa.int>
wrote:

> Hi Nick,
> >
> > To clarify one other issue I had in looking into the data for this
> > observation. The PN U005 exposure is missing, which makes perfect
sense
> > given what you said. However, it looks like the MOS1S001 and MOS2S002
> > exposures are also missing, but the MOS analysis steps seem to run
> without
> > ever complaining! I am able to run through the commands: emchain >
> > mos-filter > cheese > mos-spectra > mos_back, without an
error despite
> > these missing files. Do you know what the reason for this is?
>
> The tasks are slightly different. Anyway we will try to include a comment
> in
> the description and threads.
>
> Best,
>
> Nora
> ----
> Dr. Nora Loiseau
> XMM-Newton User Support Group
>
> This message is intended only for the recipient(s) named above. It may
> contain proprietary information and/or
> protected content. Any unauthorised disclosure, use, retention or
> dissemination is prohibited. If you have received
> this e-mail in error, please notify the sender immediately. ESA applies
> appropriate organisational measures to protect
> personal data, in case of data privacy queries, please contact the ESA
> Data Protection Officer (dpo@esa.int).
>
>
>

--000000000000f5faa70575381a4d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Nora,<div><br></div><div>To
clarify, is there an issue =
on the MOS side here that I should worry about given the missing files?</di=
v><div><br></div><div>Best,</div><div>Nick</div></div><br><div
class=3D"gma=
il_quote"><div dir=3D"ltr">On Thu, Sep 6, 2018 at 11:08 AM Nora Loiseau
&lt=
;<a href=3D"mailto:xmmhelp@sciops.esa.int">xmmhelp@sciops.esa.int</a>&gt;
w=
rote:<br></div><blockquote class=3D"gmail_quote"
style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Hi Nick,<br>
&gt; <br>
&gt; To clarify one other issue I had in looking into the data for
this<br>
&gt; observation. The PN U005 exposure is missing, which makes perfect sens=
e<br>
&gt; given what you said. However, it looks like the MOS1S001 and
MOS2S002<=
br>
&gt; exposures are also missing, but the MOS analysis steps seem to run wit=
hout<br>
&gt; ever complaining! I am able to run through the commands: emchain
&gt;<=
br>
&gt; mos-filter &gt; cheese &gt; mos-spectra &gt; mos_back,
without an erro=
r despite<br>
&gt; these missing files. Do you know what the reason for this is?<br>
<br>
The tasks are slightly different. Anyway we will try to include a comment i=
n <br>
the description and threads.<br>
<br>
Best,<br>
<br>
Nora<br>
----<br>
Dr. Nora Loiseau<br>
XMM-Newton User Support Group<br>
<br>
This message is intended only for the recipient(s) named above. It may cont=
ain proprietary information and/or<br>
protected content. Any unauthorised disclosure, use, retention or dissemina=
tion is prohibited. If you have received<br>
this e-mail in error, please notify the sender immediately. ESA applies app=
ropriate organisational measures to protect<br>
personal data, in case of data privacy queries, please contact the ESA Data=
 Protection Officer (<a href=3D"mailto:dpo@esa.int"
target=3D"_blank">dpo@e=
sa.int</a>).<br>
<br>
<br>
</blockquote></div>

--000000000000f5faa70575381a4d--



Followup 4

Compose reply
Download message
From: Nicholas Rodd <nrodd@berkeley.edu>
Date: Thu, 6 Sep 2018 15:02:31 -0700
Subject: Re: Error running epchain on obsID=0690580101 (PR#83919)
To: xmmhelp@sciops.esa.int
--000000000000da7ac105753b0cd8
Content-Type: text/plain; charset="UTF-8"

Hi Nora,

I've been spending some more time digging into this same issue. In addition
to remaining confused about the above point, I'm not also confused about
the following:

   - So I tried to rerun this using epproc instead of epchain, and it spat
   the same error, it didn't skip over the bad observation. Is the idea that I
   should just ignore the error in this place and assume the exposures it has
   processed were done correctly?
   - Going back to epchain, you mentioned running with exposure=6, but this
   crashed. I checked the documentation and it suggests using exposure=2,
   which ran. Was this just a typo, or am I possibly missing something here?
   - Also in your suggested epchain command you added the keyword
   "schedule" and set this = U (for unscheduled I think). In the cookbook it
   mentions the distinction is unimportant, I just want to check why did you
   specify this? As it defaults to S, if I had not included that keyword would
   an error be introduced in the processing?
   - In addition you changed the default odfaccess to odf (which I think is
   a prerequisite for the schedule keyword being read). I haven't been able to
   find any documentation regarding when to use this keyword, could you give
   me some insight as to when I should be appending it?

Sorry to bombard you with all these questions, as I mentioned I'm new to
this dataset and really want to make sure I don't misuse it. I very much
appreciate your assistance.

Best,
Nick

On Thu, Sep 6, 2018 at 11:31 AM Nicholas Rodd <nrodd@berkeley.edu> wrote:

> Hi Nora,
>
> To clarify, is there an issue on the MOS side here that I should worry
> about given the missing files?
>
> Best,
> Nick
>
> On Thu, Sep 6, 2018 at 11:08 AM Nora Loiseau <xmmhelp@sciops.esa.int>
> wrote:
>
>> Hi Nick,
>> >
>> > To clarify one other issue I had in looking into the data for this
>> > observation. The PN U005 exposure is missing, which makes perfect
sense
>> > given what you said. However, it looks like the MOS1S001 and
MOS2S002
>> > exposures are also missing, but the MOS analysis steps seem to run
>> without
>> > ever complaining! I am able to run through the commands: emchain
>
>> > mos-filter > cheese > mos-spectra > mos_back, without an
error despite
>> > these missing files. Do you know what the reason for this is?
>>
>> The tasks are slightly different. Anyway we will try to include a
comment
>> in
>> the description and threads.
>>
>> Best,
>>
>> Nora
>> ----
>> Dr. Nora Loiseau
>> XMM-Newton User Support Group
>>
>> This message is intended only for the recipient(s) named above. It may
>> contain proprietary information and/or
>> protected content. Any unauthorised disclosure, use, retention or
>> dissemination is prohibited. If you have received
>> this e-mail in error, please notify the sender immediately. ESA applies
>> appropriate organisational measures to protect
>> personal data, in case of data privacy queries, please contact the ESA
>> Data Protection Officer (dpo@esa.int).
>>
>>
>>

--000000000000da7ac105753b0cd8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div
dir=3D"ltr">Hi Nora=
,<div><br></div><div>I&#39;ve been spending some
more time digging into thi=
s same issue. In addition to remaining confused about the above point, I&#3=
9;m not also confused about the
following:</div><div><ul><li>So I tried to =
rerun this using=C2=A0epproc instead of epchain, and it spat the same error=
, it didn&#39;t skip over the bad observation. Is the idea that I should ju=
st ignore the error in this place and assume the exposures it has processed=
 were done correctly?</li><li>Going back to epchain, you mentioned
running =
with exposure=3D6, but this crashed. I checked the documentation and it sug=
gests using exposure=3D2, which ran. Was this just a typo, or am I possibly=
 missing something here?</li><li>Also in your suggested epchain
command you=
 added the keyword &quot;schedule&quot; and set this =3D U (for
unscheduled=
 I think). In the cookbook it mentions the distinction is unimportant, I ju=
st want to check why did you specify this? As it defaults to S, if I had no=
t included that keyword would an error be introduced in the processing?</li=
><li>In addition you changed the default odfaccess to odf (which I
think is=
 a prerequisite for the schedule keyword being read). I haven&#39;t been ab=
le to find any documentation regarding when to use this keyword, could y

Message of length 8140 truncated


Reply 4

Resend
From: Nora Loiseau <xmmhelp@sciops.esa.int>
To: nrodd@berkeley.edu
Subject: Re: Error running epchain on obsID=0690580101 (PR#83919)
Date: Fri Sep  7 16:29:38 2018
Hi Nick,

Sometimes the ODF produces some files from corrupted or not much 
useful exposures, like PN U005, probably nothing was produced for 
MOS1S001 and MOS2S002. In any case you can specify which one 
you want to analyze, or let the task analyze all what it can. But 
afterwards some kind of screening of the results is needed.
> 
>    - So I tried to rerun this using epproc instead of epchain, and it spat
>    the same error, it didn't skip over the bad observation. Is the idea
that
I
>    should just ignore the error in this place and assume the exposures it
has
>    processed were done correctly?
>    - Going back to epchain, you mentioned running with exposure=6, but
this
>    crashed. I checked the documentation and it suggests using exposure=2,
>    which ran. Was this just a typo, or am I possibly missing something
here?
Is OK if it is giving you results on the desired PN exposure, these parameters 
inputs change sometimes, so it is only necessary to check a bit.

>    - Also in your suggested epchain command you added the keyword
>    "schedule" and set this = U (for unscheduled I think). In the cookbook
it
>    mentions the distinction is unimportant, I just want to check why did
you
>    specify this? As it defaults to S, if I had not included that keyword
would
>    an error be introduced in the processing?
Again there will be no error, it only might be needed to specify in some 
cases, but if it runs without this parameter there is no problem.

>    - In addition you changed the default odfaccess to odf (which I think
is
>    a prerequisite for the schedule keyword being read). I haven't been able
to
>    find any documentation regarding when to use this keyword, could you
give
>    me some insight as to when I should be appending it?
It is not needed.

Best regards,

Nora

----
Dr. Nora Loiseau
XMM-Newton User Support Group

Up to top level
AO15   AO16   AO17   AO18   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   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