run balance - gets the correct answer for IF, but fails for VEGAS - maybe because of new BOF
correct value is around 500000 = 2**19 - quite different from in simulator, presumably because IF passband is flat?
set 500000 to all of banks E,F,G,H
CM values range from ~ 2 to 13dB, for -20dBm at VEGAS. Run VEGAS target from -34 to -14 - won't always balance.
leave lbw_gain fixed
run checkLinearityBalance
Scans 1 - 11
Suddenly there is much more power in the converter module outputs??? But stop here anyway.
VEGAS balance wasn't very optimal (some target values were quite off). Run checkLinearityDB by just running the converter rack through its full range of values from 0 - 30dB.
All scans after this point have no archivist files. (bug in checkLinearityDB procedure)
Scan 12 - forgot to configure
Scan 13 = 0dB
Scan 14 = 1dB etc
Scan 39 = 26dB has a huge peak in power - like someone walked through the beam or something?
Mechanics are greasing the turret...
Scan 42 has a big swing in power through it...
Scan 43 = 30dB
Decide that switching will be confusing. At the end of this, run with total power (no switching) Run checkLinearityDB with 3dB steps
Scan 44 = 0dB
Scan 48 bank E one pol has a divot out of it...
Scan 50 is horrible...
Scan 54 = 30dB
Forgot to re-add Archivist after running configure!
Reversion check
Joe reverts the BOF file to regular
Run eso558_vegas to make sure everything is working correctly.