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 OM/75049
Full headers

From: Domitilla de Martino <demartino@na.astro.it>
Subject: Re: XMM-Newton re-generated ODF data available (Observation
Compose reply
Download message
Move To:
7 replies: 1 2 3 4 5 6 7
6 followups: 1 2 3 4 5 6

Private message: yes  no

Notes:

Notification:


Date: Tue, 29 Jul 2014 23:39:20 +0200
From: Domitilla de Martino <demartino@na.astro.it>
To: Nora Loiseau <Nora.Loiseau@sciops.esa.int>
Cc: <demartino@oacn.inaf.it>, xmmpi <xmmpi@sciops.esa.int>
Subject: Re: XMM-Newton re-generated ODF data available (Observation
   Dear Nora

The processed OM data of the above mentioned observation lack of the 
corresponding PPS for the segment S405. I've also tried to reprocess the 
ODF with SAS but it also fails to process that segment.
   Do you know what problem could be there?
  Thanking you in advance
  Domitilla


Il 2014-07-07 12:55 Nora Loiseau ha scritto:
> Dear Domitilla,
> 
> XMM-Newton Observation Data Files (ODF) for one of your observations
> are now available to you at the XMM-Newton Science Archive (XSA).
> 
> XMM-Newton Observation Id : 0729560801
> Observed in Revolution    : 2664
> ODF version number        : 001
> 
> Details of the observation can be found at:
> 
> 
> http://xmm2.esac.esa.int/obs-public/obs_view.tcl?search_instrument=0&action=Get+Selection&search_obs_id=0729560801
> 
> You can download the ODF through the XSA user interface, available at:
> 
>     http://nxsa.esac.esa.int
> 
> Please, use the username ps15 and password ps15xmm.
> 
> The ODF files were regenerated in order to provide the best possible 
> data.
> 
> 
> Best regards,
> 
> Nora
> 
> 
> 
> 
> 
> 
> 
> 
> 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.


Reply 1

Resend
From: Jacobo Ebrero <xmmpi@sciops.esa.int>
To: demartino@oacn.inaf.it
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#82696)
Date: Wed Jul 30 13:40:47 2014
Dear Domitilla,

We have checked the PPS products of your observation 0729560801 and the OM files
for segment S405 are present and they look good. We have also re-processed the
ODF without encountering any problems. Could you please send us the following in
order to reproduce your problem?

1) your working environment, as provided by the following commands:

sasversion >& mysassetup.log
uname -a >> mysassetup.log
env >> mysassetup.log

2) the full list of commands that you used including those for the SAS
start-up,

3) the output log of your commands executed with verbosity level 5 (-V 5), in
particular the one that gives an error message when trying to reprocess segment
S405.

Best regards,
Jacobo
-------------------
Dr. Jacobo Ebrero
XMM-Newton SOC
User Support Group


Reply 2

Resend
From: Jacobo Ebrero <xmmpi@sciops.esa.int>
To: demartino@oacn.inaf.it
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#82700)
Date: Thu Jul 31 11:49:07 2014
Dear Domitilla,

Thank you for the clarification. Indeed the source time series are not
created for S405 because the source detection algorithm has not found any
sources for this particular exposure. We will discuss this issue with the
OM expert and we will get back to you as soon as we have further news.

Best regards,
Jacobo
-------------------
Dr. Jacobo Ebrero
XMM-Newton SOC
User Support Group


Reply 3

Resend
From: Jacobo Ebrero <xmmpi@sciops.esa.int>
To: demartino@oacn.inaf.it
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#82700)
Date: Tue Aug  5 14:29:05 2014
Dear Domitilla,

This observation contains 10 exposures with OM in Fast mode. Looking at the PPS
data one can see that exposure 405 has not produced a time series file (*TIMESR*
file) after processing with SAS (PIPELINE).

By looking at the Fast mode "pseudo-images" (*IMAGEF* files) the target source
can be seen more o less clearly. We suggest to check always the presence of
source(s) in the fast window pseudo-image, as indicated in this thread:

http://xmm.esac.esa.int/sas/current/documentation/threads/omf_thread.shtml

For example, by using e.g. ds9, we display these images and we superimpose the
corresponding region files (*SFSREG* files) so that we can see that for exposure
405 no source has been detected. Furthermore, we also see that the detection in
exposure 406 is not correct, and therefore the corresponding timeseries for this
exposure is wrong.

