07/06 SHARP Beam calculations

Beam calculations were made using three sets of Uranus (chopped) data. Group 1 data was pointed directly at Uranus, while Groups 2 and 3 had a 15 arcsecond az offset, +15 for Group 2 and -15 for Group 3.

Using integ, four hwp files were combined to create one fits image. From the output of integ, we also noted the high and low chopper positions for each hwp position, and the difference between the two. (We also noted the maximum pixel intensity along with its position.)

For each group, we calculated the average chop pointing (chop high + chop low) and then for each file calculated four chop pointing offsets (chop ptg -avg(chop ptg)). We also calculated the rms chop error for each file (300-chop diff).

With this information, we eliminated files from further analysis based on the following criteria:

1. chop pointing offset > 1.0
2. rms chop error >= 3.0
3. looking in fits V image, eliminated files with bad pixel row

After these files were eliminated, we broke up the remaining files in each group to two subsets, a and b.

Each file in the subset was processed through quicklook (creating h and v files), and all of the files in the subset were then combined by the 'sum' function. The resulting h and v fits files were then processed by fitgauss to create the beam FWHM.

Note: Groups 2b and 3a are messed up. I put them in for documentation purposes, but you can ignore them.

jpg images of h and v arrays:

• h_sum1a
• v_sum1a
• h_sum1b
• v_sum1b
• h_sum2a
• v_sum2a
• h_sum2b
• v_sum2b
• h_sum3a
• v_sum3a
• h_sum3b
• v_sum3b

Dead pixel masks

• H
• V