| 
 
 Step 4: Preparing a list of observation
requests (continued)
 
 Specifying mosaics of CCD fields (continued)
 
A minor planet search could use mosaics of CCD fields with rows oriented in the
east-west direction, that is, PA = 90 deg. In this case, one could prepare
a text file containing a list of names and centers for various mosaics in different
parts of the sky, 
 
| Mosaic_1   13 25 00.00 +35 00 00.0
Mosaic_2   15 00 00.00 -11 00 00.0
Mosaic_3   18 30 00.00 -17 00 00.0
Mosaic_4   20 12 00.00 +00 00 00.0
Mosaic_5   22 00 00.00 +14 00 00.0
 |  
add these objects to TAO's fixed object database
with the help of program addFixedTargets, and then
request mosaics around the various center coordinates: 
 
| Mosaic_1; &
  PA=90 width=3.50 overlap=1.50 dRA=0. ddec=0. &
    -1   -1 &
     0   -1 &
     1   -1 &
    -1    0 &
     0    0 &
     1    0 &
    -1    1 &
     0    1 &
     1    1
Mosaic_2; &
  PA=90 width=3.50 overlap=1.50 dRA=0. ddec=0. &
     0    0 &
     1    0 &
     2    0 &
     3    0
...   
 |  
Notes:
  All fields in a mosaic will be scheduled using identical parameters. In particular,
      the exposure time, camera resolution, frame size, frame mode, filter, observing 
      window, minimum altitude, maximum |hour angle|, moon avoidance radius, image
      insertion method, and request
      identifier will be the same for all fields. The number of requested images per field
      will be the same for all fields; if the timeseries 
      keyword is specified on
      the first line of the mosaic request, then different numbers of images may be 
      scheduled for each field.
  The default options specified in the user's profile
      may be overriden in the same way as for non-mosaic requests, by specifying
      the non-default options on the first line of the request:
 
| 2002 XH4; 4i exp=300. filter=I &
  PA=36.5 width=3.50 overlap=1.50 dRA=-.00137 ddec=-.02052 &
     0    0 &
    -1    0 &
     1    0 &
    -2    0 &
     2    0
 |  
    The above request would be identical to the previously discussed example about the
    recovery of 2002 XH4, except that now four 300-sec I-band exposures of each field 
    are being requested. 
  The fields in a mosaic may be labeled with individual request
identifiers. For example, in the request
 
| C/2003 F1; &
  PA=36.5 width=3.50 overlap=1.50 dRA=-.00137 ddec=-.02052 &
     0    0 &
    -1    0 #MT-052 &
     1    0 &
    -2    0 # &
     2    0 #AM-441
 |  
fields (-1,0) and (2,0) have identifiers MT-052 and AM-441, respectively, and the other
three fields have blank identifiers. If an identifier is specified on the first line
of a mosaic request, it applies to all fields for which individual requests have not been
specified. For example, in the request
 
| 2004 JB12; #C042-A &
  PA=36.5 width=3.50 overlap=1.50 dRA=-.00137 ddec=-.02052 &
     0    0 &
    -1    0 #SP-332 &
     1    0 &
    -2    0 # &
     2    0 #MG-163
 |  
fields (0,0) and (1,0) share the identifier C042-A, fields (-1,0) and (2,0) have
identifiers SP-332 and MG-163, respectively, and field (-2,0) has a blank identifier.
 
Previous: Specifying mosaics of CCD fieldsNext: Running the scheduler
 
 
 
 © 1999-2004 Paulo Holvorcem
 |