This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
dithered_exposures [2019/07/29 15:43] davner removed |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | The note below is kindly provided by Christopher Willmer. | ||
- | |||
- | 90Prime allows obtaining dithered exposures through scripts, which is | ||
- | absolutely critical in the case of exposures in R, I, SDSS r, i and z | ||
- | (e.g. Cool, 2007, ApJS, 169,21) where fringing is a problem. | ||
- | As an example, R. Cool combined from 12 to 42 z band exposures obtained | ||
- | during the course of each night to create a " | ||
- | By scripting much of the book-keeping is reduced. | ||
- | |||
- | In the case described here, a series of " | ||
- | is calculated using a circular pattern. The total amplitude in Ra and Dec is | ||
- | 2 arc minutes, about 10% of the areal coverage of a single 90Prime CCD | ||
- | (area 23 arc min x 23 arc min). | ||
- | |||
- | 1) The observing scripts were generated using a Fortran programme (dither.f), | ||
- | for which a central coordinate, image type, object name and list of filters | ||
- | are given. In the code I use 10 dithers for SDSS u and g and 20 | ||
- | for SDSS r, i and z. The programme generates an output file | ||
- | " | ||
- | fed into a perl script (dither_to_dos.pl) that will translate the | ||
- | LINUX/UNIX carriage return control into DOS carriage return + linefeed. | ||
- | For each file is does: | ||
- | |||
- | perl -p -e ' | ||
- | |||
- | 2) The scripts then need to arrive at the 90prime bokccd computer somehow. | ||
- | I copied the files to bok: | ||
- | |||
- | scp *scr*txt primefocus@bok.as.arizona.edu:/ | ||
- | |||
- | and then on bokccd fired cygwin and | ||
- | |||
- | scp primefocus@bok.as.arizona.edu:/ | ||
- | |||
- | (not the most straightforward way but works, a USB port is also available) | ||
- | |||
- | These must then be copied using windows into directory: | ||
- | |||
- | c: | ||
- | |||
- | The final scripts MUST have the .txt suffix, otherwise the windows machine | ||
- | will not understand the file. | ||
- | |||
- | 3) Running the script | ||
- | |||
- | When the script is run, the telescope is moved to the new position and | ||
- | it will wait until the " | ||
- | waits for an additional 0.1 sec to start the integration (M. Lesser, private | ||
- | Communication, | ||
- | |||
- | To carry out dithered exposures with 90 Prime one uses on AzCam the command | ||
- | |||
- | Run Observe scriptname #_of_times | ||
- | |||
- | where #_of_times will be the number of times this script should be run. | ||
- | |||
- | This is what a line in a script looks like: | ||
- | |||
- | obs 150.0 object ' | ||
- | |||
- | obs - is the script command | ||
- | 150 - exposure time | ||
- | object - image type (OBJECT, ZERO, FLAT) | ||
- | ' | ||
- | 1 - number of exposures at this position | ||
- | u - filter | ||
- | 090348.00 - RA (HMS) with _ONLY_ two decimal digits!! | ||
- | +173427.0 - DEC (DMS) with 1 decimal digit precision | ||
- | 2000.0 - EPOCH | ||