<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi all,</p>
<p>In case anyone is interested, here is a bried update on this
issue (missing baselines in mixed-pol setup when not using
zoombands): Since a while ago, I believe the problem is not the
mix of polarisations, but rather the mix of USB/LSB. The ON
station is recording USB BBCs while the OE and OW stations record
LSB BBCs. I have been told there is a bug/feature in difx2mark4
with mixed USB/LSB data, where difx supposedly writes two
frequency tables, but difx2mark4 only reads the baselines matching
one of them. This is a likely explanation for why I seem to lose
the OE-OW baseline; it is the only LSB-LSB configuration, while
the USB-LSB baselines (OE-ON and OW-ON) are kept. Using zoombands,
it seems the output is forced into one frequency table and thus no
problem for difx2mark4 et al. <br>
</p>
<p>Kind regards</p>
<p>Eskil<br>
</p>
<div class="moz-cite-prefix">On 2021-02-04 18:09, Eskil Varenius
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3250888B-8E87-4B91-9695-A0CD08F4BDF0@chalmers.se">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@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;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="SV">Hi Adam, all<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="SV"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Finally some data so I can return to the
mixed-pol issue again. To remind you, my problem is that
when correlating R-pol (1Gbps) data from ONSALA60 against
X/Y-pol (2Gbps) data from ONSA13NE and ONSA13SW, I must
define “zoom bands” to get visibilities on all baselines.
Not sure if the problem is in DiFX, or difx2mark4 (or
elsewhere). I have uploaded a tar.gz archive with
input/output files (excluding 18GB of VDIF data) at<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><a class="moz-txt-link-freetext" href="https://chalmersuniversity.box.com/s/9ed0t61bk04ag88is2ovhlm0er4qd00n">https://chalmersuniversity.box.com/s/9ed0t61bk04ag88is2ovhlm0er4qd00n</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">There you can check logfiles, input files etc.
If you want the data, I can share it (no time right now to
remember how to split out a small chunk of data for testing,
so used one full 30 sec scan). I can also try various things
on my end if you have suggestions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Here are the steps to reproduce with DiFX
2.6.2:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Unzip archive,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Edit "*.files" with correct paths to "data"
directory<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">cd zoom<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Edit "on1028_1.machines" accordingly (e.g.
computer name)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">vex2difx -v -v -v -d *v2d --force (need force
as this is mixed circular/linear data)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">calcif2 *.calc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">startdifx -n -f *.input -v<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">I now get messages, see logfile, like<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">"Thu Feb 4 17:56:58 2021 0 skirner WARNING
Baseline 0 frequency 0 points at two different frequencies
that are apparently identical - this is not wrong, but very
strange. Check the input file"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">The message is correct, I have identical zoom
windows - otherwise I don't get all baselines. To see
result, I run<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">difx2mark4 -v -b X 2300 14000 *.difx -s
../station_code_file.txt<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">and check the output on screen. All baselines
are included:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">[...]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[SX] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[ST] 896<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[XT] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[SS] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[XX] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[TT] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">[...]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Same procedure without zoom-windows, I get a
different set of baselines<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">[...]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[SX] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[XT] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[SS] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[XX] 224<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"> n120[TT] 448<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">[...]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Curiously, the "ST" (which is the ONSA13NE-SW
baseline) is missing, and the XX (ONSALA60) is half (224).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Not sure the zoom-window version is correct,
but I need the ST-baseline, and it seems to work, so I use
zoom-windows. But, I'm curious: why does this happen?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Kind regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"
lang="EN-US">Eskil<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:12.0pt;color:black">From: </span></b><span
style="font-size:12.0pt;color:black">Difx-users
<a class="moz-txt-link-rfc2396E" href="mailto:difx-users-bounces@listmgr.nrao.edu"><difx-users-bounces@listmgr.nrao.edu></a> on behalf of
Eskil Varenius via Difx-users
<a class="moz-txt-link-rfc2396E" href="mailto:difx-users@listmgr.nrao.edu"><difx-users@listmgr.nrao.edu></a><br>
<b>Reply to: </b>Eskil Varenius
<a class="moz-txt-link-rfc2396E" href="mailto:eskil.varenius@chalmers.se"><eskil.varenius@chalmers.se></a><br>
<b>Date: </b>Monday, 30 November 2020 at 11:51<br>
<b>To: </b>Adam Deller <a class="moz-txt-link-rfc2396E" href="mailto:adeller@astro.swin.edu.au"><adeller@astro.swin.edu.au></a><br>
<b>Cc: </b><a class="moz-txt-link-rfc2396E" href="mailto:difx-users@listmgr.nrao.edu">"difx-users@listmgr.nrao.edu"</a>
<a class="moz-txt-link-rfc2396E" href="mailto:difx-users@listmgr.nrao.edu"><difx-users@listmgr.nrao.edu></a><br>
<b>Subject: </b>Re: [Difx-users] A few surprises<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>Hi Adam,<o:p></o:p></p>
<p>Apologies, but I will have to defer sending additional
details as the data in question have already been removed
after correlation. (I would like to verify that the files I
send indeed produce the errors I claim, so I don't send files
with other typos). Also, I have too many other todo-items to
follow this up right now, but we regularly observe with
similar settings so I should get another data set to play with
in a few weeks. When I do, I will check the input-file
differences and let you know, and keep the data on disk for
additional tests. But I did experience the same thing for all
similar data so far. Will let you know once I have new data.<o:p></o:p></p>
<p>Cheers<o:p></o:p></p>
<p>Eskil<o:p></o:p></p>
<div>
<p class="MsoNormal">On 2020-11-30 11:43, Adam Deller wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hi Eskil, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks for the heads up, the first
two are surprising (I'm never surprised by gaps in
documentation!) <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I've got no experience with the intel
compilers, so will pass on that one. For the second,
what is the difference in the .input file produced by
vex2difx in the two cases? That might help shed some
light.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Adam<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, 30 Nov 2020 at 21:18, Eskil
Varenius via Difx-users <<a
href="mailto:difx-users@listmgr.nrao.edu"
moz-do-not-send="true">difx-users@listmgr.nrao.edu</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0cm 0cm 0cm
6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Dear difx developers,<br>
I have noted a few surprises which I would like to
report:<br>
<br>
- Compiling DiFX 2.6.1/2.6.2 with intel 2019 compiler,
mpifxcorr runs <br>
but refuses to actually read any data. It just sits
there, never <br>
starting the correlation. Using intel 2018 compiler
instead, everything <br>
works nicely.<br>
<br>
- Correlating mixed-polarisation data (antenna ON:
R-pol, OE and OW: X/Y <br>
pol) delivers correlation products on the mixed
circ/linear baselines <br>
(R-X and R-Y pol), but not on the linear/linear
baselines (XX,XY,YX,YY). <br>
However, if I add zoomwindows - describing the same
setup already in the <br>
VEX file, so no actual zooming - then I get also the
linear polarisation <br>
products. (I know mixed-pol support is limited, but
might as well note <br>
the behaviour.)<br>
<br>
- "difx2mark4 --help" v1.6 does not say it needs .calc
files, but seems <br>
it does. So documentation should be amended?<br>
<br>
Kind regards<br>
Eskil<br>
<br>
_______________________________________________<br>
Difx-users mailing list<br>
<a href="mailto:Difx-users@listmgr.nrao.edu"
target="_blank" moz-do-not-send="true">Difx-users@listmgr.nrao.edu</a><br>
<a
href="https://listmgr.nrao.edu/mailman/listinfo/difx-users"
target="_blank" moz-do-not-send="true">https://listmgr.nrao.edu/mailman/listinfo/difx-users</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">!=============================================================!<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">A/Prof.
Adam Deller <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">ARC
Future Fellow<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">Centre
for Astrophysics &
Supercomputing <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">Swinburne
University of Technology <br>
John St, Hawthorn VIC 3122
Australia<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">phone:
+61 3 9214 5307<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">fax:
+61 3 9214 8797<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">office
days (usually): Mon-Thu<br>
!=============================================================!<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>