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

From: jjung11@alaska.edu
Subject: XMM position is different from SSCweb result
Compose reply
Download message
Move To:
2 replies: 1 2
2 followups: 1 2

Private message: yes  no

Notes:

Notification:


Date: Wed, 24 Jul 2019 02:03:15 +0200
From: jjung11@alaska.edu
To: xmmhelp@sciops.esa.int
Subject: XMM position is different from SSCweb result
Full_Name: Jaewoong Jung
Submission from: (NULL) (193.147.152.102)


Dear XMM helpdesk team,

I was plotting XMM position for certain observation using radiation monitor file
(0339_orbit.FIT) and realized my plot is different from what is drawn in
literature studied same observation.
I checked it with NASA SSCweb data,
https://sscweb.gsfc.nasa.gov/cgi-bin/Locator_graphics.cgi
and found the plot in the literature is consistent with the SSCweb, but not with
RAF file.

I used 0339_orbit.FIT from radmon_0339 from XMM data archive.
The 150001 th column says at time t=1.196166731840E+08, which corresponds to
2001-10-16 10:50:09 (I used ttag command of Heasoft), XMM X position was 
-5.022592735359E+04, which is about -7.9 Earth radii.  However, when I plot the
XMM orbit in the SSCWEB for the 2001-10-16 from 10 o'clock to 11 o'clock, XMM x
position is about 7 Earth radii. It's almost like opposite, but I couldn't find
any reference that XMM is using inverted coordinate system in the 'orbit' task
document.

Can you tell which one is wrong?

Best,
Jaewoong


Reply 1

