2. Installation

The astrodata package has several dependencies like numpy, astropy, and others. All dependencies of gemini_python and astrodata are provide by the Ureka package, and users are highly encouraged to install and use this very useful package. It is an easy and, perhaps, best way to get everything you need and then some. Ureka is available at http://ssb.stsci.edu/ureka/.

WARNING: The Ureka installation script will not set up IRAF for you. You need to do that yourself. Here’s how:

$ cd ~
$ mkdir iraf
$ cd iraf
$ mkiraf
-- creating a new uparm directory
Terminal types: xgterm,xterm,gterm,vt640,vt100,etc.
Enter terminal type: xgterm
A new LOGIN.CL file has been created in the current directory.
You may wish to review and edit this file to change the defaults.

Once a user has has retrieved the gemini_python package, available as a tarfile from the Gemini website (http://gemini.edu), and untarred only minor adjustments need to be made to the user environment in order to make astrodata importable and allow reduce to work properly.

2.1. Install

2.1.2. Installation under Ureka

Assuming that you have installed Ureka and that you have write access to the Ureka directory, this will install astrodata in the Ureka site-packages directory. WARNING: While easier to install and configure, this will modify your Ureka installation.

$ python setup.py install

This will also add executables to the Ureka bin directory and documentation to the Ureka share directory.

With this installation scheme, there is no need to add paths to your environment. However, it is a lot more complicated to remove the Gemini software in case of problems, or if you just want to clean it out after evaluation.

In tcsh, you will need to run rehash to pick the new executables written to bin.

2.2. Test the installation

Start up the python interpreter and import astrodata:

$ python
>>> import astrodata

Next, return to the command line and test that reduce is reachable and runs. There may be some delay as package modules are byte compiled:

$ reduce -h [--help]

This will print the reduce help to the screen.

If users have Gemini fits files available, they can test that the Recipe System is functioning as expected with a test recipe provided by the astrodata_Gemini package:

$ reduce --recipe test_one /path/to/gemini_data.fits

If all is well, users will see something like:

Resetting logger for application: reduce
Logging configured for application: reduce
                       --- reduce, v4890  ---
              Running under astrodata Version GP-X1
All submitted files appear valid
Starting Reduction on set #1 of 1

  Processing dataset(s):
        gemini_data.fits

==============================================================================
RECIPE: test_one
==============================================================================
 PRIMITIVE: showParameters
 -------------------------
 rtf = False
 suffix = '_scafaasled'
 otherTest = False
 logindent = 3
 logfile = 'reduce.log'
 reducecache = '.reducecache'
 storedcals = 'calibrations/storedcals'
 index = 1
 retrievedcals = 'calibrations/retrievedcals'
 cachedict = {'storedcals': 'calibrations/storedcals', 'retrievedcals':
              'calibrations/retrievedcals', 'calibrations': 'calibrations',
              'reducecache': '.reducecache'}
 loglevel = 'stdinfo'
 calurl_dict = {'CALMGR': 'http://fits/calmgr',
                'UPLOADPROCCAL': 'http://fits/upload_processed_cal',
                'QAMETRICURL': 'http://fits/qareport',
                'QAQUERYURL': 'http://fits/qaforgui',
                'LOCALCALMGR': 'http://localhost:%(httpport)d/calmgr/%(caltype)s'}
 logmode = 'standard'
 test = True
 writeInt = False
 calibrations = 'calibrations'
 .
Wrote gemini_data.fits in output directory


reduce completed successfully.

Users curious about the URLs in the example above, i.e. http://fits/..., see Sec. Fits Storage in Chapter 5, Discussion.

Table Of Contents

Previous topic

1. Introduction

Next topic

3. Interfaces

This Page