What is IO?

IO (Infrared-Optical) is a suite of instruments which replace the RATCam and SupIRCam cameras. The primary aims are to provide wider fields of view and improved image quality. Ultimately their design allows the ability to simultaneously image in the optical and IR bands, though this is not yet funded.

IO:O

IO:O

Introduction


IO:O is the optical imaging component of the IO (Infrared-Optical) suite of instruments, and is a replacement for RATCam that has been the workhorse optical camera for many years. It provides a wider field of view and greater sensitivity than RATCam, and when combined with IO:I may eventually allow the ability to almost simultaneously image in both optical and near-infrared bands.

Current Status

Online
Last updated: 23 August 2016

IO:O was originally equipped with a Fairchild 486 CCD detector. However, this was found to have degraded during storage resulting in poor blue Quantum Efficiency (QE), so it was therefore replaced in June 2012 with an e2V CCD 231-84. This has worked well giving broadly similar performance to RATCam but with the advantage of a wider field of view. Read noise is currently slightly higher than RATCam with QE tilted more towards the red end of the spectrum. At present a single readout mode is implemented, giving a readout time of 13 seconds (2x2 binned). 1x1 binning is also available, although we do not regularly obtain 1x1 flats. Please contact the LT Support Astronomer if you wish to use this mode.

Specifications


IO:O is equipped with a large diameter Uniblitz iris shutter. This results in a different exposure time between the centre and edges of the field of 80ms. For reasonable photometric accuracy exposure times should therefore be greater than 20 seconds. Please feel free to discuss this issue with the LT Support Astronomer should you require short exposure times. It is of course possible to defocus the telescope so that bright targets can be observed.

IO:O's other specifications are listed below.


Detector 4096x4112 pixel e2v CCD 231, deep depletion, Astro ER1 coated
Pixel size 15.0 x 15.0 microns
Pixel scale approx. 0.15 arcsec/pixel (unbinned)
Field of view 10 x 10 arcmin
Read noise < 8 electrons
Dark current < 0.002 e / pix / sec (unbinned, 263K)
~ 0.01 e / pix / sec (unbinned, 273K)
Binning 1x1 and 2x2
Readout time1 ~37 sec (1x1 binned), ~13.5 sec (2x2 binned)
Windowed modes Not currently available
Bad pixels 6 dark point defects; 2 hot pixels; 1 column defect. (pixel mask)
Gain (1x1) 1.6 electron / ADU
Gain (2x2) 1.6 electron / ADU
Quantum Efficiency
(figures supplied by manufacturer)
Wavelength
(nm)
Quantum Efficiency
(%)
350 43
400 59
500 83
650 97
900 56

1Note: the readout time is not necessarily equivalent to the overhead between consecutive exposures,
even when taken with the same filter - see below.

Filters


IO:O uses a single, 12 position filter wheel. The wheel is mounted outside the instrument; the IO:O dewar attaches to a plate below the wheel.

