The core luciTools programs are:
This tar file
Alternatively, you can download the individual programs below.
slit_type = one of mask, phot, 2.0, 1.5, 1.0, 0.75, 0.5, and 0.25
lucierrors works assuming that a uniform naming convention has been adopted by all observers (cue laughter). We make the following associations based on the file extension:
XX.acq -- target acquistion script
XX.spc/.spec/.obs -- spectroscopic science observation script
XX.img -- imaging script
XX.cal -- calibration script
XX.flat -- flat field calibration script
XX.arc -- arc (comparison) lamp calibration script
XX.dark -- dark calibration script
XX.cal -- generic calibration script
It is hard to guess all possible naming variations, so at least among
the OSU/RC partners we are enforcing a uniform naming convention going
forward to try vainly to reduce our observing queue ingestion and script
checking workload.
The testing rules as of the current version are:
We are also encouraging users to start embedding two comments inside target acquisition scripts:
# TARGET_MAG = 13.50 H mag # GUIDE_MAG = 14.80 R magThese will be used by lucierrors to help better automate sanity checking target and guide star choices. It is essential that they be included as comments with the # character as these are not valid LUCI script commands. For OSU/RC users, these comment keywords will eventually become mandatory for all LUCI acq scripts submitted to the observing queue.
lucierrors 1.0This will sniff all scripts whose names match the above file extensions in the current working directory (NB: it does not crawl through subdirectories) and tests for common errors in logic.
script - name of LUCI .img or .spec script
The output file will be named script.flat.cal (e.g., derived from script.img or script.spec).
The flat field exposures are based on the count rates published in the LUCI instrument manual. It attempts to automatically assign lamps and integration times. The default script will execute 5 flats in each mode, and aims for a maximum of 20000 counts.
The output script will be named script.flat.cal, where script is the root name of the img or spec script given on the command line (see the Example below).
If it cannot estimate the appropriate DIT and LAMPs, it fills in the values with UNKNOWN and warns the user, and appends the file extension ".needsfixes" to alert the user (e.g., output file is script.flat.cal.needsfixes).
makeluciflat j1140.spec
Produces output
Producing a flat for script j1140.spec - output will be j1140.flat.cal
INFORMATION: defaults to O2DCR read mode and NORMAL save mode
with 5 exposures designed to yield 10000 counts each
based on count rates reported in the Lucifer manual
EXTRACTING INFORMATION FROM TARGET SCRIPT j1140.spec
found PI_NAME DTerndrup
found PROP_ID OSU_BALQSO_He
found CAMERA N1.8
found FILTER HKspec
found GRATING 200_H+K
found CENTRAL WAVE 1.93
found MASK ID990034
found MASK_POSITION mask_in_fpu
found ROE_MODE mer
Appear to have found all the needed parameters, estimating count rate
Using slitwidth 1 arcsec for slit ID990034
Expected count rate for filter HKspec lamp halo2 camera N1.8 grating 200_H+K is 2800 (ADU/s)
Will use time DIT=4 to get total counts 11200 in one exposure -- defaulting to making 5 flat exposures
and creates j1140.flat.cal in the current working directory.
Options:
-s acqScript Name of the science target acquisition (.acq) script -r deg Search radius in degrees [default: 10°] -t hours Time shift in hours of RA [default: 0 hours] -h Print help
The search radius can be changed using the -r option. The default is equivalent to -r 10.
You can shift your search forward or backwards in RA (time) at the same declination by using the -t option. For example, -t 0.5 will shift the target RA by 0.5 hours forward, and search for telluric stars around that position. This would be used, for example, to find telluric stars at the mid-point of a 1-hour science exposure to be executed after the science observations. If instead you want a telluric star to be observed before the science observations, give it a negative value (e.g., -t -0.5).
A list is printed on the screen. Pick the star you want based on the spectral type, magnitude, and availability of guide stars. These are guide stars it will try to select automatically. If you elect to select guide stars by hand, you may find others nearby that are useful beyond our simple recommendation. Beware that the choices are based on the USNO-B1 catalog, and some "stars" in USNO-B1 are unsuitable on inspection.
findlucitelluric -s j1140.acqwill print
Will parse script j1140.acq for parameters Searching for tellurics for j1140.acq within radius 10 degrees and an RA shift of 0 hours using findlucitelluric.v010.pl on Tue Dec 18 15:29:51 EST 2012 EXTRACTING INFORMATION FROM TARGET SCRIPT j1140.acq found COORD 11 40 43.63 +53 24 38.9 CANDIDATE TELLURIC STARS dist name RA Dec Type Hmag Nguide 1.41 HIP56974 11:40:46.35 +51:59:53.4 G0V 8.214 3 4.43 HIP54765 11:12:44.45 +54:53:39.4 A4V 6.434 3 4.53 HIP59330 12:10:15.88 +54:29:17.3 G0Vm 7.126 2 4.62 HIP55485 11:21:49.29 +57:04:29.4 A7Vn 6.023 3 ... 9.98 HIP51697 10:33:43.77 +53:29:50.5 A1V 6.490 5 Nguide is the number of guide stars associated with the telluric in / home1/webserv/lbtosurc/OSURC/Scripts/telluric.guide.v020.cat Closest telluric was at 1.413 degreesYour name choice becomes one of the inputs for running makelucitelluric to create the acquisition and observing scripts.
Options:
-s specScript Name of the science target observing (.spec) script -n telStar Use telStar selected previously with findlucitelluric -t 'ra dec Hmag' RA, Dec (sexigessimal 00:00:00 -00:00:00), H mag of a telluric star (instead of -n) -g 'ra dec Rmag pa' RA, Dec (sexigessimal 00:00:00 -00:00:00), Rmag, and rotator PA for a guide star -f fwhm Assumed seeing FWHM for counts estimation [default: 0.8 arcsec] -w width Slit width to use in arcsec [default: 1.0 arcsec] -m Manually select a guide star from the list -h print help
If the telluric star has a guide star, it will automatically assign the guide star which minimizes the change in the rotator angle (a semi-arbitrary choice). If you want a different one from the list of available guide stars you can select it manually (-m option). Otherwise you must specify everything about the guide star (-g option)
The slit width is determined automatically if possible, otherwise you can specify it with the -w option or you will be prompted for it. A known slit width based on the mask ID###### identification will override the width given by the -w option
You can change the assumed seeing from the default 0.8 arcsec with the -f option. This scales the peak telluric counts as FWHM*FWHM and the spectral counts by FWHM (along slit) and an error function for the slit width (Note: the LUCI ETC appears to scale spectral counts just as FWHM*FWHM).
Exposure times are set automatically to try to get between 65000 and 130000 counts in the summed spectrum and 10000 to 20000 peak counts in the acquisition image. The count estimates are included as comments in the generated scripts.
If there is insufficient information on the guide star, the guide star properties and rotator angle are set to UNKNOWN.
If the estimated count rates seem to imply that it is impossible to use the telluric star without coming close to saturation, the integration parameters are set to UNKNOWN.
makelucitelluric -s j1140.spec -n HIP55485will build two scripts
HIP55485.acq.new HIP55485.spec.newwith the acquistion and spectroscopy LUCI scripts, respectively. As it creates them you will get a verbose printout of its estimation of the counts, choice of filter for acquisition, etc.