next up previous contents
Next: Long-Slit Grism Data Reduction Up: Full Mosaicing Previous: Handling Larger Images

CASPIR Image Composite Database Format

The caspir package generates composite databases according to a simple format. The position of each individual image is descibed by a COM-line (a line beginning with "COM"). Commenting out a COM-line (by putting a "#" in front) eliminates that image from the final combined image. A sample database file and a description of the COM-line follows:

#DBM Wed 15:56:15 15-Jan-92 CSPMERGE: mosn10_024k.cdb
#DBM    master_file     mosn10_024k.mdb
#DBM    master_ref      mosn10_024k[258:513,258:513]
#DBM    merge_file      mosn10_024k.cdb
#DBM    merge_file      mosn10_024k_10.cdb
#DBM    merge_file      mosn10_024k_11.cdb
#DBM    merge_file      mosn10_024k_12.cdb
#DBM    merge_file      mosn10_024k_13.cdb
#DBM    merge_file      mosn10_024k_14.cdb
#DBM    merge_file      mosn10_024k_15.cdb
#DBM    merge_file      mosn10_024k_16.cdb
#DBM    merge_file      mosn10_024k_17.cdb
#DBM    merge_file      mosn10_024k_18.cdb
#DB # Wed 14:23:16 15-Jan-92:
#DB begin       mosn10_024k
#DB     trimsection     [*,*]
#DB     medsection      [*,*]
#DB     ncols           256
#DB     nrows           256
#DB     nxsub           3
#DB     nysub           8
#DB     nxoverlap       -1
#DB     nyoverlap       -1
#DB     corner          ll
#DB     order           row
#DB     raster          no
#DB     oval            10000.
#DB     nsubrasters     24
#DB  Wed 14:23:37 15-Jan-92:
#DB     null_input      23-24
#DB     mosaic          mosn10_024k
#DB     median_compute  yes
#DB     median_subtract no
#DBL Wed 15:27:57 15-Jan-92:
#DBL    info_file       _Tgmh9352es.ctr
#DBL    nxrsub          2 
#DBL    nyrsub          2 
#DBL    ref_image       mosn10_024k[258:513,258:513]
#DBL    ref_nim         5 
#DBG Wed 15:28:10 15-Jan-92:
#DBG    basis_info      mosn10_024k.ctr.1
#DBG    lap_basis       center
#DBG    trimlimits      [4:3,8:0]
#DBT    mos_transform   no
#DBM    do_tran         no
#DBM    out_sec         [1:727,1:703]
#DBM    overlap_sec     [475:252,455:255]
COM_000 mosn10_024k[258:513,258:513]   5 253 9 256  245  220  0.00  0.00 0.00 |
COM_001 mosn10_024k[1:256,1:256]       5 253 9 256   21    4  0.44 -0.31 0.00 |
COM_002 mosn10_024k[258:513,1:256]     5 253 9 256  241    0  0.32  0.22 0.00 |
COM_003 mosn10_024k[515:770,1:256]     5 253 9 256  462    0 -0.39 -0.30 0.00 |
COM_004 mosn10_024k[1:256,258:513]     5 253 9 256   25  224 -0.47  0.17 0.00 |
COM_005 mosn10_024k[258:513,258:513]   5 253 9 256  245  220  0.00  0.00 0.00 |
COM_006 mosn10_024k[515:770,258:513]   5 253 9 256  466  220 -0.42 -0.48 0.00 |
COM_007 mosn10_024k[1:256,515:770]     5 253 9 256   28  445 -0.08 -0.19 0.00 |
COM_008 mosn10_024k[258:513,515:770]   5 253 9 256  248  442  0.26 -0.13 0.00 |
COM_009 mosn10_024k[515:770,515:770]   5 253 9 256  469  439  0.01  0.24 0.00 |
COM_010 mosn10_024k[1:256,772:1027]    5 253 9 256    0    4 -0.34  0.11 0.00 |
COM_011 mosn10_024k[258:513,772:1027]  5 253 9 256  220    1 -0.28 -0.23 0.00 |
COM_012 mosn10_024k[515:770,772:1027]  5 253 9 256  439    0  0.47  0.23 0.00 |
COM_013 mosn10_024k[1:256,1029:1284]   5 253 9 256    2  225  0.41 -0.39 0.00 |
COM_014 mosn10_024k[258:513,1029:1284] 5 253 9 256  223  220 -0.03  0.48 0.00 |
COM_015 mosn10_024k[515:770,1029:1284] 5 253 9 256  443  220  0.24 -0.07 0.00 |
COM_016 mosn10_024k[1:256,1286:1541]   5 253 9 256    6  445  0.11  0.21 0.00 |
COM_017 mosn10_024k[258:513,1286:1541] 5 253 9 256  226  442  0.05  0.25 0.00 |
COM_018 mosn10_024k[515:770,1286:1541] 5 253 9 256  447  440 -0.15 -0.42 0.00 |

Each image has a "COM-line", which is arranged as follows:

Col. 1:
COM path identification. Unless renumbered, the _XXX corresponds to the original path position in the cspmos database. 'COM_000' marks the reference image.
Col. 2:
Actual name of the subraster, including image section, giving the location where this piece of the dataset can be found within the mosaic image produced by cspmosaic.
Col. 3 - Col. 6:
xmin, xmax, ymin, ymax. The subsection of the original image subraster which will be included in the final image. The cumulative effects of the trimlimits parameters are reflected here.
Col. 7 - Col. 8:
The x and y coordinates of the integer location of the subraster in the final image. The imshifted subraster will be offset to this integer location in the final image.
Col. 9 - Col. 10:
The x and y coordinates of the fraction location of the subraster in the final image. The subraster will be imshifted by this amount prior to image combination.
Col. 11:
The intensity offset for the subraster which will be added prior to image combination (not cumulative - applies to image only).
Col. 12:
An end-of-line marker designed to frustrate the system daemons which want to suppress any LF at the end of a line in columns 79 or 80 (thereby merging the COM-lines into one line!)

Note: Buried deep in the UNIX/IRAF system is a "daemon" which silently decides "The line is too long, I must silently fix it!". This "feature" is activated within the .login file (and elsewhere) when the environmental variable wrap is set. Lines which will be 80 characters long are optionally given an automatic LF, so that you need not worry about such issues when you are typing. This feature will break COM-lines and raise all sorts of havoc within the CASPIR registration database files!


next up previous contents
Next: Long-Slit Grism Data Reduction Up: Full Mosaicing Previous: Handling Larger Images

Kabal
Thu Jun 5 16:44:21 EST 1997