Sections:

---

Intro

• The median power level settting for each strip. The units are Measured/Optimum power. The values should be within 20% of unity for optimum sensitivity with 3 level sampling.
• The stability of the system is monitored using the median strip power for each strip taken during the day. The power by strip, the cal scale factor for each strip, and the cal corrected power for each strip are plotted. The first two show how fast the electronic gain is changing. When multiplying these two, the 3rd plot (cal corrected power) should be stable with time.
• The total power for each 1 second  sample is plotted for the first 10 strips of each day. You can see sources drifting through the beams. Occasionally you will see jumps in total power with long recovery times. These are caused in our system by the FAA radar. Some of the pixels also look "noisy" then the others.

---

How the data is processed: (top)

1. compute the rms/mean by channel for n secs (1200) seconds worth of data. There must be a cal record in the file for the file to be processed.
2. Do a robust linear fit to the rms/mean by channel throwing out outliers. The remaining channels will be the mask used to compute the total power for each spectra of the 1200 seconds (and the cal).
3. compute the  total power (mean) for each 1 second record using the above mask.
4. Over the entire strip compute the median of the total power using the data from 4.
5. Compute the cal scale factor : calK/(calOn-calOff). For the cal off use the last record of the strip (the one before the cal on). If the next strip starts within 6 seconds of the cal record, include  the first record of that strip for the calOff. If there are two cal offs,  interpolate their total power to the cal On time (if not, just use the single cal off.
6. Scale the total power data (from 4) to kelvins using the cal scale factor.
7. Save the following to disc (one save file per day). assume there are NstripsTot total strips:
• tpIAr[nstripsTot] (tpI struct), brmsAr[nstripsTot] (corget struct) ,bcalRAr[nstripsTot] (corget struct), and maskAr.

TpI struct:

   SCAN            LONG         503514951
   FNAME           STRING    '/proj/a2010/wapp.20050204.a2010.0007.fits'
   NPNTS           LONG               1200
   RMSFITA         FLOAT     Array[2, 7]   (ao + a1*channum) fit torms polA
   RMSFITB         FLOAT     Array[2, 7]   (ao + a1*channum) fit to rms polB
   MASKFRACT       FLOAT     Array[2, 7]   (fraction of band each mask contained)
   TPCORA          FLOAT     Array[1200, 7] (tot power deg K each point (polA)
   TPCORB          FLOAT     Array[1200, 7] (tot power deg K each point (polB)
   TPMEDIAN        FLOAT     Array[2, 7]   (median tot pwr each strip cor Units (a,b)
   CALK            FLOAT     Array[2, 7]   (calval degK for [pols,pixels])
   CALSCL          FLOAT     Array[2, 7]   ( calK/(calOn-calOff) tp [pols,pixels]
   NCALOFF         FLOAT           2.00000 (number of cal offs used)
   AZ              FLOAT           359.638 ( azimuth feed)
   ZA              FLOAT           9.22350 ( za )
   JD              DOUBLE           2453405.3 (jd start of strip)
   ALFAANGLE       FLOAT           18.9999 (alfa rotation angle)

•  bcalRAr . This is a corget struct holding the calon/caoff spectra for each cal
•  maskAr . This holds  the masks used to compute the total power.

The save files can be input and merged using inpsav.pro. This routine creates one large array of tpI structs. It only takes strips that have 1200 seconds worth of data.

---

Median power for each strip. The system stability: (top)

    For each month the median power, calscale factor, and Tsys are plotted for each strip taken. The four sets of plots are:

• Col 1: The median power for each strip versus date.  The plots span 2 pages. Data is in correlator units (measured/optimum power level). It has not been scaled by the cals. This data shows when the data was taken and whether the power levels setting of the wapps were ok.  The  dashed line is at +/- 20% from optimum (1 db off). The power level can be adjusted in 1db steps at the wapp input. The optimum value  should be 1. .
• Col 2: The median power level of each strip is plotted versus the strip number for the observing run. Each plot is divided by the median value for the observing run (and 1 subtracted) to show the fractional change in power. This data has not been scaled by the cals so changes in level could be from sky, gain variation, or a change of the attenuator setting during a run. Each pixel is plotted on a separate page. Consecutive days are offset for plotting with the yymmdd label on the right. The dotted lines are spaced by 5% of Tsys.
• Col 3: The cal scale factor for each strip is plotted versus the strip number for the observing run. This value converts from correlator counts to degrees K for each strip. The data is computed as :  CalK/(calOn-calOff) .  Each plot has been divided by the median value (and 1 subtracted) to show fractional changes. Variations in this value will occur because of gain variations or sky changes between the calOn and the calOff (sources drifting through). Each day is offset for plotting and labeled with yymmdd on the right.
• Col4: The median strip power corrected using the cal value (from col 3) is plotted versus stripnumber of day. The multiplication by the cals should get rid of the electronic gain variation of the system. The median power is an estimate of the average value of the power in a strip. The cal scale factor is measured at the end of the 1200 seconds. If there is a linear gain change then the plot will be flat (but offset). If there is a non-linear change in the gain then there will continue to be curvature in these plots.

• jan08 alfa reinstalled after painting..

• apr07 alfa brought down to lab for maintenance.

---

1 second total power samples vs position in strip  (top)

Notes 2013

• jan13: beam0a. slow gain variation (300-500 secs) 28,29,30,31jan13
• mar13:
  
• 01mar13: bm0a drifts a little.
  
• 13mar13 strong rfi across all beams?
  

• jan12
• 0b:1,2,3 jan .. jumps,drifting, unstable
• 2a: 4jan unstable
• 4b: 15jan  unstable
• feb12:
• 0b  dropouts 3,7,19 dropouts.
  
• may12:
• 1b  baseline changes: 31may
  
• jun12:
• 1b:
•  long recovery from radar 02jun
  
• baseline changes 3%: 03,04,14
  
• jul12:
• 1b: baseline changes 2-3%: 14,17,19 jul
  
• aug12:
• 22aug12.. iflo setup incorrectly. bad data.
• 1b:
•  long recovery from radars: 25aug12
• wandering in value about 3% of Tsys 27aug
• dec12:
  
• 10dec: no sky signal.
  

• jan11: 02jan11 5a,b jump
• 23mar11: beam 6a died..
• apr11: beam1b jumping around.
• 28nov11: beam2a jumped
  
• dec11:
• beam2a jumping around:06,09,10,14,15,16,17,18,30,31dec11
  

• 10xxxx: 2a is noisier than the  other beams. higher tsys.
  
• 1001xx:
• 31jan10 beam 5b jumping around.
• 1010:
• 6b dead
• 2a is noiser.
• 1011:
• 101105: punta salinas in all modes.
  
• beam 5b jumping, wandering up to 3%
• dates:07,10,11,12
• 1012:
• 101209: bias card 5 adjusted. small changes to 2.
• 2a unstable: 11dec10,12dec10
• 5a,b still jumps around: 10,12dec
  

• 0901xx:
• Bm 1b jumps/wanders:jan: 17,18,19,20,22.
  
• Bm5b:jan:18,20
• 0902xx:
• Bm 5b drifting feb:27,28.
• 0903xx:
• Bm 5b drifting/jumping 1-5% mar:06,07,08,09
• 0906xx
• bm 5b jumping around.
  
• 0907xx
• bm 5b drifting/jumping around.
• 0911xx
• 05-13nov beams 4-6 trouble while biases adjusted
• beam2a: higher tsys. jumping,05,24nov09.
  
• 0912xx
• 23-29dec beam 2a occasionally jumping

• 080430: beam0b jumping around most of april
• nov08: 1b is jumping a lot. long recover times and sometimes just random  jumps.
• dec08: 19-21dec08 beam 2b looks a little unstable.
  

 home_~phil