The problem then is the detection of the target in these two exposures 405 and
406. The solution for this is to perform a manual detection of the target using
the interactive SAS task "omsource" on the images
P0729560801OMS405IMAGEF1000.FTZ and P0729560801OMS406IMAGEF1000.FTZ.

We obtain in this way two source lists which can be used for the subsequent fast
mode processing. Instead of "omfchain" we have to use the individual tasks:

 omregion + evselect + evselect + omlcbuild + lcplot

where in omregion we use as input the source list obtained with omsource. The
sequence will look as follows (for example for exposure 405):

(P0729560801OMS405NEWSWSRLI1000.FIT is the source list obtained with omsource)

omregion set=my_work_path/P0729560801OMS405NEWSWSRLI1000.FIT srcnumber=1
srcradius=-6 nfwhm=3 bkginner=1.2 bkgouter=2.5
bkgfile=my_work_path/F0729560801OMS405NEWBGDREG1000.FIT
srcfile=my_work_path/F0729560801OMS405NEWSRCREG1000.FIT

evselect table=my_work_path/F0729560801OMS405NEWEVLIST1000.FIT
filteredset=filtered.fits withfilteredset=no keepfilteroutput=no
flagcolumn=EVFLAG flagbit=-1 destruct=yes dssblock='' expression='((WIN_FLAG
.eq. 0) .and. (region(my_work_path/F0729560801OMS405NEWSRCREG1000.FIT, CORR_X,
CORR_Y)))' filtertype=expression cleandss=no updateexposure=yes
filterexposure=yes writedss=yes blockstocopy='' attributestocopy=''
energycolumn=PHA zcolumn=WEIGHT zerrorcolumn=EWEIGHT withzerrorcolumn=no
withzcolumn=no ignorelegallimits=no imageset=image.fits xcolumn=RAWX
ycolumn=RAWY ximagebinsize=1 yimagebinsize=1 squarepixels=no ximagesize=600
yimagesize=600 imagebinning=imageSize ximagemin=1 ximagemax=640 withxranges=no
yimagemin=1 yimagemax=640 withyranges=no imagedatatype=Real64
withimagedatatype=no raimagecenter=0 decimagecenter=0 withcelestialcenter=no
withimageset=no spectrumset=spectrum.fits spectralbinsize=5 specchannelmin=0
specchannelmax=11999 withspecranges=no withspectrumset=no
rateset=my_work_path/F0729560801OMS405NEWSCRATE1000.FIT timecolumn=TIME
timebinsize=10 timemin=0 timemax=1000 withtimeranges=no maketimecolumn=yes
makeratecolumn=no withrateset=yes histogramset=histo.fits histogramcolumn=TIME
histogrambinsize=1 histogrammin=0 histogrammax=1000 withhistoranges=no
withhistogramset=no

evselect table=my_work_path/F0729560801OMS405NEWEVLIST1000.FIT
filteredset=filtered.fits withfilteredset=no keepfilteroutput=no
flagcolumn=EVFLAG flagbit=-1 destruct=yes dssblock='' expression='WIN_FLAG .eq.
0 && region(my_work_path/F0729560801OMS405NEWBGDREG1000.FIT, CORR_X,
CORR_Y)'
filtertype=expression cleandss=no updateexposure=yes filterexposure=yes
writedss=yes blockstocopy='' attributestocopy='' energycolumn=PHA zcolumn=WEIGHT
zerrorcolumn=EWEIGHT withzerrorcolumn=no withzcolumn=no ignorelegallimits=no
imageset=image.fits xcolumn=RAWX ycolumn=RAWY ximagebinsize=1 yimagebinsize=1
squarepixels=no ximagesize=600 yimagesize=600 imagebinning=imageSize ximagemin=1
ximagemax=640 withxranges=no yimagemin=1 yimagemax=640 withyranges=no
imagedatatype=Real64 withimagedatatype=no raimagecenter=0 decimagecenter=0
withcelestialcenter=no withimageset=no spectrumset=spectrum.fits
spectralbinsize=5 specchannelmin=0 specchannelmax=11999 withspecranges=no
withspectrumset=no rateset=my_work_path/F0729560801OMS405NEWBGRATE1000.FIT
timecolumn=TIME timebinsize=10 timemin=0 timemax=1000 withtimeranges=no
maketimecolumn=yes makeratecolumn=no withrateset=yes histogramset=histo.fits
histogramcolumn=TIME histogrambinsize=1 histogrammin=0 histogrammax=1000
withhistoranges=no withhistogramset=no

