The HIRES Redux Page

Brought to you by

I should first emphasize that this code was developed by using many of the routines created for the MIKE Redux
 pipeline. In particular, the efforts of Scott M. Burles (MIT) were critical to any success of this pipeline.
HIRES

Quick Links

Recommendations for Calibrations

Archived Calibration Files


HIRES Install


HIRES cookbook


HIRES QA Examples


HIRES bugs none reported! :)


HIRES Version Notes




I. Overview of the Code

The HIRES Redux code was built with the IDL software pacakge to reduce single point source objects. The code can work with users that have little IDL experience, but you will struggle at first. I highly recommend you read the Intro to IDL book or some other resource before diving in. Here is an executive summary of the code (a simple Keynote presentation in PDF format):

HIRES presentation (4Mb pdf)


The general approach of the code is as follows:
  • Examine the set of data files to determine image type
  • Organize the observations according to setups.
  • Process the flats and trace the orders
  • Process the arcs and create 2D wavelength solutions
  • Create a slit profile
  • Process the object frames (flatten, CR reject)
  • Identify and trace the object
  • Sky subtract
  • Extract
  • Flux (Coming..)

II. Installing the Software

The code relies on several IDL packages in addition the routines that were designed specifically for MIKE. These are:
More detailed notes for obtaining and installing these packages can be found here: install notes. We wish to emphasize that the code expects the most up-to-date versions of the Sloan codes. Users with old versions of any of these packages beware!

III. Using the Code

Moderately detailed descriptions of running the code are given in this reduction cookbook. While we try to include a lot of detail here, it still is insufficient. All of the HIRES routines are described in this html file. Experienced IDL users should be able to dig into the codes and follow along.
Hopefully, we will include an example session of running the code in this space before long.

III. Developing the Code + Bug Fixing

We do encourage all users to consider ways to improve the code and to suggest them to us. Of course, we'd also like to hear about bugs. Please do make an effort to verify it is a bug in the code as opposed to 'user error'. Along those lines, if you are a novice to IDL, we suspect you will have many more 'user errors' than bugs to find.
This research is supported, in part, by NSF grant AST 03-07408.
e-mail: hiredux@ucolick.org
last modified 2/10/06