<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Another observation: The code is indeed swapping IFs (only when it
must), and it is aware that each IF pair may have had a different BW.
It is using the correct BWs to calculate SSLOs. HOWEVER, it is not
communicating the swap to other places that need to know, namely the
part of the code that creates these lines in the script:<br>
<br>
<pre><code><span class="iceOutTxt" id="mainForm:_id682:0:_id1169">corrmode.setBandwidth(0,3,0,3)
</span></code><code><span class="iceOutTxt"
id="mainForm:_id682:0:_id1169">vlaloif.setBandwidthA(0)
vlaloif.setBandwidthB(3)
vlaloif.setBandwidthC(0)
vlaloif.setBandwidthD(3)
</span></code>
</pre>
I'll fix this later today and also suggest some tests that exercise
this code.<br>
<br>
David Harland wrote:
<blockquote cite="mid:497904C4.6010703@nrao.edu" type="cite">I should
have mentioned that the OPT is probably missing a test that would warn
the user that the lowest A/C frequency for Ka band is 32GHz. I'll look
into that and update the code if it is indeed missing. --David
<br>
<br>
<br>
Gustaaf Van Moorsel wrote:
<br>
<blockquote type="cite">During software time I tested tuning the IF
pairs more than 4 GHz apart.
<br>
During 30 minutes I observed the following scans in spectral line, BW
<br>
code 1, 25 MHz bandwidth, 1.56 MHz channel width. The schedule was
<br>
created using the OPT.
<br>
<br>
1 - dummy scan at X-band, continuum
<br>
2 - reference pointing determination, X-band, continuum
<br>
3 - K-band, AC at 20.5 GHz, BD at 25.5 GHz
<br>
4 - Ka-band, AC at 36.0 GHz, BD at 30.0 GHz
<br>
5 - Ka-band, AC at 38.0 GHz, BD at 28.0 GHz
<br>
6 - Q-band, AC at 49.0 GHz, BD at 42.0 GHz
<br>
7 - Q-band, AC at 42.0 GHz, BD at 49.0 GHz
<br>
8 - Ka-band, AC at 30.0 GHz, BD at 36.0 GHz
<br>
<br>
The observations were successful: scans 1 - 6 were observed, whereas
scan
<br>
7 and 8 were not; not surprising since they (on purpose) violated the
req-
<br>
uirement that the AC frequency has to be greater than the BD frequency.
<br>
The OPT should probably check for those constraints.
<br>
<br>
Notes:
<br>
<br>
1 - In scan 3 (K-band) the system accepts freq(AC) < freq(BD) but
AIPS
<br>
labels the higher of the two frequencies as IF 1, an the lower as IF
<br>
2. How do we make sure the right data is attributed to the right
IF?
<br>
<br>
2 - AIPS labels the IF pairs with a slightly different frequency than
req-
<br>
uested in the OPT. For instance, in scan 4, AC requested is 36.0
GHZ,
<br>
AIPS labels it as 36.00078125 GHz, a difference of half a channel.
BD
<br>
requested is 30.0 GHz, AIPS labels it as 30.02421875 MHz, a
difference
<br>
of 15.5 channels. This needs to be sorted out.
<br>
<br>
Gustaaf
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>