omlcbuild srcregionset=my_work_path/F0729560801OMS405NEWSRCREG1000.FIT
bkgregionset=my_work_path/F0729560801OMS405NEWBGDREG1000.FIT
srcrateset=my_work_path/F0729560801OMS405NEWSCRATE1000.FIT
bkgrateset=my_work_path/F0729560801OMS405NEWBGRATE1000.FIT
sourcelistset=my_work_path/P0729560801OMS405NEWSWSRLI1000.FIT
wdxset=odf_path/2664_0729560801_OMS40500WDX.FIT
outset=my_work_path/P0729560801OMS405NEWTIMESR1000.FIT mod8corrupted=0 
bkgfromimage=no subtractbkg=yes

lcplot set=my_work_path/P0729560801OMS405NEWTIMESR1000.FIT binsize=1
plotdevice=/PS p

Message of length 5555 truncated


Followup 1

Compose reply
Download message
Date: Thu, 31 Jul 2014 11:07:16 +0200
From: Domitilla de Martino <demartino@na.astro.it>
To: Jacobo Ebrero <xmmpi@sciops.esa.int>
Cc: <demartino@oacn.inaf.it>
Subject: Re: XMM-Newton re-generated ODF data available (Observation
   Dear Jacobo
I probably did not clarify what was really missing in the processed 
data for S405.
All file well reprocessed but the source Timeseries was not created. It 
appears that
the source was not detected in both PPS and in my reprocessing.
  Regards
  Domitilla


Il 2014-07-30 15:40 Jacobo Ebrero ha scritto:
> Dear Domitilla,
> 
> We have checked the PPS products of your observation 0729560801 and 
> the OM files
> for segment S405 are present and they look good. We have also 
> re-processed the
> ODF without encountering any problems. Could you please send us the 
> following in
> order to reproduce your problem?
> 
> 1) your working environment, as provided by the following commands:
> 
> sasversion >& mysassetup.log
> uname -a >> mysassetup.log
> env >> mysassetup.log
> 
> 2) the full list of commands that you used including those for the SAS
> start-up,
> 
> 3) the output log of your commands executed with verbosity level 5 (-V 
> 5), in
> particular the one that gives an error message when trying to 
> reprocess segment
> S405.
> 
> Best regards,
> Jacobo
> -------------------
> Dr. Jacobo Ebrero
> XMM-Newton SOC
> User Support Group
> 
> 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.



Followup 2

Compose reply
Download message
Date: Thu, 07 Aug 2014 16:25:53 +0200
From: Domitilla de Martino <demartino@oacn.inaf.it>
To: Jacobo Ebrero <xmmpi@sciops.esa.int>
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#82700)
   Hola Jacobo
Muchas gracias.
I'm currently out of work and will come back at the endof the month. Then
I'll try as you indicate.
Yes, I agree to let this issue known among colleagues as it could be 
very useful
  thank you again

Hasta pronto
Domitilla


