<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-AU" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Hi Craig,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Yes I think the main issue is if correlators use the location.dat from sched as telescope positions, the bookkeeping is not enough to know which ITRF frame was used. The rest of
the sched/calc mechanisms are fine.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Cheers<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US">Chris<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Difx-users <difx-users-bounces@listmgr.nrao.edu> on behalf of R. Craig Walker via Difx-users <difx-users@listmgr.nrao.edu><br>
<b>Date: </b>Saturday, 5 July 2025 at 09:32<br>
<b>To: </b>difx-users@listmgr.nrao.edu <difx-users@listmgr.nrao.edu><br>
<b>Subject: </b>Re: [Difx-users] ITRF realisations {External}<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Sched, at least when I was the author and maintainer, never claimed to
<br>
do geometric calculations at a level appropriate for correlation. For <br>
scheduling of scans, typically many seconds long, one can be more <br>
casual. So Sched never required the user to provide EOP. The <br>
correlators needed to get measured EOP values for best results. What <br>
Sched does provide to the correlator and get from the users are the <br>
station and source coordinates in whatever reference frames are being <br>
used. For this, it is important that the coordinate values be in the <br>
same system used for the EOP measurements that the correlator will use, <br>
whatever those are. After all, the EOP are a major factor in defining <br>
the rotation between the terrestrial and celestial reference frames at <br>
the time of the observations. So when scheduling, you should learn <br>
which ITRF realization is being used for the EOP observations and use <br>
that for astronomy observations. For geodetic observations, it may not <br>
matter because the model will be bucked out and replaced anyway.<br>
<br>
Cheers,<br>
<br>
Craig<br>
<br>
<br>
On 7/4/25 6:49 AM, Leonid Petrov via Difx-users wrote:<br>
> Chris,<br>
><br>
> I looked at sched-12.0. I found that internally it uses UTC(t)<br>
> function as time. It assumes UT1(t) = UTC(t), see for instance<br>
> schgeo.f. This can introduce an error that is equivalent to an<br>
> error in position of mid-latitude sites at a level of several<br>
> hundreds meters.<br>
><br>
> In that context difference in several centimeters between different<br>
> station catalogues is irrelevant.<br>
><br>
> Leonid<br>
> 2025.07.04_08:47:11<br>
><br>
>> On 2025-07-04 01:02, Phillips, Chris (S&A, Marsfield) via Difx-users <br>
>> wrote:<br>
>> Hi all,<br>
>><br>
>> I have just learned that ITRF (which we use as the XYZ coordinate<br>
>> system of our telescopes) has multiple realisations (ITRF2000,<br>
>> ITRF2014 etc).<br>
>><br>
>> There was approx a 9cm change between around ITRF2005, which is huge.<br>
>><br>
>> The “Frame” detail in Sched is light on details and vex2difx make<br>
>> no mention of frame.<br>
>><br>
>> Does anyone know what ITRF frame Sched expects?<br>
>><br>
>> Thanks<br>
>><br>
>> Chris<br>
>> _______________________________________________<br>
>> Difx-users mailing list<br>
>> Difx-users@listmgr.nrao.edu<br>
>> <a href="https://listmgr.nrao.edu/mailman/listinfo/difx-users">https://listmgr.nrao.edu/mailman/listinfo/difx-users</a><br>
><br>
> _______________________________________________<br>
> Difx-users mailing list<br>
> Difx-users@listmgr.nrao.edu<br>
> <a href="https://listmgr.nrao.edu/mailman/listinfo/difx-users">https://listmgr.nrao.edu/mailman/listinfo/difx-users</a><br>
<br>
_______________________________________________<br>
Difx-users mailing list<br>
Difx-users@listmgr.nrao.edu<br>
<a href="https://listmgr.nrao.edu/mailman/listinfo/difx-users">https://listmgr.nrao.edu/mailman/listinfo/difx-users</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>