The wheel contains a selection of Sloan (u',g',r',i',z'), Bessell (B and V) and narrow-band filters (Hα rest wavelength and Hα redshifted to 663.4nm, 670.5nm, 675.5 nm and 682.2 nm).

Removal of Hα 682.2 nm

Being the least-requested filter, the Hα 682.2 nm slot has been used intermittently to test alternative instrument configurations. If you require this filter contact the support astronomer to ensure it is currently available.

Current status: installed.

Removal history:

  • 20 Oct 2014 - 24 Apr 2015: removed to make way for an uncharacterised "V+R" broad-band filter (GG475+KG3) used for tracking of the GAIA Space Telescope.
  • 30 Jun 2015 - 20 Oct 2015: removed in favour of experimental polaroid.

Filter profile plots

Profile plots for each filter are displayed below (click for bigger versions).

Sloan
Bessell

Plain text files of most of these filter profiles are also available:
SDSS-U
SDSS-G
SDSS-R
SDSS-I
SDSS-Z
H-alpha (rest frame)
H-alpha (redshifted to 663.4 nm)
H-alpha (redshifted to 670.5 nm)
H-alpha (redshifted to 675.5 nm)
H-alpha (redshifted to 682.2 nm)

Standards


A standards observation programme similar to that previously used with RATCam is in operation. Broad-band images of calibration fields drawn from the SDSS Extended Northern+Equatorial u'g'r'i'z' Standards are obtained every 2-3 hours. They are spaced every few hours of RA and are observed in all bands. These data are available to all observers via the LT data archive under the Proposal ID IOOStand or, for observations obtained within the past month, from the Recent Data page.

If you require standards beyond those routinely taken by the robotic system, you must request them explicitly in your Phase 1 proposal and include the appropriate observations in your Phase 2 sequence definition. The time needed for these observations should also be included in your application.

Sensitivity & Saturation


Our Exposure Time Calculator should be used to estimate exposure times to be used with IO:O.

IO:O replaced RATCam as the work-horse optical imager at the LT in late 2013. The relative sensitivity of the two instruments is plotted below, where the X axis is Wavelength in Angstroms and the Y axis the relative photon count rate for IO:O divided by the photon count rate for RATCam. This plot demonstrates that the e2V detector in IO:O appears to be slightly worse in the blue though considerably better in the red than the detector in RATCam.

In terms of IO:O's saturation limit, an r~12 star will saturate the detector in 10 sec (minimum recommended integration for 1% photometry) under the best seeing conditions typically observed at ORM. Users with target brighter than 12th mag should consider defocusing the telescope.

Observing Overheads


To the calculated exposure time (Te) the following overheads must be added:

  • Acquisition time, Ta - time taken to slew the telescope on target. This is 60 seconds.
  • Autoguider acquisition, Tg - only if you nominate to use the autoguider. This is 45 seconds.
  • Filter change time, Tf. This is 15 seconds.
  • Readout time, Tr. Assume that this is 18.5 seconds for 2x2 on-chip binning (this includes 5 seconds at the start of each exposure when FITS header information is sent from the telescope and written to the file header).
Example
Suppose you have a programme with 21 objects which you wish to observe (guided) for 10 nights in a row, with an exposure time of 60 seconds, through three different filters.
  • For one 60 sec exposure only (i.e. only one filter), the total time T1 is
      T1 = Ta + Tg + Tf + Te + Tr = 60 + 45 + 15 + 60 + 18.5 = 198.5 sec
  • However for three exposures of the same object, where a different filter is used each time (nf = 3), the total time spent on the object Tobj is:
      Tobj = Ta + Tg + nf(Tf + Te + Tr) = 60 + 45 + 3(15 + 60 + 18.5) = 386 sec

    Note that the slew and guider acquisition time is only applied once; no slewing is required after the first exposure because the telescope is already on target.
  • For twenty-one different objects (nobj=21) slewing between each object, per night for ten nights (nN=10), the total time Ttot is:
      Ttot = nN nobj Tobj = 10 x 21 x 386 = 80955 sec = 22.5 hours

Using IO:O


Guidelines on how to prepare observations are given in the Phase 2 web pages. Note in particular the instrument-specific User Interface Instructions. The phase 2 "Wizard" should always be used to prepare observations. Groups that can not be prepared with the wizard should be discussed with LT Phase 2 support. Note that LT staff do not routinely check observing groups, and that observing groups are potentially active as soon as they are submitted. Please do contact us if you have any questions about your observations.

up to top of page

RTML and Automated Followup


IO:O can accept observation requests formated in Remote Telescope Markup Language (RTML) which allows you to automatically trigger certain observations from within your own autonomous software. We provide a command line based utility which can format RTML packets for you, making it easy to integrate observing requests into a shell script or other data processing pipeline. For some use cases it might also be easier for users to upload all their observing requests from the command line instead of using the phase2ui. The facility is available to all users who have TAG-awarded time allocations. Please contact us if this sounds of interest and we can provide full user instructions.

Data Reduction Pipeline


Basic instrumental reductions are applied to all IO:O images before the data are passed to users. This includes bias subtraction, trimming of the overscan regions, and flat fielding. A library of the current calibration frames is maintained as part of the data archive and updated daily so that images are always reduced using the latest available flat-field image.

Each of the operations performed by the pipeline are described below.

  • Differential amplifier read


    IO:O uses a 'dummy' read-out circuit which is identical and in parallel with the signal read-out except that it is not connected to the detector read-out register. This provides a differential reference signal to which the data signal is compared to reject common mode noise. Rather than apply the noise rejection in hardware, a 'dummy' image is stored in the raw FITS file and subtracted off by the data reduction pipeline. It thus functions effectively like a bias image taken pixel-perfect simultaneously with the image data. The differential image is linearly scaled by an empirically determined constant before subtraction in order to minimise the common mode noise in the final result.
  • Bias Subtraction


    Bias subtraction is based on analysis of the overscans on either side of the image. Various options exist in the pipeline software but the simplest — a single constant bias value for the entire image — has proved to be most effective and robust because any spatial structures, ramps etc have already been removed by the differential image subtraction. When multiple read-out amplifiers are being used, a single bias level is deteremined spearately for each one.

  • Overscan Trimming


    The overscan regions are trimmed off the image leaving a 2048x2056 (assuming 2x2 binning) pixel image. The overscans are not included in the reduced data products.

  • Dark Subtraction


    This is not currently performed though the facility exists in the reduction pipeline if required. At operating temperature (-110C) the dark current is less than 0.002 electron / pix / second which is not significant for most purposes. If you feel you need a dark frame, please contact us.

  • Flat Fielding


    Twilight flats are automatically obtained every evening and morning. From five to seven frames are typically obtained, dithered on the sky, and a master flat created as a median stack of the frames. In the pipeline the appropriate master flat field is selected from the library to match the filter and binning configuration of the current exposure. The library actually holds reciprocal flat-fields normalised to unity because of the computational efficiency of multiplying rather than dividing; the image data are therefore multiplied by the library flat.

  • Bad Pixel Mask


    No cosmic ray rejection or bad pixel mask is applied since it is important for users performing accurate photometry to know exactly what masking has been applied. The bad pixel masks linked below are not applied or used in any way by the pipeline but are instead made available to observers for their own use. They were generated from g',r',i',z',V twilight flat fields by flagging pixels which differ from their neighbours by more than 20%.

  • Fringe Frames


    Fringing on IO:O is always weak and only significant at all in the z' filter. We currently do not perform any automated defringing of CCD data before these are loaded into the archive. However, prepared master fringe frames created by stacking multiple deep integrations of blank fields are available below. Note that the fringes on the IO:O CCD vary on timescales of months, so these data are updated infrequently. If you need access to the individual integrations used to build these master fringe frames, they are publicly available from the data archive. Simply select IOOFringe from the Proposal ID drop-down list. In this way users can extract the most recent fringe frame from the archive at any time.

    Fringe Frames for the previous detector were obtained 9th Feb 2012. We have not yet published fringe frames for the new e2V detector.

    Fringing with the e2v chip is at a very low level and can not be seen for example in individual i band frames. A slight hint of fringing can be seen in long exposure z band frames. Given the low level, until a larger data set is obtained we can not create or distribute meaningful fringe frames.

up to top of page