Il 05/08/2014 16:29, Jacobo Ebrero ha scritto:
> Dear Domitilla,
>
> This observation contains 10 exposures with OM in Fast mode. Looking at the
PPS
> data one can see that exposure 405 has not produced a time series file
(*TIMESR*
> file) after processing with SAS (PIPELINE).
>
> By looking at the Fast mode "pseudo-images" (*IMAGEF* files) the target
source
> can be seen more o less clearly. We suggest to check always the presence of
> source(s) in the fast window pseudo-image, as indicated in this thread:
>
> http://xmm.esac.esa.int/sas/current/documentation/threads/omf_thread.shtml
>
> For example, by using e.g. ds9, we display these images and we superimpose
the
> corresponding region files (*SFSREG* files) so that we can see that for
exposure
> 405 no source has been detected. Furthermore, we also see that the
detection in
> exposure 406 is not correct, and therefore the corresponding timeseries for
this
> exposure is wrong.
>
> The problem then is the detection of the target in these two exposures 405
and
> 406. The solution for this is to perform a manual detection of the target
using
> the interactive SAS task "omsource" on the images
> P0729560801OMS405IMAGEF1000.FTZ and P0729560801OMS406IMAGEF1000.FTZ.
>
> We obtain in this way two source lists which can be used for the subsequent
fast
> mode processing. Instead of "omfchain" we have to use the individual tasks:
>
>   omregion + evselect + evselect + omlcbuild + lcplot
>
> where in omregion we use as input the source list obtained with omsource.
The
> sequence will look as follows (for example for exposure 405):
>
> (P0729560801OMS405NEWSWSRLI1000.FIT is the source list obtained with
omsource)
>
> omregion set=my_work_path/P0729560801OMS405NEWSWSRLI1000.FIT srcnumber=1
> srcradius=-6 nfwhm=3 bkginner=1.2 bkgouter=2.5
> bkgfile=my_work_path/F0729560801OMS405NEWBGDREG1000.FIT
> srcfile=my_work_path/F0729560801OMS405NEWSRCREG1000.FIT
>
> evselect table=my_work_path/F0729560801OMS405NEWEVLIST1000.FIT
> filteredset=filtered.fits withfilteredset=no keepfilteroutput=no
> flagcolumn=EVFLAG flagbit=-1 destruct=yes dssblock=''
expression='((WIN_FLAG
> .eq. 0) .and. (region(my_work_path/F0729560801OMS405NEWSRCREG1000.FIT,
CORR_X,
> CORR_Y)))' filtertype=expression cleandss=no updateexposure=yes
> filterexposure=yes writedss=yes blockstocopy='' attributestocopy=''
> energycolumn=PHA zcolumn=WEIGHT zerrorcolumn=EWEIGHT withzerrorcolumn=no
> withzcolumn=no ignorelegallimits=no imageset=image.fits xcolumn=RAWX
> ycolumn=RAWY ximagebinsize=1 yimagebinsize=1 squarepixels=no ximagesize=600
> yimagesize=600 imagebinning=imageSize ximagemin=1 ximagemax=640
withxranges=no
> yimagemin=1 yimagemax=640 withyranges=no imagedatatype=Real64
> withimagedatatype=no raimagecenter=0 decimagecenter=0
withcelestialcenter=no
> withimageset=no spectrumset=spectrum.fits spectralbinsize=5
specchannelmin=0
> specchannelmax=11999 withspecranges=no withspectrumset=no
> rateset=my_work_path/F0729560801OMS405NEWSCRATE1000.FIT timecolumn=TIME
> timebinsize=10 timemin=0 timemax=1000 withtimeranges=no maketimecolumn=yes
> makeratecolumn=no withrateset=yes histogramset=histo.fits
histogramcolumn=TIME
> histogrambinsize=1 histogrammin=0 histogrammax=1000 withhistoranges=no
> withhistogramset=no
>
> evselect table=my_work_path/F0729560801OMS405NEWEVLIST1000.FIT
> filteredset=filtered.fits withfilteredset=no keepfilteroutput=no
> flagcolumn=EVFLAG flagbit=-1 destruct=yes dssblock='' expression='WIN_FLAG
.eq.
> 0 && region(my_work_path/F0729560801OMS405NEWBGDREG1000.FIT,
CORR_X, CORR_Y)'
> filtertype=expression cleandss=no updateexposure=yes filterexposure=yes
> writedss=yes blockstocopy='' attributestocopy='' energycolumn=PHA
zcolumn=WEIGHT
> zerrorcolumn=EWEIGHT withzerrorcolumn=no withzcolumn=no
ignorelegallimits=no
> imageset=image.fits xcolumn=RAWX ycolumn=RAWY ximagebinsize=1
yimagebinsize=1
> squarepixels=no ximagesize=600 yimagesize=600 imagebinning=imageSize
ximagemin=1
> ximagemax=640 withxranges=no yimagemin=1 yimagemax=640 withyranges=no
> imagedatatype=Real64 withimagedatatype=no raimagecenter=0 decimagecenter=0
> withcelestialcenter=no withimageset=no spectrumset=spectrum.fits
> spectralbinsize=5 specchannelmin=0 specchannelmax=11999 withspecranges=no
> withspectrumset=no rateset=my_work_path/F0729560801OMS405NEWBGRATE1000.FIT
> timecolumn=TIME timebinsize=10 timemin=0 timemax=1000 withtimeranges=no
> maketimecolumn=yes makeratecolumn=no withrateset=yes
histogramset=histo.fits
> histogramcolumn=TIME hi

