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 Pending/84888
Full headers

From: jjung11@alaska.edu
Subject: Using epiclccorr for extended source lightcurve
Compose reply
Download message
Move To:
2 replies: 1 2
1 followups: 1

Private message: yes  no

Notes:

Notification:


Date: Tue, 23 Apr 2019 04:12:06 +0200
From: jjung11@alaska.edu
To: xmmhelp@sciops.esa.int
Subject: Using epiclccorr for extended source lightcurve
Full_Name: Jaewoong Jung
Submission from: (NULL) (193.147.152.102)


Dear XMM helpdesk team,

I'm studying a magnetosheath SWCX signal from XMM data. So after filtering
soft-proton flare, removing other things like point sources, I made a light
curve from very large region ((detx,dety) in circle (0,0,16000)) using
evselect.
However, resultant light curve had unnatural zig-zag pattern, and I thought it
is due to effect of GTI included. I'm trying to correct light curve following
this article, 
https://www.cosmos.esa.int/web/xmm-newton/sas-thread-timing
But the fact that article explicitly states that it's for point source light
curve worries me. 

I'm trying to use following command,

epiclccorr srctslist=MOS1cleanf.lc eventlist=MOS1cleanf.fits
outset=MOS1_lccorr.lc applyabsolutecorrections=yes

Here MOS1cleanf.lc is the lightcurve generated from evselect, MOS1cleanf.fits is
the event file after soft proton filtering and point sources removed.

I'm not including background lightcurve because I'm doing magnetosheath
background study, and I already found out the value of other background
(particle, astrophysical, heliospheric) from spectral analysis. I'll subtract it
from my light curve later to get the final light curve.

I'm not sure whether I should use absolute/relative correction . After reading
epiclccorr document, it looks like relative correction is for my job, but then
are vignetting, bad pixels not corrected? I couldn't find subroutines of
epiclccorr so I couldn't analyze each of them separately.

Actually I tried that command and resultant curve looked better than the
not-corrected one, but I'm not sure whether it is done correctly. 

Can you give me your advice whether epiclccorr will works for my job please?

Thanks,
Jaewoong


Reply 1

Resend
From: Simone Migliari <xmmhelp@sciops.esa.int>
To: jjung11@alaska.edu
Subject: Re: Using epiclccorr for extended source lightcurve (PR#84888)
Date: Thu Apr 25 10:58:46 2019
Dear Jaewoong Jung

apologies for the late reply. 

As a first impression, since the absolute correction is not time dependent, a
zig-zag light curve 
would look suspicious. However, to have a better idea, would you mind sending
me:
1) the plots that you extracted with absolute and relative correction
2) the log of the reduction/analysis of the observation from the very beginning
to the use of 
epiclccorr included. 

Thank you
Kind regards
Simone


> Full_Name: Jaewoong Jung
> Submission from: (NULL) (193.147.152.102)
> 
> 
> Dear XMM helpdesk team,
> 
> I'm studying a magnetosheath SWCX signal from XMM data. So after filtering
> soft-proton flare, removing other things like point sources, I made a
light
> curve from very large region ((detx,dety) in circle (0,0,16000)) using
> evselect.
> However, resultant light curve had unnatural zig-zag pattern, and I thought
it
> is due to effect of GTI included. I'm trying to correct light curve
following
> this article, 
> https://www.cosmos.esa.int/web/xmm-newton/sas-thread-timing
> But the fact that article explicitly states that it's for point source
light
> curve worries me. 
> 
> I'm trying to use following command,
> 
> epiclccorr srctslist=MOS1cleanf.lc eventlist=MOS1cleanf.fits
> outset=MOS1_lccorr.lc applyabsolutecorrections=yes
> 
> Here MOS1cleanf.lc is the lightcurve generated from evselect,
MOS1cleanf.fits
is
> the event file after soft proton filtering and point sources removed.
> 
> I'm not including background lightcurve because I'm doing magnetosheath
> background study, and I already found out the value of other background
> (particle, astrophysical, heliospheric) from spectral analysis. I'll
subtract
it
> from my light curve later to get the final light curve.
> 
> I'm not sure whether I should use absolute/relative correction . After
reading
> epiclccorr document, it looks like relative correction is for my job, but
then
> are vignetting, bad pixels not corrected? I couldn't find subroutines of
> epiclccorr so I couldn't analyze each of them separately.
> 
> Actually I tried that command and resultant curve looked better than the
> not-corrected one, but I'm not sure whether it is done correctly. 
> 
> Can you give me your advice whether epiclccorr will works for my job
please?
> 
> Thanks,
> Jaewoong
> 
> 


Followup 1

Compose reply
Download message
From: Jaewoong Jung <jjung11@alaska.edu>
Date: Fri, 26 Apr 2019 13:58:22 -0800
Subject: Re: Using epiclccorr for extended source lightcurve (PR#84888)
To: Simone Migliari <xmmhelp@sciops.esa.int>
--000000000000359d97058776097c
Content-Type: multipart/alternative; boundary="000000000000359d93058776097a"

--000000000000359d93058776097a
Content-Type: text/plain; charset="UTF-8"

Dear Simone,

Thank you for your answer.
I attached the log of the reduction, and the plots from absolute/relative
correction. (I exported data using fv and used a Python script -which is
not included here- to make plots. Absolute correction plot is made from
MOS1_lccorra.lc and relative correction plot is from MOS1_lccorrr.lc)

Thanks
Jaewoong



On Thu, Apr 25, 2019 at 12:58 AM Simone Migliari <xmmhelp@sciops.esa.int>
wrote:

> Dear Jaewoong Jung
>
> apologies for the late reply.
>
> As a first impression, since the absolute correction is not time
> dependent, a
> zig-zag light curve
> would look suspicious. However, to have a better idea, would you mind
> sending
> me:
> 1) the plots that you extracted with absolute and relative correction
> 2) the log of the reduction/analysis of the observation from the very
> beginning
> to the use of
> epiclccorr included.
>
> Thank you
> Kind regards
> Simone
>
>
> > Full_Name: Jaewoong Jung
> > Submission from: (NULL) (193.147.152.102)
> >
> >
> > Dear XMM helpdesk team,
> >
> > I'm studying a magnetosheath SWCX signal from XMM data. So after
> filtering
> > soft-proton flare, removing other things like point sources, I made a
> light
> > curve from very large region ((detx,dety) in circle (0,0,16000)) using
> > evselect.
> > However, resultant light curve had unnatural zig-zag pattern, and I
> thought
> it
> > is due to effect of GTI included. I'm trying to correct light curve
> following
> > this article,
> > https://www.cosmos.esa.int/web/xmm-newton/sas-thread-timing
> > But the fact that article explicitly states that it's for point source
> light
> > curve worries me.
> >
> > I'm trying to use following command,
> >
> > epiclccorr srctslist=MOS1cleanf.lc eventlist=MOS1cleanf.fits
> > outset=MOS1_lccorr.lc applyabsolutecorrections=yes
> >
> > Here MOS1cleanf.lc is the lightcurve generated from evselect,
> MOS1cleanf.fits
> is
> > the event file after soft proton filtering and point sources removed.
> >
> > I'm not including background lightcurve because I'm doing
magnetosheath
> > background study, and I already found out the value of other
background
> > (particle, astrophysical, heliospheric) from spectral analysis. I'll
> subtract
> it
> > from my light curve later to get the final light curve.
> >
> > I'm not sure whether I should use absolute/relative correction . After
> reading
> > epiclccorr document, it looks like relative correction is for my job,
but
> then
> > are vignetting, bad pixels not corrected? I couldn't find subroutines
of
> > epiclccorr so I couldn't analyze each of them separately.
> >
> > Actually I tried that command and resultant curve looked better than
the
> > not-corrected one, but I'm not sure whether it is done correctly.
> >
> > Can you give me your advice whether epiclccorr will works for my job
> please?
> >
> > Thanks,
> > Jaewoong
> >
> >
>
> 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).
>
>
>

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

<div dir=3D"ltr">Dear
Simone,<div><br></div><div>Thank you for your answer.=
=C2=A0<br><div>I attached the log of the reduction, and the plots
from abso=
lute/relative correction. (I exported data using fv and used a Python scrip=
t -which is not included here- to make plots. Absolute correction plot is m=
ade from MOS1_lccorra.lc and relative correction plot is from MOS1_lccorrr.=
lc)</div><div><br></div><div>Thanks</div><div>Jaewoong</div><div><br></div>=
<div><br></div></div></div><br><div
class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Thu, Apr 25, 2019 at 12:58 AM Simone Migliari
&lt;<=
a href=3D"mailto:xmmhelp@sciops.esa.int">xmmhelp@sciops.esa.int</a>&gt;
wro=
te:<br></div><blockquote class=3D"gmail_quote"
style=3D"

Message of length 1756568 truncated


Reply 2

Resend
From: Simone Migliari <xmmhelp@sciops.esa.int>
To: jjung11@alaska.edu
Subject: Re: Using epiclccorr for extended source lightcurve (PR#84888)
Date: Tue Apr 30 18:02:32 2019
Dear Jaewoong

thank you for your patience. We are trying to reproduce the analysis and the
plots. We will get back 
to you as soon as possible. Please note in Spain there are two days of holidays,
so it will be slower. 
Apologies for the inconvenience. 

regards
Simone

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