Resend
From: Lucia Ballo <xmmhelp@sciops.esa.int>
To: jjung11@alaska.edu
Subject: Re: XMM position is different from SSCweb result (PR#85483)
Date: Fri Jul 26 16:25:44 2019
Dear Jaewoong,

I suspect that you might be comparing plots based on different 
coordinate systems.

As regards the radiation monitor file, currently the output of the 
task orbit contains two sets of position vectors: x-y-z GEI and x-y-z 
GSE position vectors (in both cases, in km):

https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/node8.html

The celestial to geocentric solar ecliptic conversion has been 
implemented in the version 2.10 of the orbit task:

https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/ChangeLog

*_orbit.FIT files produced with older versions (as the one available in 
the XSA for rev. 339, that is produced using version 2.9) contain only 
one set of position vectors, corresponding to the celestial x-y-z.


Instead, if I understood correctly, when producing the plot with 
the NASA SSCweb data you are asking for orbits plotted in the GSE
system.
You might want to check if the two plots for rev. 339 agree better when 
using the NASA SSCweb data in the GEI system, or comparing the results 
in the GSE system for a more recent revolution.


Could you please try these checks and let us know if you still find something 
strange?


With kind regards,
Lucia

--
   Dr Lucia Ballo 
   XMM-Newton Science Operations Centre
   Community Support and Scientific Planning Team


Followup 1

Compose reply
Download message
From: Jaewoong Jung <jjung11@alaska.edu>
Date: Fri, 26 Jul 2019 14:52:17 -0800
Subject: Re: XMM position is different from SSCweb result (PR#85483)
To: Lucia Ballo <xmmhelp@sciops.esa.int>
--000000000000861487058e9d6573
Content-Type: text/plain; charset="UTF-8"

Dear Lucia,

Thanks for the reply.
Even though task orbit says it produces two sets of position vectors,
radiation monitor file (even for recent rev 1888) contains only one
position vector, and XMM website doesn't give explanation which one is
that. (GSE or GEI)
Can you clarify on this point?

Thanks
Jaewoong



On Fri, Jul 26, 2019 at 6:25 AM Lucia Ballo <xmmhelp@sciops.esa.int>
wrote:

> Dear Jaewoong,
>
> I suspect that you might be comparing plots based on different
> coordinate systems.
>
> As regards the radiation monitor file, currently the output of the
> task orbit contains two sets of position vectors: x-y-z GEI and x-y-z
> GSE position vectors (in both cases, in km):
>
> https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/node8.html
>
> The celestial to geocentric solar ecliptic conversion has been
> implemented in the version 2.10 of the orbit task:
>
> https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/ChangeLog
>
> *_orbit.FIT files produced with older versions (as the one available in
> the XSA for rev. 339, that is produced using version 2.9) contain only
> one set of position vectors, corresponding to the celestial x-y-z.
>
>
> Instead, if I understood correctly, when producing the plot with
> the NASA SSCweb data you are asking for orbits plotted in the GSE
> system.
> You might want to check if the two plots for rev. 339 agree better when
> using the NASA SSCweb data in the GEI system, or comparing the results
> in the GSE system for a more recent revolution.
>
>
> Could you please try these checks and let us know if you still find
> something
> strange?
>
>
> With kind regards,
> Lucia
>
> --
>    Dr Lucia Ballo
>    XMM-Newton Science Operations Centre
>    Community Support and Scientific Planning Team
>
> 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).
>
>
>

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

<div dir=3D"ltr">Dear=C2=A0Lucia,<div><br></div><div>Thanks
for the reply.<=
/div><div>Even though task orbit says it produces two sets of position
vect=
ors, radiation monitor file (even for recent rev 1888) contains only one po=
sition vector, and XMM website doesn&#39;t give explanation which one is th=
at. (GSE or GEI)</div><div>Can you clarify on this
point?</div><div><br></d=
iv><div>Thanks</div><div>Jaewoong</div><div><br></div><div><br></div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr"
class=3D"gmail_attr">On Fri=
, Jul 26, 2019 at 6:25 AM Lucia Ballo &lt;<a
href=3D"mailto:xmmhelp@sciops.=
esa.int">xmmhelp@sciops.esa.int</a>&gt;
wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Dear Jaewoong,<br>
<br>
I suspect that you might be comparing plots based on different <br>
coordinate systems.<br>
<br>
As regards the radiation monitor file, currently the output of the <br>
task orbit contains two sets of position vectors: x-y-z GEI and x-y-z <br>
GSE position vectors (in both cases, in km):<br>
<br>
<a href=3D"https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/=
node8.html" rel=3D"noreferrer" target=3D"_blank">https://xmm-tools.cosmos.e=
sa.int/external/sas/current/doc/orbit/node8.html</a><br>
<br>
The celestial to geocentric solar ecliptic conversion has been <br>
implemented in the version 2.10 of the orbit task:<br>
<br>
<a href=3D"https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/=
ChangeLog" rel=3D"noreferrer" target=3D"_blank">https://xmm-tools.cosmos.es=
a.int/external/sas/current/doc/orbit/ChangeLog</a><br>
<br>
*_orbit.FIT files produced with older versions (as the one available in <br=
>
the XSA for rev. 339, that is produced using version 2.9) contain only
<br>
one set of position vectors, corresponding to the celestial x-y-z.<br>
<br>
<br>
Instead, if I understood correctly, when producing the plot with <br>
the NASA SSCweb data you are asking fo

Message of length 6343 truncated


Reply 2

Resend
From: Lucia Ballo <xmmhelp@sciops.esa.int>
To: jjung11@alaska.edu
Subject: Re: XMM position is different from SSCweb result (PR#85483)
Date: Thu Aug  1 17:26:39 2019
Dear Jaewoong,

As you find reported in the ChangeLog of the SAS task orbit:

https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/ChangeLog

the conversion from GEI to GSE coordinates has been implemented in the 
version 2.10 of the orbit task, released on 2014-04-25; you may have a 
look also to the comments to the task:

https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/node10.html

Our documentation refers to the last version.

Revolution analysed with older versions of the task do not include this 
conversion; therefore, in that cases the *_orbit.FIT file includes only
one set of position vector, corresponding to the GEI of year J2000.0. 
This is the case, for example, of rev. 1888, that was created with orbit-2.9, 
as you can check in the header of the 1888_orbit.FIT file.

I hope that this can help you; otherwise please do not hesitate to contact us 
again.

With kind regards,
Lucia


Followup 2

Compose reply
Download message
From: Jaewoong Jung <jjung11@alaska.edu>
Date: Thu, 1 Aug 2019 16:05:09 -0800
Subject: Re: XMM position is different from SSCweb result (PR#85483)
To: Lucia Ballo <xmmhelp@sciops.esa.int>
--00000000000038db23058f171d88
Content-Type: text/plain; charset="UTF-8"

Dear Lucia,

Thank you for the clarification. Sorry it's my fault that I didn't read it
carefully.


Best regards,
Jaewoong

On Thu, Aug 1, 2019 at 7:26 AM Lucia Ballo <xmmhelp@sciops.esa.int> wrote:

> Dear Jaewoong,
>
> As you find reported in the ChangeLog of the SAS task orbit:
>
> https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/ChangeLog
>
> the conversion from GEI to GSE coordinates has been implemented in the
> version 2.10 of the orbit task, released on 2014-04-25; you may have a
> look also to the comments to the task:
>
> https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/node10.html
>
> Our documentation refers to the last version.
>
> Revolution analysed with older versions of the task do not include this
> conversion; therefore, in that cases the *_orbit.FIT file includes only
> one set of position vector, corresponding to the GEI of year J2000.0.
> This is the case, for example, of rev. 1888, that was created with
> orbit-2.9,
> as you can check in the header of the 1888_orbit.FIT file.
>
> I hope that this can help you; otherwise please do not hesitate to contact
> us
> again.
>
> With kind regards,
> Lucia
>
> 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).
>
>
>

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

<div dir=3D"ltr"><div>Dear
Lucia,</div><div><br></div>Thank you for the cla=
rification. Sorry it&#39;s my fault that I didn&#39;t read it
carefully.<br=
><div><br></div><div><br></div><div>Best
regards,</div><div>Jaewoong</div><=
/div><br><div class=3D"gmail_quote"><div dir=3D"ltr"
class=3D"gmail_attr">O=
n Thu, Aug 1, 2019 at 7:26 AM Lucia Ballo &lt;<a
href=3D"mailto:xmmhelp@sci=
ops.esa.int">xmmhelp@sciops.esa.int</a>&gt;
wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">Dear Jaewoong,<br>
<br>
As you find reported in the ChangeLog of the SAS task orbit:<br>
<br>
<a href=3D"https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/=
ChangeLog" rel=3D"noreferrer" target=3D"_blank">https://xmm-tools.cosmos.es=
a.int/external/sas/current/doc/orbit/ChangeLog</a><br>
<br>
the conversion from GEI to GSE coordinates has been implemented in the
<br>
version 2.10 of the orbit task, released on 2014-04-25; you may have a
<br>
look also to the comments to the task:<br>
<br>
<a href=3D"https://xmm-tools.cosmos.esa.int/external/sas/current/doc/orbit/=
node10.html" rel=3D"noreferrer" target=3D"_blank">https://xmm-tools.cosmos.=
esa.int/external/sas/current/doc/orbit/node10.html</a><br>
<br>
Our documentation refers to the last version.<br>
<br>
Revolution analysed with older versions of the task do not include this <br=
>
conversion; therefore, in that cases the *_orbit.FIT file includes
only<br>
one set of position vector, corresponding to the GEI of year J2000.0. <br>
This is the case, for example, of rev. 1888, that was created with orbit-2.=
9, <br>
as you can check in the header of the 1888_orbit.FIT file.<br>
<br>
I hope that this can help you; otherwise please do not hesitate to contact =
us <br>
again.<br>
<br>
With kind regards,<br>
Lucia<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>

--00000000000038db23058f171d88--


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