Message of length 7509 truncated


Reply 4

Resend
From: Jacobo Ebrero <xmmhelp@sciops.esa.int>
To: demartino@oacn.inaf.it
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#75049)
Date: Mon Oct 20 10:26:01 2014
Dear Domitilla,

We have moved this ticket to the XMM Helpdesk so it is publicly available to the
rest of the users (unless you wish otherwise, in which case we can make it
private).

We would like to know if our recommended procedure worked fine in your dataset.
Please send any follow-up mails to this address (not to the xmmpi one).

Best regards,
Jacobo
----------------------
Dr. Jacobo Ebrero
XMM-Newton SOC
User Support Group


Followup 3

Compose reply
Download message
Date: Mon, 20 Oct 2014 20:20:14 +0200
From: Domitilla de Martino <demartino@oacn.inaf.it>
To: Jacobo Ebrero <xmmhelp@sciops.esa.int>
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#75049)
   Dear Jacobo

Thank you for your email. Yes it worked fine!
  Gratefully
  Cheers
  Domitilla



Il 20/10/2014 12:26, Jacobo Ebrero ha scritto:
> Dear Domitilla,
>
> We have moved this ticket to the XMM Helpdesk so it is publicly available
to the
> rest of the users (unless you wish otherwise, in which case we can make it
> private).
>
> We would like to know if our recommended procedure worked fine in your
dataset.
> Please send any follow-up mails to this address (not to the xmmpi one).
>
> Best regards,
> Jacobo
> ----------------------
> Dr. Jacobo Ebrero
> XMM-Newton SOC
> User Support Group
>
> 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.
>


-- 
=================================================================
  Domitilla de Martino                                           |
                                                                 |
INAF Osservatorio Astronomico di Capodimonte Napoli             |
Via Moiariello 16 80131 Naples Italy                            |
                                                                 |
TEL: 39-081-5575580                                             |
FAX: 39-081-456710                                              |
e-mail: demartino@oacn.inaf.it                                  |
Skype: ddemartino
=================================================================



Followup 4

Compose reply
Download message
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#75049)
From: DEMARTINO DOMITILLA <demartino@oacn.inaf.it>
Date: Thu, 23 Oct 2014 12:46:24 +0200
To: Jacobo Ebrero <xmmhelp@sciops.esa.int>
Dear  Jacobo

 Regarding OM light curves and in particular the conversion from count rates
into magnitude the task "ommag"
 should be used. However using either single fast window mode time series or the
merged ones I find error as detailed below.
 I then just used the SAS watch out countrate-magnitude procedure and for
magnitude errorbars I just compute them from converting the
  max and min rates.

  Could you please let me know what I'm doing wrong?
  Thanking you in advance
 Best wishes
 Domitilla


XMM Science Analysis System - GUI version 1.52.9
Started on Wed Oct 22 19:43:53 2014

@@ SAS_SUPPRESS_WARNING=1; export SAS_SUPPRESS_WARNING
@@ SAS_CCF=/Users/demartinodomitilla/Documents/XSS1227/XMM_2014/0729560801/ANALYSIS/ccf.cif;
$
@@ SAS_CCFPATH=/Users/demartinodomitilla/Documents/XMM/XMM_CCF; export
SAS_CCFPATH
@@ cd /Users/demartinodomitilla/Documents/XSS1227/XMM_2014/0729560801/ANALYSIS
@@ HOME=/Users/demartinodomitilla; export HOME
@@ SAS_MEMORY_MODEL=high; export SAS_MEMORY_MODEL
@@ SAS_ODF=/Users/demartinodomitilla/Documents/XSS1227/XMM_2014/0729560801/ANALYSIS/2664_0729$
@@ SAS_VERBOSITY=5; export SAS_VERBOSITY
Task 'ommag' started
@@ ommag set=OMU_BAR_MAG_50s.fits
Executing (routine): ommag set=OMU_BAR_MAG_50s.fits  -w 1 -V 5
ommag (ommag-3.10.2)  [xmmsas_20130501_1901-13.0.0] started: 
2014-10-22T17:45:20.000
** ommag: fatal (badFileType)  Could not find any compatibile blocks in set
OMU_BAR_MAG_50s.f$
Task 'ommag' finished



Il giorno 20/ott/2014, alle ore 12:26, Jacobo Ebrero
<xmmhelp@sciops.esa.int> ha scritto:

