The Agile window provides complete control over the Agile high-speed photometer.
Much of the window is the standard Expose Window; only Agile-specific items are described in this document.
Note: unlike many other instruments, Agile has no separate configuration window. This is because Agile has no static configuration, except for the current filter. All other parameters are specified as part of the command that starts an exposure sequence.
Extra Controls
- Gain: CCD amplifier gain; one of Low, Medium or High
- Read Rate: CCD pixel readout rate: one of Fast or Slow. This is a crucial parameter for short exposures because your minimum exposure time is the image readout rate plus a small overhead for image file handling. If you find your exposure is rejected because the exposure time is too short then you can try increasing the readout rate, increasing the bin factor, reducing overscan or windowing the image.
- Filter Wheel: controls for the Agile filter wheel.
- Filter Slide: information about the filter in the filter slide, or Out if there is no filter in the slide. This information is read only because the filter slide is manually controlled.
Environmental Status
Environ toggles detailed display of environmental details. The associated string is a summary of the current status. Details that the Environ button exposes include:
- Camera: state of camera connection. This is important because the camera is disconnected and reconnected after every exposure sequence (to work around a data corrupting bug in Princeton Instruments' PVCam library) and you cannot command an exposure unless the camera is connected. It takes about 30 seconds for reconnection. If you find it annoying then please complain to Princeton Instruments; maybe if enough people do so they will actually fix it.
Call PI at 609-587-9797 and ask to speak to Rob Allen (leave a message) or email him at RAllen@piacton.com. Agile is a VersArray 1024 Frame-Transfer camera with a USB interface on a Linux system. The bug is that if the camera will corrupt data with a band of zeros if used to take multiple sequences of exposures without closing the camera between sequences. Russell Owen first reported it 2008-12 (or perhaps a bit earlier) and supplied simple test code that reproduces the problem.
- CCD Temp: the current CCD temperature.
- CCD Set Temp: the desired CCD temperature.
- CCD Temp Limits: CCD temperature limits as four values: low, high, very low, very high.
- GPS Synced: is the timer card synced to the site's GPS clock? If not then you cannot rely on the timing of externally synched exposures.
- NTP Status: status of the NTP client. If the status is bad then then you cannot rely on the timing of externally synched exposures. The status is reported as three fields:
- State of NTP client (Running is the desired state)
- NTP server (as of this 2009-07-09 uses galileo)
- Stratum of NTP server (should be 1 or 2)
- Filter Wheel: is the filter wheel controller connected? If not, you will not be able to control the filter wheel. To connect the filter wheel controller, issue this command in the command bar at the bottom of the Log window:
agile connDev fw.
- Filter Wheel Motor: status of filter wheel motor and controller. To home the filter wheel controller, issue this command in the command bar at the bottom of the Log window:
agile fwhome (there must be a filter wheel mounted in Agile for homing to succeed).
Sound Cues
Agile is capable of taking very short exposures and sound cues are maddening if played too often; so the "exposure begins" sound cue is played at most once every 30 seconds. Also, Agile is a frame-transfer camera, so the end of each exposure marks the start of the next exposure. Thus the "exposure ends" sound cue is never played. (Eventually I hope to play it once at the end of an exposure sequence.)
See also these references at APO: