- The script kfindwhm.script
measures focus and seeing and sets the focus to the measured value.
Run it
once or twice each night, or more, especially if the outside
temperature changes
by more than a few degrees C. Rob runs a similar script at the beginning
of each night, unless specifically told not to.
Follow these instructions to run it manually:
-
You do not need photometric or completely dark conditions to run
kfindwhm.script. Dark twilight is OK (sun at least 12 degrees below the
horizon).
-
Make sure that track and dome are on (Tele Tasks),
then type "kfindfwhm" in the command window. This command is an alias to:
"source /home/falco/findfwhm/kfindfwhm.script."
-
The script will first ask you to hit return if you're ready to start
and you want to use the default, the r filter. If you wish to use
another filter enter its name (from the list the script
shows), then hit return. You can quit at this stage by entering
X, or if you enter a filter not in the list, the script will
also quit. The
script will print out some information as it goes, more than you need,
but just in case. The script automatically looks for stars not far
from zenith at the time of observations, so the telescope should not
have to slew very far if you start near zenith.
-
The script will take a focus image with 11 10-second exposures with
focus values between +70 and -70 focus units, centered on the starting
focus value. The script analyzes the focus image for you. The total
time to run the script is about 5 minutes. If it's successful, it
will print "FINDFWHM RESULTS" and date, best focus, FWHM (in arcsec) and the
filter. It saves those values and the mirror temperatures to a running log
file (/home/observer/findfwhm/findfwhm.log). It will
also set the telescope focus to the best value it found, so there is no
need to change the focus after running the script. If it fails, it will
print "FINDFWHM FAILED" and a reason for the failure if it knows it, and do
nothing else.
Possible causes for failure are:
- Starting from a focus value beyond the range that the script examines.
Try focusing the telescope manually
first and then run kfindfwhm as described above.
- Clouds may prevent meaningful measurements.
- The script tempfocus sets the telescope focus using a line that
we fit to focus (obtained with kfindfwhm) vs.
ambient temperature data.
- We monitor focus vs. temperature and
periodically update the linear function:
Type "tempfocus" in the Telshell at the beginning of the night
to run tempfocus. Make sure that you start out close to
focus. To confirm that, first run kfindfwhm once as described
above. You may also type "deltafocus" after you've run
tempfocus once; it avoids
the larger uncertainty in the zero point for the function.
The scripts log temperature and focus values, to keep
broadening the range of validity of the function.
NEW seeing measurements:
- EF extracted FWHM values from the Robot logs for
2013, 2014 and 2015. Rob computes and records
a FWHM value for each exposure it takes.
The results show that
the image quality improved significantly after the new mirror was
installed in September 2013:
The quality was better in the first half, compared to the
second half, of 2014:
The quality was again better in the first half of 2015, but
the onset of El Niño made the second half significantly worse:
The FWHM history
documents these measurements of FWHM.
Old calibrations and seeing measurements:
Consistent with Deb Woods' 2006
WFS analysis of the 1.2m primary,
the seeing we measure with Keplercam and the r filter
has deteriorated compared to previous measurements:
- 4shooter calibration:
Minicam calibration:
- We obtained seeing measurements between 03/24/03 and 10/24/03,
thanks to many observers who used findfwhm with 4shooter.
The results show that,
in spite of our controlling the temperatures of the primary mirror,
the seeing has not improved significantly:
The solid histogram includes all the measurements, while the dashed
histograms show measurements taken when the temperature
difference between the mirror and the chamber was below 0.5C, or
when the measurements were made in the middle of the night. The
different histograms show little difference in the median seeing
of about 1.6 arcsec.
The plot below is a histogram of the maximum temperature difference
between sensors on the mirror and sensors in the chamber. The peak is
at 0.3C.
- EF measured the seeing on frames taken as part of the Hectospec
survey, BH (before Hexapod). The data were uniform: R filter,
10-minute exposures. Here is a histogram of those values for the
period Feb-May 2001 (with the old pod). The solid (dashed) histogram
is for exposures taken at hour angles < 2h (> 2h).
- EF also measured the seeing on frames taken as part of the
Hectospec and Mass Function surveys, AH (after Hexapod). The data
again were reasonably uniform: R filter, 5 to 10-minute exposures.
Here is a histogram of those values for the period Sep 2001-May 2002
(with the hexapod). The solid (dashed) histogram is for exposures
taken at hour angles <2h (>2h).
The two histograms above show there are interesting
differences for data taken with
the old pod and the new hexapod :
- The peak for hour angles <2h for the hexapod is at 1.4 arcsec,
while for the pod the analogous peak is at 1.6 arcsec.
- The peaks for hour angles <2h and >2h coincide for hexapod,
whereas the analogous peaks for the pod are displaced from
each other by 0.1 arcsec. We
interpret this effect as the result of an improved
hold of collimation by the hexapod, compared to the pod.
- The histogram for the hexapod is somewhat broader than that for
the pod. We interpret that as the result of degraded weather toward the
end of 2001 and the beginning of 2002.
The first two items above indicate there was some improvement in the
1.2m seeing thanks to the hexapod. Work will continue to try to improve
the seeing further.
- In 1995, EF measured the seeing on frames taken as part of the FKS
search for lensed quasars (Kochanek, Falco and Schild 1995, ApJ 452, 109).
Here is a histogram of those values.
To 1.2m home page