> Dear Domitilla,
> 
> We have moved this ticket to the XMM Helpdesk so it is publicly available
to the
> rest of the users (unless you wish otherwise, in which case we can make it
> private).
> 
> We would like to know if our recommended procedure worked fine in your
dataset.
> Please send any follow-up mails to this address (not to the xmmpi one).
> 
> Best regards,
> Jacobo
> ----------------------
> Dr. Jacobo Ebrero
> XMM-Newton SOC
> User Support Group
> 
> 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.
> 




Reply 5

Resend
From: Jacobo Ebrero <xmmhelp@sciops.esa.int>
To: demartino@oacn.inaf.it
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#75049)
Date: Thu Oct 23 13:11:16 2014
Dear Domitilla,

We would need to know the following:

1) does this error appear with all your lightcurves or only with the one you
mention in you mail?

2) the full list of commands you used to generate the lightcurve; is it one
generated with omfchain or with the recipe that we suggested to use?

3) could you please send us also the conflictive fits file? (if they are more
than one, just the one you mention in your mail would be enough)

Best regards,
Jacobo
----------------------
Dr. Jacobo Ebrero
XMM-Newton SOC
User Support Group


Followup 5

Compose reply
Download message
From: DEMARTINO DOMITILLA <demartino@oacn.inaf.it>
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#75049)
Date: Thu, 23 Oct 2014 15:27:45 +0200
To: Jacobo Ebrero <xmmhelp@sciops.esa.int>
--Apple-Mail=_73B4C9BD-4B8E-48DF-A27D-D525A0312EE6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear Jacobo

>=20
> We would need to know the following:
>=20
> 1) does this error appear with all your lightcurves or only with the =
one you
> mention in you mail?
>=20

   YES with all time series=20

> 2) the full list of commands you used to generate the lightcurve; is =
it one
> generated with omfchain or with the recipe that we suggested to use?
>=20

    I used omichain to reprocess and generate the light curves.
  However it does not work also with the time series produced with your =
recipe.
  The data are Time, rate, error, background, error background=20


> 3) could you please send us also the conflictive fits file? (if they =
are more
> than one, just the one you mention in your mail would be enough)
>=20

     Hereby on single time series (OMS007_BAR_50s.fits) as well as the =
total light curve
obtained merging the 10 OM U band segments  (OMU_BAR_MAG_50s.fits)

  The time series were barycorrected

 =20=

--Apple-Mail=_73B4C9BD-4B8E-48DF-A27D-D525A0312EE6
Content-Disposition: attachment;
	filename=OMS007_BAR_50s.fits
Content-Type: application/octet-stream;
	name="OMS007_BAR_50s.fits"
Content-Transfer-Encoding: quoted-printable

