Mess with the WTTM data 05.29.02 ## Looks like extension 1 carries the image data ## ## --------------------------------------------- ## display n2133[1] 1 display n2134[1] 2 display n2135[1] 3 display n2136[1] 4 beep ## Arjun warned that first image was short, so will probably ## want to do some scaling... ## ---------------------------------------------------------- imstat n2133[1][600:2000,600:2000] imstat n2134[1][600:2000,600:2000] imstat n2135[1][600:2000,600:2000] imstat n2136[1][600:2000,600:2000] # IMAGE NPIX MEAN MAX MIDPT n2133[1][600:2000,600:2000] 1962801 1.99 1337. 1.841 n2134[1][600:2000,600:2000] 1962801 10.18 4483. 9.988 n2135[1][600:2000,600:2000] 1962801 9.546 5730. 9.436 n2136[1][600:2000,600:2000] 1962801 9.393 4054. 9.329 ## Looks like there's a bit of a shift: ## ---------------------------------------------------------- 876.00 1883.18 875.93 1883.30 882.87 1891.00 882.98 1890.99 ## Resulting shift file: 0 0 0 0 -7 -8 -7 -8 imcombine ("@list.combine", "hdf_nb", rejmask=" ", plfile=" ", sigma="", logfile="STDOUT", combine="average", reject="none", project=no, outtype="real", offsets="list.shift", masktype="none", maskvalue=0., blank=0., scale="median", zero="none", weight="none", statsec="[600:2000,600:2000]", expname="", lthreshold=INDEF, hthreshold=INDEF, nlow=0, nhigh=2, nkeep=1, mclip=yes, lsigma=3., hsigma=3., rdnoise="0.", gain="1.", snoise="0.", sigscale=0.1, pclip=-0.682, grow=0.) display hdf_nb 1 ## Check out this scaling: ## ---------------------------------------------------------- Images Median Scale Offsets n2133[1] 1.858 4.127 7 8 n2134[1] 10.027 0.765 7 8 n2135[1] 9.4284 0.813 0 0 n2136[1] 9.3595 0.819 0 0 ## Doesn't that look like it's doing the wrong thing? The first image ## should count *less*. Rather than deal with this further, let's just ## drop it from the data. imcombine ("@list.combine", "hdf_nb3", rejmask=" ", plfile=" ", sigma="", logfile="STDOUT", combine="average", reject="none", project=no, outtype="real", offsets="list.shift", masktype="none", maskvalue=0., blank=0., scale="median", zero="none", weight="none", statsec="[600:2000,600:2000]", expname="", lthreshold=INDEF, hthreshold=INDEF, nlow=0, nhigh=2, nkeep=1, mclip=yes, lsigma=3., hsigma=3., rdnoise="0.", gain="1.", snoise="0.", sigscale=0.1, pclip=-0.682, grow=0.) display hdf_nb3 1 ## Astrometry in WTTM header (?!) indicates that the image is rotated ## by 90 degrees. Undo this: ## ---------------------------------------------------------- input = "hdf_nb3" Input data output = "hdf_nb3rot" Output data rotation = -90. Rotation angle in degrees (xin = INDEF) X origin of input image in pixels (yin = INDEF) Y origin of input image in pixels (xout = INDEF) X origin of output image in pixels (yout = INDEF) Y origin of output image in pixels (ncols = 0.) Number of columns in the output image (nlines = 0.) Number of lines in the output image (interpolant = "linear") Interpolant (nearest,linear,poly3,poly5,spline3) (boundary = "constant") Boundary extension (nearest,constant,reflect,wrap) (constant = 0.) Constant for constant boundary extension (nxblock = 512) X dimension of working block size in pixels (nyblock = 512) Y dimension of working block size in pixels (verbose = yes) Print messages about the progress of the task ? (mode = "ql") ## Now look for known objects. Some facts from Arjun: ## "Pixel scale is around 0.1"/pix if i recall." ## "fov is around 4'" ## "The position for the center of the field is 12:36:52.67 +62:16:02.7 J2000" ## (This is pix 1297,2321 in Hawaii I-band image.) ## ---------------------------------------------------------- ## The header information is CRAP CRAP CRAP. Looks to me like there's a flip ## in the x-y direction. imcopy hdf_nb3[-*,*] hdf_nb3f That's it. Jesus Christ. Make a plate solution. imexam > image.xy tvmark 3 image.xy label- num+ color=204 nxoffse=10 nyoffse=10 pointsi=3 txsize=3 toleran=3 radii=3 imexam > ref.xy tvmark 2 ref.xy label- num+ color=204 xyeq yes dss_plate_finder "" ref.xy iraf 1 2 0 > ref.radec xyeq yes dss_plate_finder4 "" ref.xy iraf 1 2 0 > ref.radec Results in: Coords File: image.xyradec Image: hdf_nb3f Database: hdf_nb3f.db Solution: hdf_nb3f Refsystem: j2000 Coordinates: equatorial FK5 Equinox: J2000.000 Epoch: J2000.00000000 MJD: 51544.50000 Insystem: j2000 Coordinates: equatorial FK5 Equinox: J2000.000 Epoch: J2000.00000000 MJD: 51544.50000 Coordinate mapping status Ra/Dec or Long/Lat fit rms: 0.194 0.0984 (arcsec arcsec) Coordinate mapping parameters Sky projection geometry: tan Reference point: 12:36:53.254 62:15:49.45 (hours degrees) Reference point: 937.611 1113.304 (pixels pixels) X and Y scale: 0.111 0.107 (arcsec/pixel arcsec/pixel) X and Y axis rotation: 179.521 359.639 (degrees degrees) Wcs mapping status Ra/Dec or Long/Lat wcs rms: 0.194 0.0984 (arcsec arcsec) Updating image header wcs ## GOT IT. Shit. Now look for our sers... display hdfall_i_reg 1 display hdf_nb3f 2 beep ## Try registering? Use wregister: input = "hdf_nb3f" The input images reference = "hdfall_i_reg" Input reference images output = "hdf_nb3f_reg" The output registered images (xmin = INDEF) Minimum logical x reference coordinate value (xmax = INDEF) Maximum logical x reference coordinate value (ymin = INDEF) Minimum logical y reference coordinate value (ymax = INDEF) Maximum logical y reference coordinate value (nx = 10) Number of grid points in x (ny = 10) Number of grid points in y (wcs = "world") The default world coordinate system (transpose = no) Force a world coordinate tranpose ? (xformat = "%10.3f") Output logical x coordinate format (yformat = "%10.3f") Output logical y coordinate format (wxformat = "") Output world x coordinate format (wyformat = "") Output world y coordinate format (fitgeometry = "general") Fitting geometry (function = "polynomial") Type of coordinate surface to be computed (xxorder = 2) Order of x fit in x (xyorder = 2) Order of x fit in y (xxterms = "half") X fit cross terms type (yxorder = 2) Order of y fit in x (yyorder = 2) Order of y fit in y (yxterms = "half") Y fit cross terms type (reject = INDEF) The rejection limit in units of sigma (calctype = "double") Transformation computation type (geometry = "geometric") Transformation geometry (xsample = 1.) X coordinate sampling interval (ysample = 1.) Y coordinate sampling interval (interpolant = "nearest") The interpolant type (boundary = "nearest") Boundary extensiontype (constant = 0.) Constant for constant boundary extension (fluxconserve = yes) Preserve image flux ? (nxblock = 9200) X dimension blocking factor (nyblock = 1024) Y dimension blocking factor (wcsinherit = yes) Inherit wcs of the reference image ? (verbose = yes) Print messages about progress of task? (interactive = no) Compute transformation interactively? (graphics = "stdgraph") The standard graphics device (gcommands = "") The graphics cursor (mode = "ql") Output: Coordinate list: imxymatch.1 Transform: hdf_nb3f Results file: Coordinate mapping status X fit ok. Y fit ok. Xin and Yin fit rms: 8.396476E-4 8.970486E-4 Coordinate mapping parameters Mean Xref and Yref: 1500.5 1500.5 Mean Xin and Yin: 1387.104 -303.1325 X and Y shift: -1295.863 -3144.991 (xin yin) X and Y scale: 1.800795 1.876924 (xin / xref yin / yref) X and Y axis rotation: 359.457 359.613 (degrees degrees) Transforming image hdf_nb3f to image hdf_nb3f_reg Using transform hdf_nb3f in database wregister.db ## It worked, but you gotta not let IRAF pick the zscale on the registered ## nb image: display hdf_nb3f_reg zs- z1=-2.855802 z2=50.90023 zr- ## Carve it up so that you don't have this problem: imcopy hdf_nb3f_reg[740:1870,1690:2980] hdf_nb3f_regnbt imcopy hdfall_i_reg[740:1870,1690:2980] hdfall_i_regnbt imcopy hdf_Rimage_reg[740:1870,1690:2980] hdf_Rimage_regnbt display hdf_nb3f_regnbt 1 display hdf_Rimage_regnbt 2 display hdfall_i_regnbt 3 beep ## Tar it up and send it to arjun: hal2000> tar cvf wttm.tar hdf_Rimage_regnbt.fits hdf_nb3f_regnbt.fits hdfall_i_regnbt.fits