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

From: bernardini@wayne.edu
Subject: OM tracking mode
Compose reply
Download message
Move To:
1 replies: 1
1 followups: 1

Private message: yes  no

Notes:

Notification:


Date: Fri, 14 Feb 2014 17:08:50 GMT
From: bernardini@wayne.edu
To: xmmhelp@sciops.esa.int
CC: bernardini@wayne.edu
Subject: OM tracking mode
Full_Name: Federico Bernardini
Submission from: (NULL) (35.16.30.184)


I am trying to apply the barycenter correction to OM data. By looking at the
header file, the data I am working on are in DATAMODE='TRAKING'. The procedure
to apply the barycenter correction suggested at
http://xmm.esac.esa.int/sas/current/documentation/threads/omf_thread.shtml
does not work. since it refers to FAST MODE only.

How can I apply the barycenter correction to TRAKING MODE data?

I am interested in the following observation ID: 0405180501, 0206380301,
0679810201

Thanks 

Regards,

Federico


Reply 1

Resend
From: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
To: bernardini@wayne.edu
Subject: Re: OM tracking mode (PR#73644)
Date: Sat Feb 15 17:34:03 2014
Dear Federico Bernardini,

 could you explain the purpose behind studying the processed tracking data
files? These files are only useful for studying the OM field tracking stars. 

Normally the baricentric corrections are used when one is studying variability
(e.g. in OM fast  mode). The referred SAS thread is in fact for OM fast mode
data, and it works on the P*TIMESR* produced by omfchain or in pps products.

Of course, one may want to have the observing times referred to the Solar System
Baricenter and therefore one has to apply the correction and there are many
tools in IDL and other packages (XMM orbital data are needed). For XMM this
correction  will be insignificant, unless you want to compute, say the phase of
a known periodic system.

The SAS task baricenter can be used with appropriate input files (see SAS doc).
For any set of times (e.g. observing times in OM image exposures) it should be
possible to create a table with the format and structure of the P*TIMESR* files
and then apply baricen as if it was a fast mode table (the necessary XMM orbital
data can be found in the ODF).

You can find both image and fast mode data in the quoted obsids. So for the fast
mode, no problem: first omfchain and after baricen. For the image data, you can
take the middle exposure time of each exposure and create a table
P*TIMESR*_like.

By the way, there is an additional obsid for the same target: 0679810101. 

 Best wishes,
Jan-Uwe Ness


> I am trying to apply the barycenter correction to OM data. By looking at
the
> header file, the data I am working on are in DATAMODE='TRAKING'. The
procedure
> to apply the barycenter correction suggested at
> http://xmm.esac.esa.int/sas/current/documentation/threads/omf_thread.shtml
> does not work. since it refers to FAST MODE only.
> 
> How can I apply the barycenter correction to TRAKING MODE data?
> 
> I am interested in the following observation ID: 0405180501, 0206380301,
> 0679810201
> 
> Thanks 
> 
> Regards,
> 
> Federico
> 
> 


Followup 1

Compose reply
Download message
Subject: Re: OM tracking mode (PR#73644)
From: Federico Bernardini <fh0126@wayne.edu>
Date: Sat, 15 Feb 2014 13:14:18 -0500
To: Jan-Uwe Ness <xmmhelp@sciops.esa.int>
I see,
thank you vary much.

What I really need is the fast mode data.

Thanks again

Federico

On Feb 15, 2014, at 12:34 PM, Jan-Uwe Ness <xmmhelp@sciops.esa.int> wrote:

> Dear Federico Bernardini,
> 
> could you explain the purpose behind studying the processed tracking data
> files? These files are only useful for studying the OM field tracking
stars. 
> 
> Normally the baricentric corrections are used when one is studying
variability
> (e.g. in OM fast  mode). The referred SAS thread is in fact for OM fast
mode
> data, and it works on the P*TIMESR* produced by omfchain or in pps
products.
> 
> Of course, one may want to have the observing times referred to the Solar
System
> Baricenter and therefore one has to apply the correction and there are many
> tools in IDL and other packages (XMM orbital data are needed). For XMM this
> correction  will be insignificant, unless you want to compute, say the
phase of
> a known periodic system.
> 
> The SAS task baricenter can be used with appropriate input files (see SAS
doc).
> For any set of times (e.g. observing times in OM image exposures) it should
be
> possible to create a table with the format and structure of the P*TIMESR*
files
> and then apply baricen as if it was a fast mode table (the necessary XMM
orbital
> data can be found in the ODF).
> 
> You can find both image and fast mode data in the quoted obsids. So for the
fast
> mode, no problem: first omfchain and after baricen. For the image data, you
can
> take the middle exposure time of each exposure and create a table
> P*TIMESR*_like.
> 
> By the way, there is an additional obsid for the same target: 0679810101. 
> 
> Best wishes,
> Jan-Uwe Ness
> 
> 
>> I am trying to apply the barycenter correction to OM data. By looking
at the
>> header file, the data I am working on are in DATAMODE='TRAKING'. The
> procedure
>> to apply the barycenter correction suggested at
>> http://xmm.esac.esa.int/sas/current/documentation/threads/omf_thread.shtml
>> does not work. since it refers to FAST MODE only.
>> 
>> How can I apply the barycenter correction to TRAKING MODE data?
>> 
>> I am interested in the following observation ID: 0405180501,
0206380301,
>> 0679810201
>> 
>> Thanks 
>> 
>> Regards,
>> 
>> Federico
>> 
>> 
> 
> 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.
> 



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   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