SIMPLE=20=20=3D=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
T=20/=20file=20does=20conform=20to=20FITS=20standard=20=20=20=20=20=20=20=
=20=20=20=20=20=20BITPIX=20=20=3D=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=208=20/=20number=20of=20bits=20per=20data=20pixel=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20NAXIS=20=20=20=3D=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=200=20/=20number=20of=20=
data=20axes=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20EXTEND=20=20=3D=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20T=20/=20FITS=20dataset=20may=20contain=20extensions=20=
=20=20=20=20=20=20=20=20=20=20=20XPROC0=20=20=3D=20'omlcbuild=20=
srcregionset=3D../RE_PROC//F0729560801OMS007SRCREG1000.FIT=20&'CONTINUE=20=
=20'bkgregionset=3D../RE_PROC//F0729560801OMS007BGDREG1000.FIT=20=
srcrateset&'CONTINUE=20=20'=3D../RE_PROC//F0729560801OMS007SCRATE1000.FIT=20=
bkgrateset=3D../RE_PROC/&'CONTINUE=20=20=
'/F0729560801OMS007BGRATE1000.FIT=20=
sourcelistset=3D../RE_PROC//P0729560&'CONTINUE=20=20=
'801OMS007SWSRLI1000.FIT=20=
wdxset=3D../ODF//2664_0729560801_OMS00700WDX.&'CONTINUE=20=20'FIT=20=
outset=3D../RE_PROC//P0729560801OMS007TIMESR1000.FIT=20=
mod8corrupte&'CONTINUE=20=20'd=3D0=20imageset=3D''''=20bkgfromimage=3Dno=20=
subtractbkg=3Dyes=20#=20(omlcbuild-1.39&'CONTINUE=20=20'.1)=20=
[xmmsas_20130501_1901-13.0.0]'=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20XPROC1=20=20=
=3D=20'barycen=20withtable=3Dyes=20table=3DOMS007_BAR_50s.fits:RATE=20=
timecolumn=3DTIM&'CONTINUE=20=20'E=20withsrccoordinates=3Dno=20srcra=3D0=20=
srcdec=3D0=20processgtis=3Dyes=20processexp&'CONTINUE=20=20=
'osutables=3Dyes=20time=3D0=20ephemeris=3DDE405=20#=20(barycen-1.20.4)=20=
[xmmsas_201&'CONTINUE=20=20'30501_1901-13.0.0]'=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20XDAL0=20=20=20=3D=20=
'OMS007_BAR_50s.fits=202014-10-22T11:45:52.000=20Modify=20barycen=20=
(barycen&'CONTINUE=20=20'-1.20.4)=20[xmmsas_20130501_1901-13.0.0]=20High=20=
SAS_MEMORY_MODEL=3Dhigh=20S&'CONTINUE=20=20'AS_ROWS=3D=20SAS_ZERO_ROWS=3D=20=
SAS_COLUMN_WISE=3D=20'=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20XDAL1=20=20=20=3D=20=
'../RE_PROC//P0729560801OMS007TIMESR1000.FIT=20=
2014-07-31T12:26:42.000&'CONTINUE=20=20'=20Create=20omlcbuild=20=
(omlcbuild-1.39.1)=20[xmmsas_20130501_1901-13.0.0]=20&'CONTINUE=20=20=
'High=20SAS_MEMORY_MODEL=3Dhigh=20SAS_ROWS=3D=20SAS_ZERO_ROWS=3D=20=
SAS_COLUMN_WISE=3D'CREATOR=20=3D=20'omlcbuild=20(omlcbuild-1.39.1)=20=
[xmmsas_20130501_1901-13.0.0]'=20/=20name=20ofDATE=20=20=20=20=3D=20=
'2014-07-31T12:26:42.000'=20/=20creation=20date=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20LONGSTRN=3D=20=
'OGIP=201.0'=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20TELESCOP=3D=20'XMM=20=20=20=20=20=
'=20=20=20=20=20=20=20=20=20=20=20/=20Telescope=20(mission)=20name=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20INSTRUME=3D=20=
'OM=20=20=20=20=20=20'=20=20=20=20=20=20=20=20=20=20=20/=20Instrument=20=
name=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20DETNAM=20=20=3D=20'REDUNDANT'=20=20=20=20=20=20=
=20=20=20=20/=20PRIME=20or=20REDUNDAN

Message of length 102735 truncated


Reply 6

Resend
From: Jacobo Ebrero <xmmhelp@sciops.esa.int>
To: demartino@oacn.inaf.it
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#75049)
Date: Thu Oct 23 14:59:36 2014
Dear Domitilla,

Indeed the task ommag is used to convert count rates to magnitudes. However, the
input file is not a light curve but a source list obtained after running
omdetect. In the description of omichain that you can find here:

http://xmm.esac.esa.int/sas/current/documentation/threads/omi_stepbystep.shtml

you can see that the task ommag is run automatically after omdetect (step 10)
and columns with the magnitude and its error are appended to the source list
files *SWSRLI* (columns MAG and MAGERR, respectively). In principle there is no
need to run ommag again unless one wants to modifify some source detection
parameters (e.g. the detection threshold), but in such cases is easier to run
omichain again with the desired settings.

For fast images, the situation is a bit different. In the description of
omfchain:

http://xmm.esac.esa.int/sas/current/documentation/threads/omf_stepbystep.shtml

there is no call to ommag. In this case, the user has to calculate the
magnitudes by hand using the method 3 described in this SAS watchout:

http://xmm.esac.esa.int/sas/current/watchout/Evergreen_tips_and_tricks/uvflux.shtml

introducing in the formula the zero point of your filter and the count rate to
be converted.

Best regards,
Jacobo
----------------------
Dr. Jacobo Ebrero
XMM-Newton SOC
User Support Group


Followup 6

Compose reply
Download message
Date: Thu, 23 Oct 2014 17:11:07 +0200
From: Domitilla de Martino <demartino@oacn.inaf.it>
To: Jacobo Ebrero <xmmhelp@sciops.esa.int>
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#75049)
This is a multi-part message in MIME format.
--------------090505010706000704080706
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

   Dear Jacobo

  Indeed I thought so, but the latest ommag description within SAS (9 
Dec. 2013) states:
"The ...list... can be a source-list from omdetect or a *timeseries* from 
evselect or trcon"
   so a timeseries is supposed to be another type of input file.
   So I wanted to make sure that I was not doing something wrong. Maybe 
this can be clarified in a forthcoming update of that command
  in order to let users know about it.

   The SWSRLI file is there and infact it provides the Average magnitude 
for each segment timeseries.
   But what I wanted to do is to have light curves in magnitude for 
plotting purposes and not single points for each segment.

  Therefore I  computed the magnitudes using SAS watchout from count 
rates using Zeropoint in the U band
  and for errorbars on magnitudes I computed the relative magnitudes 
corresponding to the max and min countrates.
  This is the correct procedure, isn't it?

   Best wishes and thank you again for your prompt reply
   Domitilla


Il 23/10/2014 16:59, Jacobo Ebrero ha scritto:
> Dear Domitilla,
>
> Indeed the task ommag is used to convert count rates to magnitudes.
However, the
> input file is not a light curve but a source list obtained after running
> omdetect. In the description of omichain that you can find here:
>
> http://xmm.esac.esa.int/sas/current/documentation/threads/omi_stepbystep.shtml
>
> you can see that the task ommag is run automatically after omdetect (step
10)
> and columns with the magnitude and its error are appended to the source
list
> files *SWSRLI* (columns MAG and MAGERR, respectively). In principle there
is no
> need to run ommag again unless one wants to modifify some source detection
> parameters (e.g. the detection threshold), but in such cases is easier to
run
> omichain again with the desired settings.
>
> For fast images, the situation is a bit different. In the description of
> omfchain:
>
> http://xmm.esac.esa.int/sas/current/documentation/threads/omf_stepbystep.shtml
>
> there is no call to ommag. In this case, the user has to calculate the
> magnitudes by hand using the method 3 described in this SAS watchout:
>
> http://xmm.esac.esa.int/sas/current/watchout/Evergreen_tips_and_tricks/uvflux.shtml
>
> introducing in the formula the zero point of your filter and the count rate
to
> be converted.
>
> Best regards,
> Jacobo
> ----------------------
> Dr. Jacobo Ebrero
> XMM-Newton SOC
> User Support Group
>
> 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.
>


-- 
=================================================================
  Domitilla de Martino                                           |
                                                                 |
INAF Osservatorio Astronomico di Capodimonte Napoli             |
Via Moiariello 16 80131 Naples Italy                            |
                                                                 |
TEL: 39-081-5575580                                             |
FAX: 39-081-456710                                              |
e-mail: demartino@oacn.inaf.it                                  |
Skype: ddemartino
=================================================================


--------------090505010706000704080706
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">.. Dear Jacobo<br>
      ..<br>
      ..Indeed I thought so, but the latest ommag description within SAS
      (9 Dec. 2013) states:<br>
      "The ...list... can be a source-list from omdetect or a
<b>timeseries</b>
      from evselect or trcon"<br>
      .. so a timeseries is supposed to be another type of input file.<br>
      .. So I wanted to make sure that I was not doing something wrong.
      Maybe this can be clarified in a forthcoming update of that
      command<br>
      ..in order to let users know about it.<br>
      <br>
      .. The SWSRLI file is there and infact it provides the Average
      magnitude for each segment timeseries.<br>
      .. But what I wanted to do is to have light cur

Message of length 9001 truncated


Reply 7

Resend
From: Jacobo Ebrero <xmmhelp@sciops.esa.int>
To: demartino@oacn.inaf.it
Subject: Re: XMM-Newton re-generated ODF data available (Observation (PR#75049)
Date: Mon Oct 27 15:07:00 2014
Dear Domitilla,

The part in the task description that says that the input list can be a
timeseries from evselect or trcon is outdated. Only source lists from omdetect
are considered as a valid input for ommag. Our apologies for the
inconveniences.

Best regards,
Jacobo
----------------------
Dr. Jacobo Ebrero
XMM-Newton SOC
User Support Group

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