The OSIRIS User's Manual
[Main Index]

Known OSIRIS Problems (or "Features")

This page will list known problems with the instrument and (hopefully) ways to fix/recover from these problems. Some potential problems may also be listed in the main OSIRIS User's Manual.

PLEASE REPORT ANY PROBLEMS YOU NOTICE TO:

Darren DePoy (depoy@astronomy.ohio-state.edu)

Bob Blum (rblum@noao.edu)

Sean Points (spoints@ctio.noao.edu)

Vignetting at the corners of the array (November 1998)

OSIRIS was not originally designed to illuminate a full 1024x1024 array (with 18.5 micron pixels) and thus this vignetting is unavoidable without a costly modification of the optical system. This is not planned for the forseeable future, unless you care to write us a big check.

Shading at the array quadrant boundaries (March 1999)

The HAWAII HgCdTe array in OSIRIS exhibits a time variable "shading," or ramping of higher than average bias level at the boundaries of the upper and lower quadrants. This feature generally subtracts cleanly to a high degree between frames (e.g. between succesive object and sky images), but may show residual counts sometimes (particularly between the first image and subsequent images in a series). The unilluminated portion of the OSIRIS images can be used to make a row-by-row correction for this. Ask the support astronomer for details.

20 July 2000. The new array installed in December 1999 does not exhibit the unstable shading of the previous array. Therefore, we recommand that no line-by line bias subtraction be done.

Bias discontinuity across quadrant boundary (April 1999)

The HAWAII HgCdTe array in OSIRIS exhibits a bias discontinuity across the quadrant boundaries (primarily across the boundary between the upper and lower quadrants) which appears to be flux (ADU/second) dependent. The source of the problem is not known. The effect results in a discontinuity in the count level which does not subtract out between similar images taken with and without illumination (e.g dome lights on - dome lights off) when the count rate on the array is above a threshold value of approximately 1000 ADU/second. The flux should be kept below about 1000 ADU/second in order to insure properly calibrated data. This is particularly important for flat fields. Check with the support astronomer for details/status.

20 July 2000. A new array was installed in OSIRIS in 1999 December. The bias discontinuity has been greatly diminished.

Fringing in spectroscopic modes (May 1999)

As with the original NICMOS III detector in OSIRIS, the new HAWAII array exhibits fringing in the spectroscopic modes. Spectra should be taken at multiple (7 to 10) positions along the slit to average out the effect of fringes.

Slit position changes on array (15 January 2001)

The apparrent y pixel position of the slit appears to change on the array when the telescope is moved. It is not clear if this is just a worse than normal flexure or if the acquistion mirror is not repeating its position well (something may be loose). Tests with the telescope in one position and repeated flips of the acquisition mirror indicate it reproduces its position to +/- 0.1 pixel. We will derive a new flexure map on the next engineering run. Until this problem is resolved, observers should pay more attention to the slit position (we recommend checking it on each new object). The full range of movement reported by observers is about 4 pixels.

Sticking of the CAMFOCUS mechanism (01 July 2004)

The CAMFOCUS mechanism which is used to make a best focus of the OSIRIS optical train has been sticking. The mechanism will occasionally either not move at all (though the motor is asserted) or will move but not properly initialize to its home position (these could be independent problems). As of early July, the mechanism appears to be behaving.

Update (12 April 2008)
When a camera is changed using the Prospero command

pr> camera n

where n=0-3, the camera turret rotates to change the camera and performs an automatic camfocus reset. Sometimes after a camera change one receives the following error message in the Prospero window:

pr> camera n Setting camera... pr> camfocus 500 Setting camfocus... pr> camera m Setting camera Error: Command returned error ERROR: Aborting motion: Total step limit exceeded. Error: Could not reset camfocus to home position Execution error in Prospero command. Command: camera m

This signifies that during the camera change, the camfocus reset exceeded its low limit switch and should not be moved via Prospero commands, i.e., repeating

pr> camfocus 0 reset

commands. This will only drive the camfocus mechanism further past the low limit switch, resulting in a physical collision in which the instrument will have to be warmed and opened to fix.

The current accepted procedure to recover from the initial error is to offset the camfocus mechanism via commands to the IE from the ISIS window as shown below.
IS% >IE mstatus camfocus IS% IE> STATUS: MechNum=7 Address=6 EncBits=0000101100000000 Position=INVALID Current=255 StepDelay=2200 IS% >IE setadr 6 IS% IE> DONE: Address=6 IS% >IE offset 2000 IS% IE> DONE: Offset completed. IS% >IE mstatus camfocus IS% IE> STATUS: MechNum=7 Address=6 EncBits=0000101100000000 Position=INVALID Current=255 StepDelay=2200i IS% >IE offset 2000 IS% IE> ERROR: Aborting motion: Hi limit encountered. IS% >IE mstatus camfocus IS% IE> STATUS: MechNum=7 Address=6 EncBits=0010100100100000 Position=HILIMIT Current=255 StepDelay=2200

Notice that at the first mstatus command the camfocus posistion is "INVALID". After the second offset command, the camfocus has been moved to its high limit and the camfocus posistion is no longer INVALID. At this stage, it should be possible to return to the Prospero window and issue a camfocus 0 reset command to home the camfocus mechanism with success. If in doubt about the procedure, please contact Sean Points (the telescope operators have this contact information).

Scrambled Images (07 September 2006)

The fiber run at SOAR may be long enough that image transfer is compromised if the fiber throughput is degraded. The fibers should be checked for transmission each time they are reconnected. The September 06 values show good transmission for test signals of 22mV degradation or less. 22.8 mV is too low and has been shown to result in lost data and therefore bad images.

Fringing in spectroscopic modes at SOAR (July 2007)

Fringing at SOAR is qualitatively similar to what was seen at the Blanco, however the situation is more difficult. The fringe pattern at SOAR is nearly aligned with pixel rows which is perpendicular to the spectral dispersion. Thus simple dithering along the slit is not as effective in removing the fringes (through averaging).

Careful tests suggest the fringes move when the slit mechanism or flip mirror are moved. This means a small movement of the slit image results in a shifted fringe pattern.

A possible solution is to "dither" the grating by a small amount when taking flats. This will produce a combined flat with no fringes. Division of the flat into data taken through out the night can then be used to fit fringes and remove them. Dithering the grating for both data and flats may be the best way to remove fringes, but will require more work in software to reduce.

Short exposure times in f/7 spectroscopic mode (July 2007)

It is not recommended to take spectra of bright objects which require the minimum exposure time (3 sec). The reason is that the dispersion direction is perpendicular to the fast read pixel direction and thus the OSIRIS readout can be up to 3 sec different for parts of the spectrum. This is enough that seeing changes can affect the amount of light through the slit for different parts of the spectrum. This problem appears possibly more significant at SOAR than at the Blanco, and it is not clear if part of the issue is guiding rather than seeing excursions. Please use fainter telluric standards which require longer exposure times (7-8th mag, 30-60 sec) so that the read time is a small fraction of the total exposure. Uniform surface brightness dsitributions are not affected.

[ OSIRIS Home Page ]

Updated: 2007 July [osiris@astronomy.ohio-state.edu]