<html xmlns:v="urn:schemas-microsoft-com:vml" 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=utf-8">
<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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;
mso-fareast-language:EN-US;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-NZ" link="#0563C1" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext">>> </span>Which in v2d would translate to "format=VDIFL/8016/2"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So the vex file has MARK5B, but two stations recorded VDIF. Drudg knowing the station setup has put the appropriate commands in the prc file to record VDIF.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Anyway I ran through the setup and tried to run it and “errmon” tells me for these files:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:windowtext">This does not look like a valid Mark5B data.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Fair enough, I see its trying to use “format=Mark8-128-2-2” and it should be “format=VDIF_8000-128-2-2” (if I use m5spec on the vdif files).
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">So I try the above line in the v2d files
</span>"format=VDIFL/8016/2" for the appropriate stations<span style="color:windowtext">, and now when I run vex2difx I get :<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:windowtext">Error: cannot change format to VDIF from any other non-VDIF format (antenna WA) with the .v2d file. You need to change the .vex file.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Hummm, a bit of a catch 22 here ?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext;mso-fareast-language:EN-NZ">Stuart Weston<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext;mso-fareast-language:EN-NZ"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:windowtext;mso-fareast-language:EN-NZ">Mobile: 021 713062<br>
<br>
Skype: stuart.d.weston<br>
Email: stuart.weston@aut.ac.nz<br>
<br>
http://www.atnf.csiro.au/people/Stuart.Weston/index.html<br>
<br>
Software Engineer<br>
Institute for Radio Astronomy & Space Research (IRASR)<br>
School of Engineering, Computer and Mathematical Sciences<br>
Faculty of Design and Creative Technologies<br>
Auckland University of Technology, New Zealand.<br>
<br>
http://www.irasr.aut.ac.nz/<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext;mso-fareast-language:EN-NZ">From:</span></b><span lang="EN-US" style="color:windowtext;mso-fareast-language:EN-NZ"> Jan Wagner <jwagner105@googlemail.com>
<br>
<b>Sent:</b> Thursday, 27 February 2020 11:58 PM<br>
<b>To:</b> Stuart Weston <stuart.weston@aut.ac.nz><br>
<b>Subject:</b> Re: [Difx-users] Question - correlate near field sources ie Spacecraft<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Stuart,<span style="mso-fareast-language:EN-NZ"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">due to the strange VDIF format error you could use DiFX utility "printVDIFheader" to verify what the headers of vygr2_wa_no0108 actually say.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Maybe the "legacy" flag is set ('L' column in printVDIFheader output would be all '1').
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In that case the frame header size would then be 16 instead of 32 bytes, and format VDIFL instead of VDIF, with a format string *possibly* of "VDIFL_8000-128-2-2". Which in v2d would translate to "format=VDIFL/8016/2".<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">And as Simone already pointed out, "vsum -s <vdif files>" could be a more convenient way of generating a file list for a set of VDIF files. Vsum autodetects the nasty details of the VDIF format.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Good luck!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jan<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Am 27.02.2020 um 04:05 schrieb Stuart Weston via Difx-users:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Well two of you asked for updates <span style="font-family:"Segoe UI Emoji",sans-serif">
😊</span> Progress so far …<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">directory2filelist:</span></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">First issue, directory2filelist doesn’t like VDIF files (Which I have for Wa and Ti) :<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">oper@ww-flexbuf-01 DiFX-2.5.2 vygr2> directory2filelist /raid0/etransfer/wa/vygr2_wa_no0108 VDIF_8000-128-2-2<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">VDIF Warning: Changing frameheadersize from 32 to 16<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">VDIF Warning: Changing databytesperpacket from 8000 to 124473216<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Segmentation fault<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">It is even more unhappy with “vbs_fs” for merging jive5ab vdif chunks into one logical file at the fuse mount point (PS: I now use “vbs_fs” for DSPSR with Williem for VDIF Single Dish pulsar data).<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">v2d :</span></b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt"> </span></b><o:p></o:p></p>
<p class="MsoNormal">Also for v2d ephemFile has to be either tle (Two-Line elements) or bsp (which I assume means BaryCenter on 399 Earth, our observing platform). Now NASA HORIZONS doesn’t seem to produce a valid file acceptable to SPICE. So goto NASA NAIF
which has some “old” archived bsp files but nothing current.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I was trying to use the HORIZONS ID “Voyager_2” , that didn’t work :<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">================================================================================<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Toolkit version: N0066<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">SPICE(IDCODENOTFOUND) --<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">The target, 'Voyager_2', is not a recognized name for an ephemeris object. The<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">cause of this problem may be that you need an updated version of the SPICE<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Toolkit. Alternatively you may call SPKEZ directly if you know the SPICE ID<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">codes for both 'Voyager_2' and '399'<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">A traceback follows. The name of the highest level module is first.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">spkezr_c --> SPKEZR<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Oh, by the way: The SPICELIB error handling actions are USER-TAILORABLE. You<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">can choose whether the Toolkit aborts or continues when errors occur, which<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">error messages to output, and where to send the output. Please read the ERROR<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">"Required Reading" file, or see the routines ERRACT, ERRDEV, and ERRPRT.<o:p></o:p></p>
<div style="border:none;border-bottom:double windowtext 2.25pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Anyway under the NAIF archive there is a “voyager_2.ST+1992_m05208u.merged.bsp” which goes to “2021 JAN05”. Now you need NAIF ID 3 for the Earth Barycenter (our observation platform) and NAIF ID -32 for Voyager 2<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">SOURCE VGR2 {<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">ephemObject = -32<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">ephemFile = voyager_2.ST+1992_m05208u.merged.bsp<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">}<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Now v2d works, there are some warnings about stop/start times for the vdif files.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">oper@ww-flexbuf-01 DiFX-2.5.2 vygr2> vex2difx --force vygr2.v2d<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Filelist file vygr_atca.filelist was a listing with no start/stop times.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Note: Future versions of vex2difx may stop allowing file lists without start/stop times. Filelists for VDIF and Mark5B files with start/stop times can be generated with "vsum -s" and "m5bsum -s" respectively.
These times allow vex2difx to properly assign data to jobs and is especially important in cases where multiple jobs are generated per project.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Filelist file vygr_dss.filelist was a listing with no start/stop times.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Filelist file vygr_wa.filelist was a listing with no start/stop times.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">start date: 2020y015d08h00m00s<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">stop date: 2020y015d12h00m00s<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: no clock values for antenna AT .<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: no clock values for antenna WA .<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: no clock values for antenna TI .<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Note: Proceeding even though there were 3 warnings.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Job vygr2 1: no clock offsets being applied to antenna AT<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> Unless this is intentional, your results will suffer!<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Job vygr2 1: no clock offsets being applied to antenna TI<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> Unless this is intentional, your results will suffer!<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Job vygr2 1: no clock offsets being applied to antenna WA<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> Unless this is intentional, your results will suffer!<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Job vygr2 2: no clock offsets being applied to antenna AT<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> Unless this is intentional, your results will suffer!<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Job vygr2 2: no clock offsets being applied to antenna TI<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> Unless this is intentional, your results will suffer!<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">Warning: Job vygr2 2: no clock offsets being applied to antenna WA<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> Unless this is intentional, your results will suffer!<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt">2 job(s) created.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I’ll come back to the <b>clock offsets</b> next as I do have those to add, I’ll append a $CLOCK section shortly.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I am just working my way through step by step, where each step will have several iterations to sort things out.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-fareast-language:EN-NZ">Stuart Weston</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-fareast-language:EN-NZ"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-fareast-language:EN-NZ">Mobile: 021 713062<br>
<br>
Skype: stuart.d.weston<br>
Email: <a href="mailto:stuart.weston@aut.ac.nz">stuart.weston@aut.ac.nz</a><br>
<br>
<a href="http://www.atnf.csiro.au/people/Stuart.Weston/index.html">http://www.atnf.csiro.au/people/Stuart.Weston/index.html</a><br>
<br>
Software Engineer<br>
Institute for Radio Astronomy & Space Research (IRASR)<br>
School of Engineering, Computer and Mathematical Sciences<br>
Faculty of Design and Creative Technologies<br>
Auckland University of Technology, New Zealand.<br>
<br>
<a href="http://www.irasr.aut.ac.nz/">http://www.irasr.aut.ac.nz/</a></span><o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:EN-NZ">From:</span></b><span lang="EN-US" style="mso-fareast-language:EN-NZ"> Stuart Weston
<br>
<b>Sent:</b> Thursday, 27 February 2020 1:51 PM<br>
<b>To:</b> <a href="mailto:difx-users@listmgr.nrao.edu">difx-users@listmgr.nrao.edu</a><br>
<b>Cc:</b> Oleg Titov <a href="mailto:Oleg.Titov@ga.gov.au"><Oleg.Titov@ga.gov.au></a><br>
<b>Subject:</b> Question - correlate near field sources ie Spacecraft</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I have some VLBI on Voyager to correlate.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">So had a read of : <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><a href="https://www.atnf.csiro.au/vlbi/dokuwiki/doku.php/difx/spacecraft">https://www.atnf.csiro.au/vlbi/dokuwiki/doku.php/difx/spacecraft</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I have setup SPICE <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Anyone done this before and any tip’s, help or suggestions ?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The ephemFile as that as obtained say from <a href="https://ssd.jpl.nasa.gov/horizons.cgi">
https://ssd.jpl.nasa.gov/horizons.cgi</a> ?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-fareast-language:EN-NZ">Stuart Weston</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-fareast-language:EN-NZ"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;mso-fareast-language:EN-NZ">Mobile: 021 713062<br>
<br>
Skype: stuart.d.weston<br>
Email: <a href="mailto:stuart.weston@aut.ac.nz">stuart.weston@aut.ac.nz</a><br>
<br>
<a href="http://www.atnf.csiro.au/people/Stuart.Weston/index.html">http://www.atnf.csiro.au/people/Stuart.Weston/index.html</a><br>
<br>
Software Engineer<br>
Institute for Radio Astronomy & Space Research (IRASR)<br>
School of Engineering, Computer and Mathematical Sciences<br>
Faculty of Design and Creative Technologies<br>
Auckland University of Technology, New Zealand.<br>
<br>
<a href="http://www.irasr.aut.ac.nz/">http://www.irasr.aut.ac.nz/</a></span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-NZ"><br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Difx-users mailing list<o:p></o:p></pre>
<pre><a href="mailto:Difx-users@listmgr.nrao.edu">Difx-users@listmgr.nrao.edu</a><o:p></o:p></pre>
<pre><a href="https://listmgr.nrao.edu/mailman/listinfo/difx-users">https://listmgr.nrao.edu/mailman/listinfo/difx-users</a><o:p></o:p></pre>
</blockquote>
<p><o:p> </o:p></p>
</div>
</body>
</html>