Tracking Test

Propose to reserve 2.5 hours on both K1 and K2 for autoguider/servo tests

First, I would like to collect data on open-loop tracking ability of the telescope. Second, I would like to run an autoguider test (not yet developed) to verify the response time of the autoguider/DCS loop. I think both tests can be done within 2.5 hours. The first part is a standard PM, the second is driven by MAGIQ, and is needed to pin down several specifications. We could get by with running the second part on just one telescope, if time is really tight.

1. Name of principal investigator, PI, and other personnel involved in observing, data reduction, and test reporting.
Tom Nordin
2. Purpose of test (development project, general telescope engineering, instrument commissioning, problem trouble shooting, data quality, training, etc.)
Telescope servo performance verification
3. Test number (from "remedy") if applicable.
Part 1: 463, Part 2: Not yet written
4. Test duration in hours (time requested).
2.5 hours per telescope
5. Brief description of test.
See above
6. Telescope/instrument configuration required.
F/15, tertiary, SSC (or similar)
7. Plan for data reduction, analysis, and reporting.
Part 1: Straightforward, Part 2, No idea yet
8. Preferred dates of observations and dates to avoid.
Could be put into the queue for a non-windy night.
9. Status and progress reports from previous use of engineering time.
This data will be used to support design decisions for the MAGIQ autoguider.